Getting maximum value from a minimum number of tests, with e2e component tests

About the session

This talk introduces, explains and demonstrates an approach to automated testing which covers as much of the surface area of your codebase as possible.

Imagine a unit test where the 'unit' is actually multiple executables! A single test can cover the whole happy path flow of a complex piece of orchestration, from API handlers, service bus handlers, database calls etc all in-memory, fast and with a nice fluent developer experience!

Because everything including the Program.cs and startup code are covered we can spot configuration and IoC issues which are hard to test with more traditional methods. I include a method of mocking and asserting against Azure Service Bus