Lots has been said about how to write testable code and about the importance of dependency management. But practically no one talks about how to write tests themselves. Why in some projects tests serve as documentation, and in others they only complicate maintenance? What to do if tests are being written, but the percent of code coverage is not increasing? How to turn a routine description of test cases into a creative process which is clear for all the team? The point of the talk is to answer these and many other questions, show the audience how to write readable and simple-to-maintain tests forming engineering culture.
Delivery Club Tech