AI Poland 2026 · Free online webinar

Mocks Tax Every Change. Agents Just Hand You the Bill.

Live online webinar 100% free

Mocks tax every change.
Agents just hand you the bill.

Join Younes Jaaidi to see how your testing strategy becomes your review strategy: structure-insensitive tests and Charted Coding to beat review fatigue in AI-assisted development.

Thursday, 5 November 2026 · 17:00 CET60 minutes · Online · Free

No fee, no ticket needed. Register with your e-mail and we will send you the link to join. With Younes Jaaidi · Software Engineer and trainer at Marmicode, Google Developer Expert.

Workshop host Younes Jaaidi
TEST BEHAVIOR, NOT STRUCTURE
Younes JaaidiSoftware Engineer & trainer at Marmicode · Google Developer Expert
The experiment

Same prompt, same codebase, two testing strategies.

We run one change, "make courses a required search parameter", twice on the same Angular app tested with Vitest. Mock-heavy tests force a 43-file rewrite and still ship the bug. Behavior-focused tests with fakes touch 3 files, rewrite nothing, and catch it.

Side-by-side comparison. Mocks: 43 files changed, 212 test lines, about one hour to review, bug still shipped. Fakes: 3 files changed, 0 test lines rewritten, about one minute to review, no bug shipped.
Mock-heavy: 43 files, ~1 h review, bug shipped Behavior-focused: 3 files, ~1 min, bug caught
What we'll use
AngularVitestFakesObject MothersCharted Coding
01 / SPOT

Spot the hidden cost.

See why mock-heavy tests turn every agent refactor into a review burden, and how a fully green suite can still hide a bug.

02 / BEHAVIOR

Test behavior, not structure.

Learn the patterns that let tests survive refactors and point at real bugs: fakes over mocks, object mothers, readable setup.

03 / TRUST

Review less, trust more.

Meet Charted Coding, a methodology where the tests carry the load while you review only what matters.

One hour. One change, run twice.

From a green suite
to a bug you can't hide.

A focused, demo-driven session: we run the same change on two testing strategies, review both diffs, then make testing the center of the workflow with Charted Coding. You can follow along without coding.

Mocks Tax Every Change
  1. 01

    The hidden cost of mocks

    Why mock-heavy tests make every agent refactor expensive, and why the bill now lands in review.

  2. 02

    The change on mock-heavy tests

    Run it on Vitest with mocks: a 43-file diff, tests rewritten to stay green, and a bug swept under a mock.

  3. 03

    The change on behavior-focused tests

    Run the same change with fakes and object mothers: a 3-file diff, nothing rewritten, the bug caught.

  4. 04

    Review the two diffs

    Compare which diff you can actually review and which suite points at the real bug.

  5. 05

    Charted Coding

    Design doc, scaffold, red, green: a methodology that puts testing at the center so you review where it matters.

  6. 06

    Takeaways & next steps

    Wrap-up and where to take structure-insensitive testing and Charted Coding next.

The methodology

Charted Coding: tests at the center.

A design doc to scaffold to red to green loop that keeps a human hand on the helm. You chart the intent and waypoints, navigate with failing then passing tests, and steer: refactor, rollback, re-chart or compound.

Charted Coding diagram: a Chart with a design doc and waypoints feeds a Navigate loop of scaffold, red failing test, green make it pass, and refactor, with a Steer axis from hands on helm to autopilot.
Chart · design doc + waypoints Navigate · red, green, refactor Steer · refactor, rollback, re-chart
Workshop host Younes Jaaidi
Meet your host

Younes Jaaidi

Software Engineer & trainer at Marmicode · Google Developer Expert

Younes is a software engineer, trainer and author behind Marmicode. A Google Developer Expert, he helps teams write tests that actually protect them: behavior-focused, refactor-proof, and honest about bugs.

In this session he puts two testing strategies head to head on the same AI-assisted change, then shows how Charted Coding keeps testing at the center so review stays sane.

TestingVitestAngularFakesCharted Coding
Good to know

Before you join.

Is the webinar free?

Yes, completely. There is no fee and you do not need a conference ticket. Just register with your e-mail.

What will we cover?

We run the same change twice on an Angular app tested with Vitest, once on mock-heavy tests and once on behavior-focused tests with fakes and object mothers, then compare the diffs and introduce Charted Coding.

Do I need to prepare anything?

No setup is required. This is a live demonstration, so you can follow along without coding. Basic familiarity with testing and Angular will help you follow the examples.

Who is it for?

Developers, tech leads and teams who rely on tests and AI assistants, and who feel the review burden that comes with mock-heavy test suites.

When does it take place?

The webinar takes place on Thursday, 5 November 2026 at 17:00 CET (Europe/Warsaw). The live session lasts one hour.

How do I join?

Register with your e-mail in the form above. You will receive the link to the live session by e-mail, plus a reminder before we start.

Ready? Free

Save your free seat for Thursday, 5 November.

Takes 10 seconds. You only need an e-mail address.

Save my free seat