Page 158 - SOFTWARE TESTING & QUALITY ASSURANCE
P. 158
Unit 10: Test Planning Fundamentals
There are many software scheduling products that will make this process easier to manage. The project
manager or test manager is responsible for the schedule and is likely to use such software scheduling
products to create test schedules.
10.7 Test Cases
The test case is the heart of a test plan. A test case is a document that describes a set of data inputs and
operating conditions required to run a test, together with the expected results of the run. The tester
should run the software according to the test case documentation and then compare the actual results
with the expected results noted in the documents. If the obtained results are in complete agreement
with the expected results, then it indicates that no error has been identified. The result of such a test case
is said to be ‘pass’. A potential error is said to be identified when some or all of the results do not agree
with the expected results. In such cases, the test case will have the status ‘fail’.
Table 10.3 Example of a Test Case
Test Test Name Description Expected Results Pass/Fail
Case No.
1 C6455_SA112 on Linux. Run the previous voice The script runs
Tests the voice channel fax Sample Application successfully.
with the new out file version with the new Good quality voice is
version and the previous out file version. heard in both legacy
Sample Application Run the voip1.txt script. phones.
version.
2 C6455_SA112 on Linux. Run the previous voice The script runs
Tests the fax channel with fax Sample Application successfully.
the new out file version version with the new Fax pages are transmitted
and the previous Sample out file version. from both fax machines.
Application version. Run the foip1.txt script.
Test cases will be discussed in detail in the subsequent sections.
10.8 Bug Reporting
Bug reporting is the process of describing the problems found during the execution of the test case.
These could be done on paper, but using a database to track them is a lot easier and efficient. It is
important to plan the process used to manage the bugs so that every bug is tracked from the point it is
found to the point it is fixed. More will be discussed about bugs in subsequent sections.
10.9 Metrics and Statistics
Metrics and statistics are the means by which the development and success of the project and the testing
activity are determined. The test planning activity should exactly determine what information will be
gathered, what decisions will be taken, and who will be responsible for gathering them.
Test metrics help us analyze the current progress in testing and give directions on how to proceed with
the testing activities. They also allow us to set goals and predict future developments, and act as a
feedback mechanism to improve the testing process.
LOVELY PROFESSIONAL UNIVERSITY 151