Integration testing,told from the evidence.

Ask a .NET team about their unit tests and you hear numbers: coverage, speed, how many. Ask about their integration tests and you hear complaints. Yet the integration tests are the ones that catch the bugs that matter: the API that writes something the UI never shows, the message that arrives twice, the job that runs at the wrong time.

I kept hearing the same three complaints, and I kept having them myself. ProtoTest is my answer to all three.

A few weeks after I released ProtoTest 1.0, I deleted the LinkedIn post that announced it. Nothing had crashed. No one had complained. I deleted it because, reading my own docs again, I no longer agreed with them.

This post is about what was wrong, what I changed for 1.1, and the rules I work by now.