I. Introduction
1. Purpose
In order to make the work of the testing phase system can be structured, and the system can be tested according to the standard, especially the preparation of this plan.
2. Background
To be developed software system name:
the project developers:
3. Scope
Project managers, all members of the test group
4. The defect classification criteria
Serious defects
1. Since the program crashes caused by illegal exit
2. infinite loop
3. due to procedural errors caused by interruption of operation
4. Functional error
error 5. Data Communication
is a big flaw
1. Program error
2. Programming Interface error
smaller defects
1. the operator interface errors (including the column name in the data window is defined, the meanings are the same)
2. print, malformed
3. simple input limiting control is not in the foreground
4. No prompt deletion
minor defects
1. interface irregular
2. auxiliary DESCRIPTION unclear
3. the non-standard input and output
4. long operation is not presented to the user
5. the prompt text is not employed industry terminology
6. the input region may be read-only area and no clear distinction flag
other defects
other errors
5. Test Reference Document
Requirements documents, prototypes map
II. Test Strategy
1. Functional Test
Test Objective: functional testing needs all the features of items to achieve.
Test method: according to test requirements, adoption of guidelines, test cases, manual testing, verify the following:
get the right results in the use of legitimate data.
Display the appropriate error message when using illegal data or warnings.
Each business rule is properly applied.
Testing tools: Zen
Completion Criteria: All planned tests have been executed.
The discovery of the defect repair rate by guidelines.
We can not achieve functional test item development team needs to give a reasonable explanation or made changes to requirements.
Special considerations: None
2. Performance Test
Test Objective: Verify system some of the key scenes when large concurrent user system capabilities, stability, and reliability of
the test method: using virtual simulation tools for each scenario concurrent users, time pressure measurement.
Testing tools:
Completion Criteria: Pressure test results meet the required performance indicators
specific matters: the corresponding function in normal use, pay attention to the test data
3. Safety Test
Test objectives: application-level security: verifying specific user can access only those functions or data that belongs to the type of user has been granted access to the
testing methods: Create tests for each user type, and by creating various types of users to specific transactions verify their permissions, modify user type and re-run the test for the same user. For each type of user, or refuses to ensure proper additional functions or these data
Testing tools:
Completion Criteria: various known types of users can access the corresponding function or data, and all transactions are running as expected and run all the affairs in the previous application functional testing in
special items: Transaction processing all of a sudden power failure, or whether it will continue to process the appropriate information when prompted to re-enter the system.
4. Compatibility Test
Test Objective: Verify whether the test object can normally use in all types of operating system and browser version
test: Verify that each function in all kinds of various types of operating system and browser version
Testing tools:
Completion Criteria: functions and data can normally use and display in each browser,
special considerations:
5. Compatibility Test
Test Objective: program interface complies with the relevant specifications. (Including window window, between fields and field browsing, as well as objects and features (e.g., menu, size, position, state of various access methods (Tab key, mouse movement, and shortcuts) to be used and the window center) are standard)
test method: one check in accordance with the relevant provisions, including menus, buttons, copyright information, and so on. Check the message text and punctuation, icons, etc.
Testing tools:
Completion Criteria: program interface complies with the relevant specifications, each window are consistent with benchmark version or within acceptable standard
Special Considerations: Note the copyright information and the installer splash screen, note the version information.
Third, the test environment
Hardware environment, software environment, a specific test condition
Fourth, the test task and schedule
1. Test tasks
| Testing phase |
Testing tasks |
Stage completion flag |
| The overall test planning, |
Read reference documentation, test plans, assign test tasks. |
Submit "overall test plan" and through accreditation |
| System Test Plan |
Depending on the application needs analysis project documentation, project application to develop system test plans |
Submit "system test plan" and through accreditation |
| System Test Design |
Development test case design |
Submit "system test" and passed the assessment |
| System test implementation phase |
Perform system testing |
Submit "System Test bug log" and test items to meet demand by criteria |
| End-user documentation testing phase |
Check the "User's Manual" and "Operating Manual" , write "test analysis report." |
Ensure that relevant documents be consistent with the development of the system and ultimately , submitted to "test analysis report." |
2. Test schedule
| Test event |
Planned start date |
The actual start date |
End Date |
Stage completion flag |
| Test Plan |
|
|
|
Submit "system test plan" |
| Test design |
|
|
|
Submit "System Test Case Design" |
| Test implementation |
|
|
|
Submit "system test BUG tracking sheet" |
| Test Summary |
|
|
|
Submit "system test summary analysis report" |
Note:
1. each test group and development group modified time are not more than 3 days.
2. The test schedule is completely dependent on the development of planned and actual progress of the project development team, the development team if the adjustment program or change the schedule, testing schedule will also be adjusted accordingly.
3. In case of project development plan changes, test plan changes accordingly.
4. If the test project change plan also change.
V. Guidelines
1. To achieve all of the testing strategy and reach completion criteria.
2. "requirements specification", "outline design specification", "detailed design specification" "Coding and consistent.
3. After the test, the development group needs to modify the test items to achieve the degree of incorrect achieve the following:
Ø One, two, three bug fixes rate of 100%
Ø four, five error does not exceed 10 Ge