ThesaHelp: references t-z
Group: testing
Topic: test data selection
Topic: software review
Topic: decision table
Topic: program statistics
Topic: software metrics
Group: repetitive control
Topic: programming without errors
| |
Reference
Yamaura, T.,
"How to design practical test cases",
IEEE Software, November/December 1998, pp. 30-36.
Google
Quotations
30 ;;Quote: Hitachi catches 99.8% of bugs; documents test cases before debugging and testing
| 32 ;;Quote: at Hitachi, development and QA use different test cases
| 32 ;;Quote: need one test case per 10-15 LOC; can design 100 test cases per day
| 32+;;Quote: run 10 test cases per day during code inspection, and 25 per day during machine debugging
| 33 ;;Quote: design test cases to cover all the features; use a matrix-based test sheet and eliminate redundant cases
| 33+;;Quote: a matrix-based test sheet works well because it redesigns the software as a decision table
| 33 ;;Quote: for white-box testing, count IF statements instead of LOC; measures the number of executable paths
| 33 ;;Quote: loops are the most error-prone structure; test 0, 1, 2, average, max-1, max, and max+1 iterations
| 33 ;;Quote: 10% of test cases for boundary and limits, 15% for errors, and 15% for different platforms and performance
| 34 ;;Quote: run basic tests for 48-hours; catches memory leaks, deadlock, and time-outs
| 34 ;;Quote: catch 20% of bugs in code inspection; half of these from designing the test cases, half from the inspection
|
Related Topics
ThesaHelp: references t-z (309 items)
Group: testing (18 topics, 551 quotes)
Topic: test data selection (39 items)
Topic: software review (80 items)
Topic: decision table (29 items)
Topic: program statistics (27 items)
Topic: software metrics (32 items)
Group: repetitive control (7 topics, 117 quotes)
Topic: programming without errors (28 items)
|