Testable design impacts the ability to test the application properly. As such, testers have an obligation to understand how code impacts it and improve it.
Everyone agrees testing is good for quality. But to change the code just so you can test it? That would break up the developer’s perfect design! Just to make the tester’s life easier! And if developers expose inner data to the test, another not-so-smart developer will eventually call it and will blow up the world!
Code doesn’t become testable by itself, we have to make it like that. And that conflicts with developer ideas of good design and how code should look. In this workshop I’m going to discuss the false beliefs about testability, and how testers can discuss them with developers.
We’ll go through patterns in code that impact testability, decide how best to fix them, and what benefits we can get. In the grand scheme of things, if developers want their code to work, it should be testable. Making those changes are not even a sacrifice for testability - they are good for everyone.