This document explains the different stages of the testing life cycle. It contains what documents have to be made, how to design, review and execute test cases, how to work with the defects found and the deliverables of the testing cycle.
First, we need to know the responsibilities of a tester. A tester hast to be involved in all the development life cycle. The tester has to become familiar with the software under test, generate test cases based on requirements, test software releases, create test logs, report defects, report work progress and some more. I won’t mention them all, but basically, the tester has to communicate with the other teammates and support them, search new tools or information to be always up-to-date and report the good things and bad things.
The testing life cycle goes as follows:
· System study
· Test plan design
· Test case design
· Test case review
· Test case execution
· Defect Handling
· Gap analysis
At first, we need to make documents specifying the characteristics of the system and resources. For example: domain knowledge, software, hardware, functional points, priority, etc. In the next stage we need to specify what is going to be tested and what isn’t, as well as estimating the time needed for the tests based on resources, lines of code and focal points.
A test plan design has to be made. I consider this the core of the testing cycle. This document has to contain all the information of what we’re going to do, roles and responsibilities, schedules, scope, about the client and company, deliverables, defect definition, testing approach and some more. This is going to be the base document of what’s going to be made. This is our master plan.
The next three stages are for test cases. The document explains what a test case is, what it contains, and characteristics of a good test case, issues you may encounter and examples. It is a brief explanation to create test cases. It also explains the review process of a test case and the execution process.
After the test cases, we have to handle the defects found. The document includes information about what a defect is, types of defects, severity and who can report them. Also, the document shows a diagram of the defect life cycle.
At the very end there are the deliverables. These are all the documents made in previous stages of the cycle.
I liked this document because it includes examples and formats of what has to be made during the testing life cycle. These examples help as a guide and to understand better the explanation. This is a brief document to understand the testing process.
Javier Rojas D.