Test Coverage

One important part of testing process is choose what portion of your software must be cover with tests. The status of your software, your business and your knowledge have an impact over it.

Transcript

1. Test coverage Jorge Juan Barroso Carmona jorge@karumi.com @flipper83 +JorgeJBarroso Android Expert Android GDE
2. Basho. Poet Karumi is the beauty of ordinary things spoken of in a simple way.
3. Adam Tornhill “Testing is the process of executing a program with the intent of finding errors. ... This definition of testing has many implications ... it implies that testing is a destructive process, even a sadistic process, which explains why most people find it difficult.” Glenford J. Myers
4. Why do we need to write tests?
5. It is your responsibility
6. The only way to makes a refactor
7. it’s really good live Documentation
8. it’s a tool for Design
9. it’s Money
10. “Bad code affect to your Costumer” Martin Fowler
11. How do we decide when the coverage is good enough?
12. Low level coverage says that the code is badly tested, but you cannot claim the opposite with just high level coverage
13. Force to minimun code coverage could be a mistake. You can increase the coverage of your code without adding a single assertion.
14. Tests are Code, we need to maintain them
15. Risk-based Testing Prioritize the test over the risk of failure, the importance and the impact of failure
16. Add test coverage to the code that is important for your business
17. Tests are a good way to design complex systems.
18. Adam Tornhill “I get paid for code that works, not for tests, so my philosophy is to test as little as possible to reach a given level of confidence” Kent Beck “In most businesses, the only tests that have business value are those that are derived from business requirements.” James O Coplien
19. From scratch
20. Choose a good scope for you tests
21. Expose all your dependencies
22. Test inputs and output. Test how you software works, do not test the implementation
23. Adam Tornhill “Creating tests in an environment where they have some Control over their own Destiny.” Uncle Bob
24. Testing old code
25. Adam Tornhill “When you are very thirsty, even dirty water will keep you alive.” J. B. Rainsberger
26. Your current architecture could be mark the test scope
27. Refactor your code to increase the testability. Write temporary tests just to help you during the refactor (increase your confidence)
28. Start by testing classes that do not have a lot of dependencies
29. Reproduce your bugs with a test. Then fix it.
30. Don’t write flaky tests
31. Bibliography They’re the cracks! Adicto Al verde. Joaquin Engelmo Elegant?? Unit Testing. Pablo Guardiola Working Effectively with Unit testing. Jay Fields Software Craftmanship. Sandro Mancuso Mocks Aren't Stubs. martin fowler. 2007 Software Reliability: Principles & Practices. Glenford J. Myers 1976 The Art of Unit Testing. Roy Osherove Test Driven Development: By Example. Kent Beck
32. Find me I am very social! jorge@karumi.com @flipper83 +JorgeJBarroso Questions?