SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
4.
Checking is confirmation, verification, and
validation. By machines.
Testing is exploration, discovery,
investigation, and learning. By humans.
versus
27.
Low level coverage says that the code is badly
tested, but you cannot claim the opposite with just
high level coverage
28.
100% coverage is to test all possible code paths.
Is TDD here?
Tests are Code, we need to maintain them.
29.
Risk-based Testing: prioritize the test over the
risk of failure, the importance and the impact of
failure.
30.
“ 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
36.
“ If you find your testers splitting up functions to support the
testing process, you’re destroying your system architecture
and code comprehension along with it. Test at a coarser
level of granularity. ”
James O Coplien
“ When you are very thirsty, even dirty water will keep you
alive. ”
J. B. Rainsberger
37.
+ James Bach and michael bolton. checking vs testing (2009 -
2013)
+ Workflows of Refactoring. martin fowler. (oop 2014)
+ Why Most Unit Testing is Waste. James O Coplien (2013)
+ 467 tests, 0 failures, 0 confidence. Katrina Owen (Railsberry
2013)
+ Mocks Aren't Stubs. martin fowler (2007)
+ Integrated Tests Are A Scam. J.B. Rainsberger (2013)
+ Exploratory and Risk Based Testing. Bach, J. Kaner, C. (2004)
+ Decomposing into modules. D.L. Parnas (1972)
+ The Art of Unit Testing. Roy Osherove
+ Test Driven Development: By Example. Kent Beck
+ UnitTest. Martin fowler 2014
References