Scribd
Upload
44 views3 pages

STLC Notes

The Software Testing Life Cycle (STLC) consists of several stages including system study, test planning, writing test cases, preparing a traceability matrix, test execution, defect tracking, and generating test execution reports. After testing, a retrospective meeting is held to discuss achievements and mistakes, which informs future planning. Each stage is crucial for ensuring thorough testing and documentation throughout the software development process.

Uploaded by

2111CS010077 - SHAIK AZEED
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
44 views3 pages

STLC Notes

The Software Testing Life Cycle (STLC) consists of several stages including system study, test planning, writing test cases, preparing a traceability matrix, test execution, defect tracking, and generating test execution reports. After testing, a retrospective meeting is held to discuss achievements and mistakes, which informs future planning. Each stage is crucial for ensuring thorough testing and documentation throughout the software development process.

Uploaded by

2111CS010077 - SHAIK AZEED
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

STLC (Software testing life cycle)

1. System study:
Read the requirement, understand the requirement and if you have any
queries, interact with BA, developers or customer.

2. Prepare Test plan:


Once after reading and understanding the requirement, we go for
preparing the test plan.
Test plan is a document which drives all the future testing activities.
-Here we decide how many engineers we require to complete the testing.
-What is the total time for completing the testing/project.
-What each engineer should do in different stages of testing.
-What are types of testing we will conduct in future.
-What are the features that are to be tested and not to be tested.
-What is the testing approach
-When each activity should start & end.

3. Write test cases:


Test case is a document which contains all possible scenarios.
This activity has got several stages like:
System study, identify all possible scenarios, write test case, review test
case, fix the review comments, verify the fix, test case approval, store in
repository.

4. Prepare traceability matrix:


Once after we write test case, the biggest question is what is the proof
that each and every requirement has got atleast one test case?
So,we prepare traceability matrix to ensure that each and every
requirement has got at least one test case.

5. Test Execution:
This is the stage where we execute all the test cases.
This is where we conduct all types of testing and find the bug.
This is the stage where Test engineers become productive to the
organization.
This is the stage where the T.E spends a lot of time.

6. Defect tracking:
Once after test execution, obviously we are going to find the defects.
Each defect that we find should be tracked in an organized way. This is
called as Defect tracking.

7. Test execution report:


At the end of every test cycle, we prepare test execution report.
It is a document which we prepare and provide to the customer at the end
of every test cycle.
This report covers:
*Total no. of test cases
*Total no. of test cases executed.
*Total no. of test cases not executed.
*No of test cases passed.
*No of test cases failed
*What is the pass percentage
*What is the fail percentage.
We will prepare this document and send it to the customer. From
customer’s POV this is the last stage. But from company’s POV we have
one more activity called as Retrospective meeting.

8. Retrospective meeting/Project closure meeting/Post-mortem


meeting:
Here the entire team will sit together and discuss about the achievements
and mistakes, they document all this, that document is called as
Retrospect document.
In the next release/sprint they open this document in the planning stage
and plan in such a way that all the achievements are adopted and all the
mistakes are avoided.

You might also like