Do software testing favorite often encounter such problems, demand is due to product changes or is a research and development of the measuring time delay led to a predetermined test time is serious compression, but due to the operation in advance has been made a new version of the propaganda, on-line time remains the same, then test the children’s shoes how to take the test strategy, quality is directly related to look forward. This article describes in two steps how testing should be done to minimize the risk of going live.

90% test engineer will skills: http://yun.itheima.com/map/72.html?1912zzp

1. Step 1 ————– Analyze the changes of the version to be tested

The target

Analyze the changes to the version under test to find out the focus of the test

steps

1. Draw a test mind map for new features in the beta version, and list only the test cases with the highest priority

2. Test and check product requirements with R&D to ensure that R&D correctly understands product requirements; otherwise, it will take much longer to change and iterate than expected

3. Identify all the bugs of the software to be tested

4. Ensure that the software under test does not have any spontaneous code optimization behavior developed outside the new requirements of the product manager

2. Step 2 ————— Adopt specific test strategies according to the changes

The target

Test priorities in a prioritized strategy to ensure coverage of the most important test scenarios in limited time

The test strategy

1. The first step is to test the use case with the highest priority in the new function of the software to be tested

2. Step 2 Verify whether the modified bug in the software to be tested is corrected

Step 3 test the history core functionality

4. Step 4 verify scenarios associated with new features and bug fixes

5. If necessary, develop and modify the bug directly on the master branch to speed up the iteration time

conclusion

The biggest test is when the test time is severely compressed, considering that the only reason for a new release of software is to add new features and fix bugs from the previous release. Therefore, when time is limited, the strategy other than working overtime is to test important scenarios of new features before verifying bugs, and then conduct some other tests if time is available, so as to minimize the risk of launch. The priority of the test order is shown in the figure below