Testing, Debugging, and Verification - Testing, Part II

More documents

Recommendations

Info

Extreme Unit Testing benefits: modules (classes) must have unit tests before coding begins ◮ You gain confidence that code will meet specification. ◮ You better understand specification and requirements. ◮ You express end result before you start coding. ◮ You may implement simple designs and optimise later while reducing the risk of breaking the specification. TDV: Testing /GU 121130 26 / 28
Extreme Testing Example: Class Money c l a s s Money { private int amount ; private Currency currency ; } public Money ( int amount , Currency currency ) { t h i s . amount = amount ; t h i s . currency = currency ; } public Money add( Money m) { // NO IMPLEMENTATION YET, WRITE TEST FIRST } Demo in Eclipse. TDV: Testing /GU 121130 27 / 28
Page 1 and 2: Testing, Debugging, and Verificatio
Page 3 and 4: V-Model Requirements Analysis Archi
Page 5 and 6: Discussion: Testing Levels of a Sys
Page 7 and 8: Regression Testing Orthogonal to th
Page 9 and 10: Test Cases The science of testing i
Page 11 and 12: ‘Success’ vs. ‘Failure’ of
Page 13 and 14: Test Set A test set TS m for a (Jav
Page 15 and 16: Test Oracle, Remarks While O is in
Page 17 and 18: Automated and Repeatable Testing (c
Page 19 and 20: Basic JUnit usage public c l a s s
Page 21 and 22: Basic JUnit usage JUnit can test fo
Page 23 and 24: Compile and Run JUnit test class Al
Page 25: Reflection: Extreme Testing (cont

Testing, Debugging, and Verification - Testing, Part II

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?