Abstract: If there's one technical agile practice that everyone has a different opinion about, it's testing. The debate between the Chicago (no mocks) and London (mocking) schools of thought has been going on for more than a decade! Some claim that if you believe in POs and BAs writing acceptance tests with Gerkhin you're living in fairy land. Others that writing automated tests is a waste and that cheap QAs should catch all the bugs instead. And just to name a few influencers on opposites of the spectrum: @DHH thinks TDD is dead; while @KentBeck wishes there were more examples of what not to test!
We see a lot of value in TDD and BDD but are not blindly obsessed with these practices. We don’t question the value of having tests for your project, but we do question the value of testing absolutely everything. Over the years, we've discovered that deleting tests is just as important as writing them!
In this workshop, you will see real examples of tests we've seen (or written ourselves) that we don't believe add value to your test suite. You will also have a chance to discuss why you would delete, rewrite or rethink these tests
Learning Outcomes: - You'll leave our session with an informed opinion on what not to test in your project and, who knows, maybe you’ll even start deleting some of your tests. What’s more, you'll better understand how to test what is essential.
Attachments:
