App software semi-finished test tips

Due to the variety of product types, the advanced features of products, more embodied in the stability and reliability of product quality. The field of software application is deepening, the complexity of design is gradually enlarged, the cycle of development is shortened, and the quality requirements are gradually improved. However, according to the iteration speed of our company's version, the test time is first loose and tight, so that at the end sometimes there is no guarantee of product quality, according to the above situation I made the following strategy, for reference only:

1. Preparation of test data

Test data is prepared in advance before testing, which saves a large part of the time in the test and also saves some time for development

2.UI, main Menu test

Based on the habit of development, they will first make Ui changes to the functionality of 80% in the version requirements . In this case, we can test them first. This time we have a lot of testing time, just fit to do the UI test compatibility problem. If the design does not modify the UI aspect of the problem, we do a UI compatibility line problem on the line!

3, semi-finished test

Whether a version can be on-line on time, it needs the client and the server to match, as well as the WEB side. If the test is semi-finished, we can also probably look at the effect, whether it meets the requirements of the document, whether it is in line with the user's habits, we can print the interface data to see whether the interface is not good, or the client did not do the corresponding support, so we can quickly locate the problem. Same semi-finished product we can also do compatibility testing.

4, the large function module test

Before the large functional module test, we first need to understand the requirements, the entire logic process to look first. If there is no understanding of the place, we ask the product in time. This is a smooth test, and it is clear that your logic is consistent with the logic of development. When testing a large function module, we should focus on the test, try not to be interrupted, because the focus of the test, the most clear thinking, the best way to take a good process.

5. Other functions (statistics, start-up diagram update)

If there is no time to test, we can completely ignore the statistics, all the statistics we can focus on the final test, the test statistics of about 10 minutes can be completely done. The start diagram is better tested and we can test it in a minute. Like the start-up diagram of this feature development will be put in the end will do, because just change a piece on the line.

6. Custom Link Jump

Usually when a version adds large functionality, there will be a custom link jump, even if the product documentation does not mention whether or not to support a custom link jump .

7, do not want to test the function

Each product documentation, we have the need to do not want to test, in the face of such a problem I will spend some time to understand the logic, I think I will let the product to tell me the logic, because I did not understand when the demand. During the test I will also give this function to the back row, will first test the other functions.

App software semi-finished test tips