The script of the tester’s behavior when finding a bug.

This script of the tester’s behavior, when finding a bug, may take place in ideal conditions.

To remember and keep to it you should in the way described below.

However you should remember that in real life in the dependence on the project, the company, specific of development process and as with increase in your personal experience and knowledge in testing, the script can change, some parts of the script cannot be taken into consideration, or some points are completely absent!

Note: BTS – the Bug traking system.

1. Found a mistake

2. Reproduced a mistake (wrote down steps in a notebook)

3. Thought over the cause of a defect’s appearance (a few seconds, didn't think up and went

onJ, it will come with experience)

4. Checked * BTS against the bug’s duplicate

5. Hurrah! The mistake has been identified!!! (praise yourself)

6. We create a new bug in BTS:

o we start filling with a field “the description and steps”

o Expected result, a source: Requirements, technical requirements, Spec, Standards

o Actual result, a source: eyes, brain and hands of the tester

o Argumentations, screenshots, video in case of difficulty to reproduce bugs are necessary

Then we fill remaining fields (it depends on a type of BTS and company’s requirements)

* Field Summary filling (filling schemes: what? where? when? personal experience or

other)

7. Is assigned to: (is presented by team-lead, you are informed with whom you should further

communicate)

8. We communicate and prove existence of the new bug (a long process, getting on chat,

Skype, by mail, by short dashes between departments)

9. Justified, we wait for fixing – the new version

10. We check the new version, ran the test case, i.e. subsections of item 5

11. Is it still broken? Gave back, continued to communicate!

12. Finally the next version … whoa works!

13. We close the bug, it is desirable the same person who opened the bug

14. To add the comment: "It has worked!" and to change the bug status, it depends on BTS

15. Reinsurance (after the bug fixing to reproduce the bug by steps and taking into account reproduction conditions to get sure the bug has been fixed completely)

16. Triumph!!

Date: 2015-04-20; view: 985