Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Test Coverage

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.

Karumi

June 21, 2016
Tweet

More Decks by Karumi

Other Decks in Technology

Transcript

  1. 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
  2. Low level coverage says that the code is badly tested,

    but you cannot claim the opposite with just high level coverage
  3. Force to minimun code coverage could be a mistake. You

    can increase the coverage of your code without adding a single assertion.
  4. Risk-based Testing Prioritize the test over the risk of failure,

    the importance and the impact of failure
  5. 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
  6. Adam Tornhill “Creating tests in an environment where they have

    some Control over their own Destiny.” Uncle Bob
  7. Adam Tornhill “When you are very thirsty, even dirty water

    will keep you alive.” J. B. Rainsberger
  8. Refactor your code to increase the testability. Write temporary tests

    just to help you during the refactor (increase your confidence)
  9. 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