Testing, Debugging, and Verification - Testing, Part II

More documents

Recommendations

Info

Reflection: Extreme Testing ◮ JUnit designed for Extreme Testing paradigm ◮ Extreme Testing part of Extreme Programming (but not depending on that) TDV: Testing /GU 121130 24 / 28
Reflection: Extreme Testing (cont’d) A few words Extreme Programming (no introduction here, but see [Myers], Chapter 8) ◮ Extreme Programming (XP) invented by Beck (co-author of JUnit) ◮ Most popular agile development process ◮ Must create tests first, then create code basis ◮ Must run unit tests for every incremental code change ◮ Motivation: ◮ oo programming allows rapid development ◮ still, quality is not guaranteed ◮ aim of XP: create quality programs in short time frames ◮ XP relies heavily on unit and acceptance testing TDV: Testing /GU 121130 25 / 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: Compile and Run JUnit test class Al
Page 27 and 28: Extreme Testing Example: Class Mone

Testing, Debugging, and Verification - Testing, Part II

Create successful ePaper yourself

Delete template?

Save as template?