1. Requirements: read requirements, understand requirements, communicate with customers, development and architecture, and deeply understand requirements. -Test team

2. Test plan: estimate the required resources (manpower, equipment, etc.). ), the time needed, the division of function points, and how to allocate and arrange resources reasonably according to the demand. -Test leader or test manager

3. Use case design: According to the test plan, task assignment and function point division, design reasonable test cases. -Test leader, senior tester

4. Execute the test: execute the test case according to the detailed steps of the test case. -Each tester (mainly junior testers)

5. Execution result record and bug record: record the test results of each use case, and write a bug record in the test management tool if there is a bug. -Each tester (mainly junior testers)

6. defect tracking: track the bugs assigned to you by the leader until the bugs are fixed. -Every tester

7. Test report: Through continuous testing and tracking, until the tested software meets the test requirements, there are no major bugs.

8. User experience, software release, etc.

Extended data:

Process analysis:

The only advantage of this process is that it can quickly find and fix problems.

In this process, the project manager is the core, and the project manager is really a great person with many years of development and project experience. He likes to share some cutting-edge technologies from time to time.

For testing, the requirements are very unclear, and test documents and use cases are also dispensable products. There is no requirement document, or it is too simple to write use cases according to the requirement document.

General test cases, such as login, file upload and download, list page turning, date selection, input box verification, search, etc. There are some "universal" use cases for reference during the test.

References:

Program Test _ Baidu Encyclopedia