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

In this phase of the test, I put my understanding of pre-testing into practice, which is relatively easy in the late delivery of the project, avoiding more risks caused by the pressure caused by time constraints. I now record my experience here.

one。 Establish a common goal

When setting up a project, establish a common goal with PD,PM, the project member, regardless of the organizational role, so that everyone can succeed in the project.

two。 Pre-input

1. Requirements analysis: business analysis of the integrity, testability and fuzzy areas of requirements; focus on the content of system-level servers. Understand the transfer mechanism and data reading rules between servers according to the business scenario. It is recommended to prepare scenario use cases here in advance, especially to verify the server processing logic results in advance with use cases with data, and to have a systematic and concrete understanding of the expected results for the server-side classmate team.

two。 Departments in stages: based on testing experience and development experience, put forward suggestions and questions about departments to see what logic should be put to the server to avoid complex interface interactions on the client side.

3. Test and analysis phase: always with doubt to consider whether the technical implementation effect can achieve the desired results of the business, find problems, and immediately have a small interview with the server and front-end developer hold to discuss the technical solution.

4. Development phase: monitor progress, provide support, and maintain a unified understanding of the expected results.

5. Before the development self-test phase: prepare the test data, as long as the server development basic problems, the client can compile and pass, put into testing at any time, help the development to get through the business, find the problem record in advance, and provide it to the development and repair.

6. Development self-testing phase: work side by side with development to ensure the understanding of use cases and the quality of self-testing. Through the interface testing, focus on the discovery of business logic.

7. The delivery phase begins: take the key business logic as the focus of testing; actively synchronize requirements changes; man-to-man every day to eliminate bug; understanding inconsistencies, immediately invite the meeting, solve on the spot.

Remember:

1. Everyone has inertia and time management problems. To ensure the quality of the development code, it is necessary to invest more in the early stage & early monitoring.

two。 Everyone has his own point of view and temper. When communicating, we should first make it clear that the premise is for a common purpose, and the key point is how to solve the problems that arise.

3. Position the role to quality assurance, look at the whole picture, and participate in more product life cycle.

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.