Turn: Test plan (Source:: 51Testing software test network--zfx081)

Test The planning phase is primarily in the pre-preparation phase of the test, in which the overall planning of the test work will be done. Include the following:

1. Introduction to test objectives and test projects.

1.1 Test Purpose: The test plan of the XXXX system helps to achieve the goal:

Identify existing project information and the software artifacts to be tested.

Recommend a test strategy that you can use and describe these strategies.

Identify the required resources and estimate the workload of the tests.

Gives the deliverable elements of the test project.

1.2 Project background

Understand what the product is, application areas, development background, key features, and scope of use. For large test projects also understand the purpose and focus of testing.

2. Test the reference document and the test submission document.

2.1 Test reference documentation

Product Requirement Specification

Product Outline Design

Detailed Product Design

Product is yo GA manual

2.2 Test Submission Documentation

test Case : Establish a test case content template that specifies the number sequence for the use case.

Test Log : Establish the test log content template to determine the application used for logging.

Defect Report: Identify the content of the defect report. Submitted in the same way. Use the defect tracking system. Determine the priority and severity of the defect.

Test summary: Establish a test summary template.

3. Test Strategy

The test strategy typically includes the following:

3.1 Database testing: Testing for database -related functions. Test objective: To ensure that the database access method and the capital normal, the data will not be destroyed. Test the database by reading and writing data.

3.2 Functional Testing: the integration test phase is mainly for large functional implementation testing, the system testing phase according to the requirements of the specification of a manual test, the acceptance test phase according to user manual specification test, in order to meet the requirements and the user manual list of function items.

3.3 Interface test: Only during the system testing phase. According to the relevant provisions of the inspection, including menus, buttons, copyright information, check the information in the text and punctuation, icons and so on.

3.4 Range Test: Only during the system testing phase. For all the data that needs to be entered, the data is entered and the output is checked. Check that the correct input is getting the correct output. The wrong input is given a corresponding error prompt.

3.5 Release Verification test: During the system test and acceptance testing phase. Try to avoid the impact of test results due to development group versioning issues. Perform the necessary reporting and testing of the basic functions of the system, usually for one day. To confirm whether the version is worth further testing as a standard.

3.6 Strength test: In the middle and later stages of system testing, by simulating the user's test. Verify the robustness of the system. For key modules, perform some necessary load tests, including large data volumes and long-time tests. Based on the stability of each module, the test of user is started. It also includes tests on capacity, hard disk capacity. Database size, and so on. The ability to test the system for self-protection in the case of a crash or program error.

3.7 Security testing: During the system testing phase, the security functions provided by the program meet the requirements of the design. Test the user's security, including user creation. Permission settings, authentication of permissions, permission levels, and so on. Test the security of the database.

3.8 Bare Metal Testing: During the system test, later or during the acceptance testing phase. In a clean environment, perform the same tests as other test environments. All test content should be included. Standard when the program is running normally on a bare metal environment.

3.9 Installation test: During the mid-to-late and acceptance testing phases of system testing. To install normal or uninstall normal as standard.

3.10 Cryptographic testing: During the mid-to-late and acceptance testing phases of system testing. The primary test for the dongle problem. Standard Time "encryption + can use" and "no Encryption + not available" Two aspects are normal.

4. Determine the test content.

Lists all the feature items that you want to test. Key points are as follows:

Functional testing: theoretically covering all functions. If there are special circumstances to cover all the main functions.

Design test: For some user interface, the structure of the menu and the design of the form is reasonable and so on test.

Overall consideration: whether the card rate is correct in the process of data flow from one module to another.

5. Testing Resources

5.1 Roles: Lists the staffing in the project.

5.2. Specific tasks assigned by testers

5.3 System (Hardware resources)

5.4 Software Environment

6. Test Progress

Lists the resource requirements and scheduling for the test phase.

List item Milestones

7. Risks and Issues

list the possible risks and issues:

High Market pressure

The test time is not enough.

The testers are in place in time (equipment and personnel).

Training for Testers.

Changes in the development schedule, requirements or design changes.

Basic training for testers.

Version control for the development group.

Go: Test plan (Source:: 51Testing software Test network--zfx081)