bug-report
-
How to write a proper bug report
Each company has its own rules for defect creation in the bug tracker – it depends on the company policy, development technology, bug tracker, project type and much more. But in any case, a good bug report has certain characteristics.
-
How to describe results in the bug report?
Defect (bug) is a discrepancy between the actual result of the program and the expected result. Defects are discovered during the software testing stage when the QA engineer compares the results of the program (component or design) with the expected result described in the requirements specification.
-
The life cycle of bug report checking at QATestLab testing courses
Bug reports created by students have their own life cycle.
-
How to write the description of the bug according to the «What? Where? When?» principle
Nowadays there are a lot of bug tracking systems, however they have one aim – to describe the essence of the defect precisely and laconically. This is the reason why they all have the similar filling principle.