Is the test cycle compressed? Teach you 9 ways to deal with it

In most projects , The milestone plan is inverted by the launch date , It is not evaluated in combination with the specific scope of the project , And the system testing stage usually belongs to the downstream of the R & D process , The upstream progress delay directly causes the downstream time to be compressed , Therefore, test students often face the problem of test cycle compression .

When the test cycle is compressed , It is impossible to complete the corresponding test work according to the original plan , So how to deal with it ？

Change testing methods and techniques to improve efficiency

For example, run automated tests earlier , Try to find problems in the early stage ; Use automated scripts for regression testing , Shorten regression test duration .

The original plan may be to manually perform regression tests , If the test cycle is tight , You can complete this part of the test task with the help of scripts .

This requires the preparation and maintenance of unit test scripts and system test scripts .

Work out

Consider that the originally arranged personnel work overtime , Whether the original planned test work can be completed , Including working overtime on weekdays and appropriate overtime on weekends .

If you work overtime , Pay attention to appropriate incentives and employee benefits , For example, apply for project bonus 、 Overtime pay 、 Invite everyone to have afternoon tea with the project funds 、 Dinner, dinner, etc .

Overtime should be appropriate , Overwork will lead to a decline in work efficiency .

Strive for more / More effective testing resources

Try to win test resources in terms of quantity and quality , One way is to add other testers , Or apply for development 、 Product personnel participate in the test , Pay attention to the allocation of test cases .

Another way is to apply for deployment of the system / The most familiar and experienced testers of the module join the project , It is possible that the student was originally assigned to other projects at the same time , In case of emergency, you can try to apply to your superior , Transfer experienced students .

Be careful not to blindly increase test resources , Join people who are not familiar with the system 、 New people 、 Temporarily hired outsourcing personnel will slow down the original test progress . Therefore, we should pay attention to when allocating requirements , It is better to have more than two familiar people in a module or system , Reserve personnel .

Reduce the scope of the test

If you work overtime 、 The way of increasing resources cannot ensure that the set tasks are completed within the set time , Then consider reducing the test scope .

This does not mean that some modules are put into production without testing , Instead, the project manager evaluates the function modules with lower priority , Communicate with the business whether it can be put into production in the next version , Give priority to ensuring the stable launch of important functions .

For example, for e-commerce system , You can turn off the integral function first , In the later stage, arrange time to fully test the integration function before putting into production . This requires attention to the configuration of various functions in the design , It can realize free switching .

Clarify the priority of test cases

If the test time is tight , Give priority to the test cases with high priority , Leave special scenes and abnormal scenes for later execution , This requires us to pay attention to the layering of test cases when designing test cases , And the unexecuted use cases should be explained in the test report .

Strengthen quality and progress control and follow-up

The more tense the test time is , The more the person in charge should strengthen follow-up and control , Monitor test quality and efficiency in a timely manner , Avoid and correct problems , Avoid serious deviations .

Record relevant risks and suggestions

Specify the test scope in the test report 、 Not online 、 Uncovered test cases, existing risks and Countermeasures .

If there are unexecuted test cases , It is necessary to arrange the test time and resources in the future .

Make a test summary

The final summary is easy to forget . Response to test cycle compression , What are the good and bad things to do , The group can summarize in time , Learn from experience , Then you can deal with similar situations calmly .

Early control

We all know that testing should not be involved in the system testing stage , In the demand stage 、 design phase 、 Coding stage , Test students should give full play to the advantages of the test , Discover possible defects in advance , Avoid relevant problems and risks , The quality is improved , The testing process can be efficient . Otherwise, the project will be in a mess , Code quality is a mess , Even if more manpower and resources are invested in the testing stage , There is nothing to mend .

When the test students encounter the compression of the test cycle , Be clear about priorities . Not only the priority of functions , And the priority of use cases , If there are few bullets , It's more important to fight accurately , Concentrate on important tasks , At the same time, we must overcome anxiety .

How to deal with the compression of test cycle is also how to balance the time 、 cost 、 Range 、 Relationship between quality , It is consistent with considering the input-output ratio at all stages of the project .

secondly , As can be seen from the side , Only by doing basic work well at ordinary times can we calmly deal with special situations , Such as system design 、 unit testing 、 Test design 、 automated testing 、 Personnel reserve, etc , Everyone always feels nervous about the project , These unimportant tasks can be put aside , Norms can be slowed down , Little does it know that it actually reduces the delivery efficiency , At the same time, it also makes the project fall into a vicious circle .

Last ： It can be in the official account ： Sad spicy bar ！ Get one by yourself 216 Page software testing engineer interview guide document information 【 Free of charge 】. And the corresponding video learning tutorial is free to share ！, It includes basic knowledge 、Linux necessary 、Shell、 The principles of the Internet 、Mysql database 、 Special topic of bag capturing tools 、 Interface testing tool 、 Test advanced -Python Programming 、Web automated testing 、APP automated testing 、 Interface automation testing 、 Testing advanced continuous integration 、 Test architecture development test framework 、 Performance testing 、 Safety test, etc. .

I recommend one 【Python Automated test communication group ：746506216】, We can discuss communication software testing together , Learn software testing together 、 Interview and other aspects of software testing , Help you advance quickly Python automated testing / Test Development , On the road to high pay .

Friends who like software testing , If my blog helps you 、 If you like my blog content , please “ give the thumbs-up ” “ Comment on ” “ Collection ” One Key triple connection ！