1 , discuss your test plan:
• Anticipate problems that may occur in your system before you perform a formal test. For example, what data the user input may cause the system to report what kind of error.
• Detect whether the logical relationship between the functions meets the needs of the user.
• Use professional testing tools.
• Segment your users as much as possible and follow their actions to complete the software's functions.
2 , do we need to test until our software is perfect?
We have a low level of technology, there will certainly be a lot of shortcomings in the development process. Our software needs testing.
3 , what is "good enough" for testing?
The software system should be able to realize the basic function according to the user's requirement. And if the software has an exception, the software should handle these exceptions on its own, and the system-level exceptions cannot be displayed to the user interface.
4 , what is the "standard for exit"? ?
The following standard references from http://blog.csdn.net/fairy6102006/article/details/4982787
1. All test case execution is complete.
2. All defects are closed or within the agreed range
3, according to the requirements of the project team or senior end
4, may be due to time factors, according to customer needs to end the test
5, through the implementation of the test process, the system has met the specified functional and non-functional requirements
6, if it is a regression test, this test has verified that the bug was fixed
5 and what is our beta version "Good enough"? What is your test matrix?
1) The expected basic goals have been fulfilled.
2) There is no logical error, that is, the function of the software and the user's needs are basically consistent.
3) Users should be fluent in use, can not have a very obvious lag.
4) can record the user's preference settings.
|
|
User type |
Screen size |
Operating system |
Operating system default language |
Network speed |
Total number of combinations |
|
Number of variables |
1 |
More |
More |
|
|
|
|
|
Program Developers |
14 or more |
Windows family operating systems |
Chinese (simp.) |
Different |
|
Software Test Plan