YouI Software test Plan

In the beta release, we will focus on testing in software development.

Our software is need to test, do not test how to know good and bad? Some programs do not test or even run-

Our goal: It is after testing the quality of the software to be effectively guaranteed. No matter what the situation can be modified or all is correct. Or we can take all aspects into account, but also to deal with the problems found. This is our good enough software.

Exit Criteria is: There are two types of user exit, after exiting need to sign in again. Another is to quit the program, the next time you log on does not require user login verification.

Our test matrix is:

1. All the functions in the design can be realized: We start to have a blueprint for the design, so the specific features should be implemented is very certain, this is more convenient to check.

2. User interface through user's trial: Invite people to use your software, and put forward comments and suggestions, some people use this is a software based on the main characteristics of the market.

3. The response time of the system can be tolerated: if typing takes a particularly long time, who uses the software?

4. The bugs found or have been resolved, or the following can be resolved: The test phase is unavoidable to find a lot of bugs, found that many bugs are not bad, found that less is not necessarily a good thing. The key is to expose as many of the problems as possible and to do our best to improve them.

5. Extreme situations can be solved (for example, overflow, and edge testing): The various boundary conditions are often problematic places. In our beta version there will be many extreme cases to experiment with.

6. Reliable data, System Stability: We write scripts, test programs, and so on to the content of care for machine validation.

YouI Software test Plan