Scribd
Upload
40 views4 pages

STLC

The Software Testing Life Cycle (STLC) is a structured process to ensure software quality through various stages, including system study, test planning, test case writing, requirement traceability, test execution, defect tracking, and reporting. Each stage involves specific tasks performed by test engineers and managers, culminating in a retrospective meeting to discuss project outcomes and improvements. The process emphasizes the importance of documentation and tracking to meet customer requirements and enhance future projects.

Uploaded by

iam.sharanyv
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
40 views4 pages

STLC

The Software Testing Life Cycle (STLC) is a structured process to ensure software quality through various stages, including system study, test planning, test case writing, requirement traceability, test execution, defect tracking, and reporting. Each stage involves specific tasks performed by test engineers and managers, culminating in a retrospective meeting to discuss project outcomes and improvements. The process emphasizes the importance of documentation and tracking to meet customer requirements and enhance future projects.

Uploaded by

iam.sharanyv
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

* STLC (Software Testing Life Cycle)

- It is a procedure to test the Software Application to ensure the


software meets quality standards. It has different stages (or)
phases.

1. System Study:

- It is going through the requirements given by the customer and


understanding how the system works.

2. Write test plan:

- It is a document which is prepared to execute testing activities


is done by test leads,test manager.

- Because the plan will be done by experienced people.

3. Write a test case:

- It is a step-by-step procedure to perform the testing on the


application.

- It is done by a Test Engineer.

- Once we go through the requirements we identify the scenario


and then convert into the test case.
- To write test case we need Requirement and test case
template (or) tool (Ex: qc or ALM, JIRA , FF) and this tool are
called repository.

4. Prepare RTM:

RTM stands for Requirement Traceability Matrix.

* It is a document which is prepared to check whether every


requirement has at least one test case or not.

* To prepare RTM, we need more requirement and test case.

* It is prepared by test engineers.

5. Execute the test case:

* Once the requirement is given to the test engineer, he writes the


test cases for the application.

* After the developer gives the developed application, then the


test cases are executed and it is compared with expected result
and actual result.
* If the expected and actual results are same the test case said to
be pass.

* If the expected result and actual result are not the same then the
status will be failed. This is called as Execute test cases.

* So here to execute, we need a test case and software


application.

* This is where exactly the software has been tested.

* This is the most important stage of Software testing Life Cycle.

6. Defect tracking:

- While executing the test cases we will find a defect, that defect
will be released to the developer.

- Test engineer should track what is happening to the defect this


process is defect tracking.

7. Test Execution Report:


* This report will tell about the total number of test case
executed.

* It will Also Tells How many Test Cases Are Passed and How
many Test Cases Are Failed.

* It will be prepared by test engineers and also By Test manager,


Test lead.

* This will be prepared between the project and also end of the
project.

* Till This Stage customer can involve and check all documents
this is the last stage from customer angle.

8. Retrospective Meeting (or) Postmortem Meeting:

- Once everything is completed all team members will gather


together like test engineer, developers,

test lead, development lead, manager, business analyst, etc.

- They will discuss about good things in the project and the
improvements to be made in the upcoming

project.

- This will be considered for future purpose.

You might also like