Let me talk to you today about what is test shift left and what is test shift right? First of all, before talking about this topic, what is the traditional software testing process and the current practice of many companies?
Generally, participate in the requirements review, and then write test cases according to the requirements documents. After the development and testing, conduct the smoke test, raise bugs, retest, and return, and then develop and maintain online, and then start the next project, repeating the above process.
So what are the disadvantages of this traditional testing process?
For example, when the product documentation is incomplete and the requirements are not clear, or the development level is relatively low, the delivery quality is poor, and the main process of the smoke test is not passed, then your test efficiency will be very low, and if it is more serious, the test may be delayed due to incomplete testing.
Another situation is that after your software goes online, once there are some production problems that do not hinder the process, because they are relatively hidden, by the time they are discovered, it may have passed for a long time.
At this time, the discoverer of the production problem is likely to come from customer complaints or business discovery, then the problem will eventually rise to QA, and then there will be various review meetings. Whoever experiences it will know how uncomfortable it is!
So, in order to fundamentally reduce the occurrence of such problems, this is why some big manufacturers have started to promote and practice test left shift and test right shift? Next, let’s talk about what is test shift left and what is test shift right?
First of all, let’s talk about the left shift of the test. In a word, the left shift of the test is to intervene in the test before the test is proposed.
In the requirements review, it is not just to understand the requirements, but to evaluate the quality of the requirements, analyze the rationality and completeness of the requirements.
In the development stage, they should also participate in the design of the design scheme and understand the implementation method of the development. Because many developers may only be familiar with the part he is responsible for, as a test, it is necessary to evaluate the scope of changes and whether there are missing modules and systems.
Testing can also be provided to development by providing test cases or automated test scripts, so that development can be considered more comprehensively during design, and at the same time, it is convenient for development to conduct self-test during coding, which helps to improve product quality. After all, the earlier problems are found, the lower the cost of solutions.
Test students also need to continuously cultivate products and develop students' quality awareness, and at the same time provide necessary technical support to assist products and develop better tests, such as public use cases, test tools, and test scripts.
In this way, you will find that the quality of the test is greatly improved. Originally, you still need to spend a day to conduct the smoke test after the test, but now it can be completed very quickly.
Next, let’s talk about what is the test right shift. In a word, moving the test to the right is to focus on the status after the product test is completed and launched, rather than thinking that it has nothing to do with you after the launch is completed.
For example, there are mainly the following ways to pay attention to the status after going online:
Through online monitoring and early warning, problems can be found in time and followed up to solve them, so as to minimize the scope of impact. The early warning function should be considered during development and design. When there is an abnormality in the system layer (such as CPU and memory problems), application layer (such as response time), and business layer (such as registration rate, transaction volume), etc., an early warning will be sent by email, so that relevant students can know where the problem is.
Test students can supervise the development of supplementary monitoring and early warning functions, and at the same time pay attention to daily monitoring and alarming, so as to respond in the first time.
Another is to focus on online business and user usage, pay more attention to functions with high user value and high usage rate, supplement missing scenarios in use cases, and cover as many functions as possible.
Whether the test is shifted to the left or the test is shifted to the right, it is for the product quality. Don't think that the test is the beginning of the test activity, and the online is the end of the test activity, and don't think that the quality is only what the test students need to pay attention to.
Finally, I would like to thank everyone who has read my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, you can take it away if you need it:
These materials should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey, and I hope it can help you! Friends in need can click on the small card below to get it