Details of the eight stages of the Software Testing Life Cycle:

Evolution:

1960s:

90s Years:

2000:

Testing trends and capabilities are changing all the time. Testers are now asked to do more technical and process-oriented things. Testing is now not only limited to finding bugs, but also has a broader scope of work. It is needed and arranged from the beginning of the project even before the requirements are formally determined.

Testing is also standardized. Just like software development has a life cycle, testing also has its own life cycle. In the following content, I will discuss what the testing life cycle is and how software testing is related.

What is life cycle?

The simple word "life cycle" refers to a series of changes from one form (state) to another. These changes can occur in tangible or intangible things. Every entity has a life cycle, from beginning to death/end.

Similarly, software is also an entity. Just like developing software consists of a series of steps, testing also has many steps, and these steps are executed in a certain order.

The systematic and planned execution of testing activities is called the testing life cycle.

What is Software Testing Life Cycle (STLC)

It refers to the testing process. This process is a series of specific steps executed in a certain order to ensure that product quality meets requirements. In the STLC process, each activity is executed systematically according to the plan. Each stage has different goals and deliverables. Each organization has different stages in STLC; but the basics are the same.

The following are the 8 stages of STLC:

1. Requirements phase (Requirements phase)

2. Planning phase (Planning Phase)

4. Design Phase (Design Phase)

5. Implementation Phase (Implementation Phase)

6. Execution Phase (Execution Phase)

7. Conclusion Phase (Conclusion Phase)

8. Closure Phase (Closure Phase)

#1. Requirements Phase:

At this stage, it is the stage of analyzing and learning needs. Brainstorm with other teams and try to find out whether the requirements are measurable. This stage helps identify the scope of the test. If any feature is untestable, communicate it promptly and make plans for some mitigation strategies (risk reduction).

#2. Planning phase:

In actual scenarios, test planning is the first step in the testing process. In this phase we identify which activities and resources match the testing objectives. We also work hard to identify test metrics, testing methods, and how to track these metrics.

What is the basis of the plan? Is it just demand?

The answer is NO. Requirements are only a basis, but there are two other factors that affect the test plan. They are:

-Organizational Testing Strategy

-Risk Analysis/Risk Management and Mitigation

#3. Analysis Phase:

STLC defines "WHAT" to be tested. Generally, we identify test conditions through requirements documents, product risks, and other test basis. Test conditions should be traceable back to requirements.

There are many factors that can affect the identification of test conditions:

-The level and depth of testing

-The complexity of the product

-Product and project risks

-The software development life cycle is involved

-Test management

-The knowledge and skills of the team

-The availability of relevant stakeholders

We should strive to write down the test conditions in a very detailed way. For example, an e-commerce website, you have a test condition as "Users should be able to pay". Or you can describe it in detail as "Users should be able to pay via credit card, WeChat, Alipay, etc." The biggest advantage of writing down detailed test conditions is that it can improve test coverage, because test cases are written through these test conditions, and these details trigger the writing of more test cases. At the same time, you can also identify the criteria for exiting the test, such as which conditions determine whether the test can be terminated.

#4. Design stage:

This stage has "HOW" to test. Tasks include the following:

-Details the test conditions. Split test conditions into multiple sub-conditions to provide coverage.

-Identify and obtain test data

-Identify and build test environment

-Create requirements tracking indicators

-Create test coverage indicators

#5. Implementation phase:

The main task of this phase is to create detailed test cases. Prioritization of test cases and which cases will be part of regression testing. It is very important to review the test cases for correctness before finalizing the decision. At the same time, don't forget to sign off the test case before the actual execution begins. For example, the final test report before the release of a new version needs to send a sign off report. If your project is designed to be automated, identify which use cases are suitable for automation and prepare test scripts. Don’t forget to review.

#6. Execution phase:

As you can know from the name, this phase is the real execution phase of STLC. But before you implement it, make sure your standards match your needs. Execute test cases and report bugs if there are any mismatches. Also fill in tracking metrics to track your progress.

#7. Summary phase:

This phase focuses on inspection standards and reports. Depending on your project and stakeholder selections, you can decide whether to publish daily or weekly reports, etc. There are different report types (daily, weekly) you can send, but the point is, the content of the report changes depending on who you send it to. If the project manager has a testing background, then they are more interested in technical aspects, so the report includes technical aspects (number of pass cases, number of failures, number of bugs, serious bugs, etc.). But if you report to higher-level stakeholders, who may not be interested in the technical aspects, you can send them some risk-related information, such as mitigating the occurrence of risks through testing.

#8. Ending phase:

The tasks of this phase include:

- Check the completion of the test. Are all use cases implemented or are some intentionally mitigated. Check if there are still S1 bugs that are active.

-Experience summary meeting and writing related documents. Including what is done well, what needs to be improved and how to improve it

Summary:

Let’s summarize STLC together.

Link: /p/21b84e176e12