The life cycle of checking bug reports on the «Fundamentals of Software Testing» course

Bug reports created by students have their own life cycle. It consists of the following stages:

• A student finds a bug by doing homework and examine it to find the conditions to reproduce it.
• A student describes a bug in MantisBT using all reporting rules. The created report is automatically assigned to the Training Center and assigned the  «assigned» status.
• The reports are checked by Training Center specialists:
  • If the reported situation is not a bug, then the TC specialist changes the bug report status to «closed» and assigns the «not a bug» resolution. Points are not given;
  • If the reported situation is a bug then the TC specialist checks it for uniqueness (whether this report is a duplicate of another). The duplicate is assigned the «duplicate» resolution and the «closed» status. Such a report is closed. Points are not given.
• The Training Centre specialist checks the bug-report:
  • If there are no errors in the structure, the specialist of the training center conducts a final assessment and assigns the «accepted» status to the report. Points are given to the student.  Reports in Russian / Ukrainian are evaluated up to 1 point and in English up to 1.5 points (for 1 report);
  • If there are some grammatical or orthographic errors the specialist of the training center assigns the «feedback» status to the report and assigns it to the student. On this stage points are added (up to 1.5);
  • All reports with the «Feedback» status are returned to the student and require improvements. Such bug reports contain detailed comments from the specialist of the Training Center, indicating the mistakes.
• The student corrects the mistakes in the bug report and the bug report is assigned the  «assigned»  status. The bug tracking system automatically assigns it to the Training Center.
• The Training Centre specialist re-checks the report:
  • If there are no errors the specialist of the training center conducts a final assessment and assigns the «accepted» status to the report and adding points (up to 1.5);
  • If there are errors the TC specialist assigns the «feedback» status  to the report and assigns it to the student again. Points are also added at this stage (up to 1.5). The student must correct the errors indicated by the specialists.
• If the report has been checked twice or the check is carried out after 18:00 of the last day of the course TC specialist conducts a final assessment, assigns the «accepted» status to the report and adds points (up to 1.5).

The life cycle of checking bug reports on the facultative task of the 

«Fundamentals of Software Testing» course

The life cycle of checking bug reports for the facultative task is different from checking bug reports for homework in the QATestLab «Fundamentals of Software Testing» course.

The life cycle of these bug reports consists of the following stages:

1. Students are looking for bugs in the system https://openlibrary.org/, https://museum-portal.com/.
2. Students describe a bug in Mantis BT using all reporting rules. The created report automatically receives the «assigned» status and goes to the «Training Center».
3. The specialist of the training center checks the report for mistakes in structure:

• If there are some errors in the bug report the student will see comments with a list of errors. However, the corrected bug reports will not be estimated. The report is given the «accepted» status even if it needs to be finalized. The maximum marks to evaluate the bug reports are the following: reports in Russian/Ukrainian are evaluated up to 2 points, in English is up to 3 points (for 1 report). Please, note that bugs found during the facultative task are estimated 2 times higher;
• If the reported situation is not a bug, then the TC specialist changes the bug report status to «closed» and assigns the «not a bug» resolution. Marks are not added in this case;
• If the reported situation is a bug, then TC specialist checks it for uniqueness (is this report a duplicate of another). The duplicate is assigned the «duplicate» resolution and the «closed» status. Such a report is closed. Points are not added.

4. It isn't necessary for students to correct the bug reports in accordance with the comments left . These bug reports are already closed and evaluated.