Test plan for software testing

It's easy for me to get caught up in a formal confinement. To complete a task cannot be done in order to complete, you should prioritize and know why to do this thing.

Write a test plan, a bit like the old lady's binding cloth, and smelly and long.

Did not write the most important time arrangement. Reflective reflection ...

But who's going to do it! In fact, as the project changes, agile development and testing is the kingly way.

Directory

1 Introduction ... 4

1.1 Document Destination ... 4

1.2 Test Purpose ... 4

1.3 Project Background ... 4

1.4 Reference documentation ... 5

2 Test Range ... 5

2.1 Test Range ... 5

2.2 Test constraints ... 6

3 Resources ... 6

3.1 Human Resources ... 6

3.1.1 Roles and Responsibilities ... 6

3.1.2 Training Program ... 7

3.2 system resources ... 7

3.2.1 Hardware and software resources ... 7

3.2.2 Test environment ... 7

3.2.3 Test Tool ... 7

3.2.4 Other requirements ... 8

4 Testing requirements ... 8

4.1 tested items ... 8

4.2 not tested items ... 8

4.3 Other test items (non-development requirements) ... 8

5 test Method ... 9

5.1 Functional test ... 9

5.2 Performance Test ... 9

6 Test Milestones ... 9

7 test task scheduling and estimating ... 9

8 test exit Criteria Definition ... 10

9 Test work documents to be delivered ... 10

10 Related documents ... 11

11 Appendix I test Strategy Standard ... 11

12 Appendix II Test-Related glossary ... 19

This is the directory of the test plan I wrote, and I have no idea what I'm writing this for. Don't write any more.

Test plan for software testing