Test shift left and right

Test left shift and test right shift understanding

Understanding of testing ：

1、 Testing is the cost center in the team , What is cost center ？ Generally speaking, from the perspective of superiors , Or from the perspective of company executives , The fewer people in the test team, the better .

2、 How can we win more benefits or better development prospects for the testing team ？ Then we need to Expand the cognition of the boss ： Let the boss treat the test team as a cost that must be paid , Becoming an accredited testing team can also bring more value .

Namely Does the test have to wait until the end to do some necessary checks ？ If we only do the necessary checks , Then the boss is willing to pay very little money in testing . But if we tell the boss ： We can move the test to the left 、 Push forward , We can help product managers improve the quality of output requirements ; Let fewer product managers be used in the project , Give higher quality requirements , Make users more satisfied —— Then the value will be much greater .

Pull through the pain points of superior management , Clarify the team's goals , We should do well   R & D leadership communication , Product leaders 、 Communication from the project manager to the team 【 Test leadership vision 】

The premise of communication is not PK The volume , It's based on facts , Analyze with data , Smart leaders communicate calmly .

Test shift left test shift right ：

For software products , The traditional quality mode moves left and tests Move right Be endowed with more connotation , Also assume more responsibilities .

■  Test shift left ： Test shift left , In essence, it is to find and prevent problems earlier with the help of tools and testing methods .

• demand ： On demand 、 Testing of architecture and design models ;
• Development ： Focus on adding pairs of units 、 Component and service layer testing ;
• Keep testing ： automated testing .

■ Test move right ： For test students , After the version goes online, we need to continue to pay attention to online monitoring and early warning , Find problems in time and follow up to solve them , Minimize the impact .

• Grayscale Release ： New version online test ;
• monitor ： Reasonable performance monitoring 、 Data monitoring and early warning mechanism ;
• User feedback ： Online problem solving 、 Tracking mechanism .

Test the output direction ：

1. Test task tracking

2. Establish code branch management specification

3. Code quality check

4. Keep testing ： be based on XX The platform realizes interface automation

The principle of test moving to the left supports the test team to work with all stakeholders early in the software development cycle . So they can clearly understand the requirements and design test cases to help the software “ Fast failure ”, Urge the team to modify all the... Earlier bug.

Participation and understanding will enable testers to acquire complete knowledge of the product , Think through all the scenes , Design real-time scenarios based on software behavior , These will help the team identify some defects before coding is completed

What activities can improve the upper limit of quality （ give an example ）：

Healthy project process （ Reasonable and strictly followed project process ）
Reasonable demand analysis （ Evaluate the quality of requirements , Analyze the rationality and integrity of requirements ）
Excellent system architecture
Complete system design （ Evaluate the quality of the design , Analyze the rationality and integrity of requirements ）
Make full use of static code scanning
Define R & D Standards
Earlier test analysis （ Complete the analysis of requirements before development , Prepare for various reviews ）
Test execution as early as possible （ Participate in test execution in advance , Some problems were found before integration ）
What activities can improve the lower limit of quality （ give an example ）：

Healthy testing process
Excellent test cases
Reasonable test plan
Appropriate automation
Appropriate exploratory testing
Development self testing （TDD、BDD, Testing provides better use cases 、 Technical support ）
Cultivation of team quality awareness
 

For test shift right , Online monitoring can be a breakthrough , give an example ：

Closed loop online problem feedback - Check - solve - Update process
More convenient log viewing 、 Return service
Rich and effective log, Facilitate the rapid positioning of problems
Rich monitoring indicators （ For example, business outlier indicators ）
Cost monitoring （ For example, SMS sending ）
Key indicators are monitored daily （ Server metrics ）
Production data monitoring （ alert ）（ adopt sql Statement to realize production data monitoring , For example, whether there are multiple orders with the same order number ）
So for the test, move right , I think we can give feedback around the problem 、 Find out 、 location 、 Monitor deployment , The participants are not limited to operation and maintenance personnel