Skip to main content

Software Testing Life Cycle (STLC)

STLC indicate the flow of testing phases that how we will start our testing, what resources we used, what are test plans, what are test cases and the reports. There are some steps of Software Testing Life Cycle.


Software Testing Life Cycle, STLC, Software Testing Help, Manual Testing
Image Source Google


  • Project Initiation: This is first part of project and collect all information with the interaction with the client, view all existing information, old software to gather information to initiate the project. 
  • System Study: In This past, QA team study regarding the ER , SRS, Use Case, Design part. 
  • Test Plan: Test Planning is most important phase of STLC. Basically as per testing, this is the first phase of STLC. In this phase , Testing team consider all available resources and the activities to achieve the objective of the software. Also team management consider the efforts and cost of the project. This phase also called test Strategy Phase. In this phase we also identify the scope of the Project. 
  • Design Test Cases: This phase is occurred after the test Plan. In this phase, Test team write down all the Test Cases as per the detailed document. Along with the Test Cases, team team also include the test data as per requirement. In this phase, Requirement Traceability Matrix also prepared. In this phase Test Team break the condition to convert it in multiple conditions to increase the coverage.
  • Execute Test Cases: In this phase, Test Team will execute the Test Cases. This phase will occur when developer write their code and provide the built to the test team. In this phase, Test team take the input from Requirement Analysis and validate the output with the expected result. If Actual result matching with the expected result then Test Case consider as PASS otherwise Test Cases considered as FAIL. 
  • Report Defects: This phase is occur after the Test Cases execution phase. All FAIL Test Cases now be added in the Report and called them Bug. Test team added all these bugs into a report and assign that report to the Developer Team to fix those bugs.
  • Regression Test: This Phase is occur once developer fixes all your bugs then again developer assign the Bug report to the Team Team. Team team now verified all Failed Test Cases and along with the Failed Test cases, Test team verified the already Pass test cases to check weather to fix Failed Test cases may be some new error generated in Pass Test Cases. This is called Regression Test. 
  • Analysis: In this phase, Test team analyse all Test Cases to verified and validate the software with the client requirement. 
  • Summery Report: This is the exit criteria of the Team team. In this phase, team team verified the cost, Test Coverage, Quality, Time, Business objective and product. Team team discuss about the current STLC and discuss what's new added in the current STLC to make it better.


Comments

Popular posts from this blog

What is API?

In general way, API (Application Programming Interface) is the intermediate software which is useful for two applications to communicate. API is the tool which is used for interaction of two applications. If developer developing any software which have multiple blocks (Modules) than developer use APIs to put them together.

Ad-Hoc Testing

Ad-Hoc Testing is the testing type which is performed without any proper procedure and without any Requirement Specification. Ad-Hoc testing is totally informal testing which have intension to break the application as early as possible and found important defect early.  In Ad-hoc testing tester do not have any test cases so only the users who have very high knowledge regarding the application only they can perform Ad-Hoc Testing.

Integration Testing

When all small unit of code combined together or we can say integrate together then perform the testing between the interface of these units to verify that are these unit working fine when these are combined. Integration Testing occur after Unit Testing. In Unit Testing , developer concern only over the each module and fixes all error in that but developer not focused that what is the effect of bug fixes in other modules. Each Unit is developed by different different programmers so in Integration Testing, We will test the data communication between these Units.