It appears that software testing is an intangible activity. The test engineers’ hard work and creativity are not seen by other project members. All their efforts result only in error reports. (by QATestLab)

1. What Information
Must a Good Error
Report Include?

2. A Secret of Good Error Report
It appears that software testing is an
intangible activity. The test engineers’
hard work and creativity are not seen
by other project members. All their
efforts result only in error reports.

3. A Secret of Good Error Report
Experienced specialists in testing know
that it is not enough to quickly find
defects in course of compatibility testing,
user interface testing, localization
testing and other activities. No less
important is to write the error reports
correctly.

4. A Secret of Good Error Report
There are a lot of various tools for error
tracking and test management that are
used in order to simplify and streamline
communication between project members
and the process of error reporting.

5. Regardless of the Utilized Error Tracking
System an Error Report Must Contain:
 the name of the reporter;
 name, version, build number of the
tested app;
 detailed info about the device, OS,
browser and etc.;
 priority, severity and status of the defect;

6. Regardless of the Utilized Error Tracking
System an Error Report Must Contain:
 name of specialist to whom the defect is assigned;
 short info about the defect;
 more detailed description of the defect (actual
and expected results);
 clear steps to reproduce the defect;
 additions (screenshots or video records of the
defect).

7. THANK YOU!
Law of Cybernetic
Entomology:
There is always one more bug.