Lecture 5 - The Software Testing Life Cycle -> Quick Intro -> Research -> Test Planning -> Test Execution -> Test Education And Reality
The gist of test case execution is conducting a practical search for bugs in the code by using test cases that we’ve created during the previous stage.
First, we perform new feature testing, using new test cases. As you recall, new test cases are often modified during their first execution.
Second, we perform regression testing, using old test cases.
During both new feature testing and regression testing, we try to find bugs. Remember:
– Once a bug has been discovered, the tester should file a bug report, entering it into the bug tracking system.
– After a programmer fixes the bug, the tester checks to see:
a. If the bug was really fixed – i.e., the tester tries to reproduce the bug.
b. If the activities during the bug fixing stage have unintentionally introduced new bugs – i.e., the tester does a quick test of the features that could have been affected
The testing performed during the steps a. and b. is also called regression testing. Thus, the expression “regress that bug” means that you have to perform the testing specified in those two steps.
Because the stages of Research and Test planning are intermingled, we’ll unite them into one body of knowledge called Test preparations, or Test preps for short.
Therefore, the majority of our future lectures will be dedicated to two things:
1. Test preps
2. Test execution Next ->
Lecture 5 - The Software Testing Life Cycle -> Quick Intro -> Research -> Test Planning -> Test Execution -> Test Education And Reality
