Test development engineer growth diary 016 - those things about the test

1. Prediction preview

• Background: In the early stage, the quality of the test was low, the number of bugs after the test was large, and the requirements were omitted. Now it has been added and standardized and implemented..
• Goal: Improve project/iteration quality.
• Preview process:

Test Criteria:

• Completed and previewed with predictions

• Provide the preview problem and fix it within 24 hours

• After the test, the smoke case test passed

Conditions (or) for no rehearsal:

• In the same project/iteration for 3 consecutive prediction previews, the number of medium and excellent problems does not exceed 5% of the number of smoking use cases

• 3 times in a row, the total number of bugs created in the month does not exceed 200

• 5 iterations/projects in a row, no delays in proposals

Condition (or) to start rehearsal again:

• The total number of bugs created in the month exceeds 200

• Assertion delay occurred

2.Assessment process

Test initiation:

• [Recommendation] For pure front-end requirements, the front-end is responsible for testing; for pure back-end requirements, the back-end is responsible for testing;

• [Recommendation] Front-end and back-end requirements, the front-end and back-end are negotiated by themselves, and one person is responsible for testing all front-end and back-end content;

Test remarks:

• [Necessary] All suggestions: attach the corresponding demand link;

• [Necessary] part/batch test: detailed list, list the specific requirements, and try to be consistent with the title of the requirements document;

Prerequisites:

• [Required] Complete the front-end and back-end joint debugging

• [Required]Complete Code Review

• [Required] Complete the smoke use case and pass

• [Suggestion] Complete the pre-rehearsal meeting and fix any issues in the rehearsal

Information for testing:

• [Required] Create a test request form

• [Essential] The notes in the test sheet need to be filled with the description of [Test focus] and [Scope of influence]

Call back:

• Incorrect branch detection;

• The main process does not work;

• Smoke test case failed;

• Development does not specify the focus and scope of testing;

• Development did not provide correct yapi documentation; interface documentation specification reference;

• No preview previewed;

Exemption Criteria:

• [Necessary] The corresponding requirements have been notified to the test synchronously;

• The requirement type is to only change the UI layout or copywriting, but not to change the interaction and business.