Public account concerns: test charging treasure, communication together

Testing is at the end of the development process, so early problems will affect testing. How to break this dilemma has become an urgent problem for testers.

As a tester, I should have the responsibility to supervise the development, product and other links, so as to avoid the impact on the test end. Establish the idea of testing left shift, starting from the requirements stage to think about how to ensure the quality of the whole process.

The so-called test left shift, is to control the upstream quality, advance to avoid risks. To do the test well, you can move to the left from the following directions:

The requirements phase

Demand changes frequently, I think research and development and testing are very distressed a thing, and the maintenance cost is very large, how to improve the quality of demand has become urgent!

  • More questions

Before the requirements review, products tend to give the review content in advance, this stage may require testing and development have a knowledge of demand and thinking ahead of time, and for some uncertain problems or recorded in the place, stay with the product manager when a formal review identified, ensure quality and stability of the demand.

  • Reasonable reward system

In view of the value of the demand problem proposed, it can be graded. Once it is adopted by the product, it can give a certain reward to the corresponding person to improve the enthusiasm of everyone in this link. Work together to ensure the quality of requirements.

  • Set up a demand counter session

Testing or R&D can be arranged to explain the requirements, which can also improve everyone’s understanding of the requirements. Of course, this may lead to the delay of the milestone. You can choose according to the situation.

Research and development phase

If the testers are capable, they can participate in the design review and database review of the r&d, because testing is the most familiar with the business, and if there are design defects in the business, they can be avoided in advance.

Use case stage

  • List key points and draw flow charts

During the requirements dismantling process, you can map the business process and then use a mind map to list the test points for the iteration. Although it will bring extra workload, I think the short-term workload may be enough, but the benefits in the later period can be foreseen.

  1. Business flow diagrams help you think deeply about requirements and the business;
  2. Test focus and business flow chart as knowledge document precipitation, help new employees quickly integrate into the team, carry out work;
  3. Flow charts and key points are more intuitive, and use cases are also improved in the later review.
  • Mutual audit within the organization

After writing the use case, you can first organize the testing personnel to check each other internally to achieve the effect of checking the deficiency.

  • Use case review

In the three-party review of production, research and testing, use cases can also be designed for reverse discussion, but it also depends on the situation of the team. Key points can be selected during the review process, and non-important ones can be passed over to improve the review efficiency. The longer the meeting is delayed, the lower the benefits will be.

To measure phase

For development and test, we can set up test access conditions.

  1. Select important test cases for this iteration for development self-test;
  2. Use cases distributed to development must self-test;
  3. After the test, the test smoke through;

After the above conditions are met, the system test can be performed.

Launch phase

First of all, we need to set up quality standards, such as:

  1. Can’t go live with serious bugs;
  2. Test cases must all pass;
  3. Some minor bugs are allowed to go live after negotiation and must be dealt with as high priority in the next iteration;
  4. Do a good job of on-line plan;

conclusion

The above are some summaries of my work. We don’t need to follow the points listed in the article all the time. We need to make adjustments according to the actual situation of the project.

I hope this article has given you some insight into your predicament.