Stephan Schmidt - January 20, 2026
A New Kind of Testing
TL;DR: A new testing approach using backend E2E tests with user journeys instead of flaky UI tests. Write long tests modeling user journeys from registration through checkout using your backend usecases. Add custom DSLs for time manipulation like 'Fast forward 1 month' or 'Run overnight jobs'. The result: faster execution, deterministic results, and easier test writing compared to slow, randomly failing UI E2E tests.
I’ve invented a new kind of testing. No really. Something I haven’t seen someone else do.
Not unit tests, not frontend end-to-end tests, not UI tests.
A new kind of testing.
Backend E2E testing with user journeys.
You write long tests that run some user journey, from registration, validation, buying something, checkout, delivery.
The code uses the usecases of your backend code to execute. It does use new code to glue those usecases together.
A test case uses usecases to model a journey.
You build a library of custom building blocks to build the journey with.
That can be reused.
You add a custom DSL, e.g. to manipulate time, “Fast forward 1 month” to check the future, or “Run overnight jobs” to see the effects of those jobs.
Not exactly what the user via the web does, but it still needs to work. If it works, there is a high chance that the web works as well.
The benefits?
Faster to execute.
Deterministic.
Easier to write.
For me this has changed everything.
From UI E2E tests that are slow and Heisenberg, who randomly fail for no reason to tests that are deterministic and fast.s
About me: Hey, I'm Stephan, I help CTOs with Coaching, with 40+ years of software development and 25+ years of engineering management experience. I've coached and mentored 80+ CTOs and founders. I've founded 3 startups. 1 nice exit. I help CTOs and engineering leaders grow, scale their teams, gain clarity, lead with confidence and navigate the challenges of fast-growing companies.
