Shulou(Shulou.com)06/03 Report--

1. The purpose and goal of the test

two。 Test dependency condition

Test the dependency of the project with other platforms, and the platform or environment on which the current project depends needs to be integrated.

3. Test range

Components to be tested, core functions, and sub-functions can be written according to the needs of the project. And non-test scope.

4. Test level

Describe the relevant test levels (unit, subsystem integration, integration testing)

5. Test type

Describe the test type:

(1) Black box, gray box and white box testing

(2) Development testing, acceptance testing, running testing

(3) smoke and regression test

(4) Manual and automated testing

(5) Mode-based testing (system startup, operating mode, degraded mode, system shutdown)

(6) normal and abnormal testing (positive and negative examples)

(7) testing of quality requirements, such as usability testing, capacity (load, stress testing), interoperability, performance, reliability, robustness, security, * testing, ease of use testing.

(8) static and dynamic testing

(9) Test of time or date

6. Human resources related to the test team

The test team, testers include responsibilities, permissions, relevant qualifications (such as expertise, training, and experience, generally required for testing as a third party), and staffing levels.

7. Testing process

Demand analysis phase

Use case design phase

Test case selection criteria (e. G. interface-based, use case path, boundary value testing, error inference)

Execute the test phase

(1) Test work products (such as test documentation, test software, test data input, expected output, test hardware and test environment)

(2) Test tasks (main test tasks, such as name, goal, precondition, input, step, postcondition and output)

(3) Test integrity and rigor (according to the test level)

(4) the source of the subsystem (whether Party A provides equipment or is it open source or internally developed)

(5) testing techniques (testing methods or techniques used in the testing process, such as boundary value testing, equivalence testing, fuzzy testing, * testing, link testing, compatibility testing)

The entry standard of the test (the standard that must be available before starting the test)

Test pause and restart criteria (there are quite a number of errors in the program documentation or system server exceptions or blocking Bug is found. )

Test completion or completion criteria (such as coverage based on different levels of code, such as statements, branches, or conditions)

(6) Test data (type and quantity of test data to be generated)

8. Environment

The equipment needed for testing: test machine and server, test tools (test management tools, etc.), test environment (software environment and hardware environment), test facilities (database, etc.).

9. Test schedule

Test milestone activities: project development cycle, schedule, etc. Such as requirements analysis, test plan, use case review, system testing, acceptance testing, etc.

10. Evaluation and measurement indicators

Reviews related to testing, test metrics, status reports (percentage and number of case that the test runs and passes)

11. references

Affects all relevant documents used in testing or writing plans, such as project requirements documents, etc.

twelve。 Project glossary

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.