bug-report | Online courses from QATestLab - Part 2

Question 1

Do I need to report a bug for each checklist item with the «Failed»  status? The limit for the course is 50 bug reports, and there are still several lectures ahead where I need to report bugs.

Accepted Answer

It is necessary to add a link to a bug report or a summary according to the «What? Where? When?» principle for all checks marked as «Failed» . You can do it in a note without reporting in the bug tracker. You can add only 5 links from Mantis. «Failed» checks cannot be left empty.

Question 2

Can I add more than 3 interesting bugs for Homework №4? Should all bugs be from different sites or from one site?

Accepted Answer

For homework №4 you can create a maximum of 3 interesting bugs which can be from different sites.

Question 3

Is it possible to add bug reports for the previous homeworks if after the homework I'll have less then 50 bug reports in Mantis?

Accepted Answer

Yes, you can report bugs for homework that has expired. They will be accepted and estimated without any feedback.

Question 4

How to capture a video without bookmarks but with an address bar in the browser?

Accepted Answer

You can disable the bookmark bar in the browser settings.

Question 5

Do I need to change the category to Homework_3 if I reported a lot of functional bugs in Mantis in the Homework_2 category?

Accepted Answer

It's better to change the category of bug reports.

Question 6

Is it possible to test a game outside of the Steam service in the «Software Testing: Basics and Practice» course?

Accepted Answer

Yes, you can test games not only from Steam.

Question 7

What is the build? Where can I find it?

Accepted Answer

Build is the final result of compiling the program with a unique build version number.

You can find it in the description of the game on the service where it was downloaded/installed or in the game settings or in the information about it.

If the game is from Steam the version can be found using the instructions at the link.

If this information is not available it is not necessary to indicate the exact and current version of the game, it is enough to write «Build #2.0» for example.

As part of the «Software Testing: Basics and Practice» course, the version of the assembly must be specified so that the student becomes familiar with the features of the design of bug reports for games.

Question 8

Is it a duplicate if two different students adding the same bug report?

Accepted Answer

Duplicates are two identical bug reports created by one student. Absolutely identically described reports of different students will also be closed as duplicates.

Question 9

Do I need to inform someone after reporting a bug / completing homework?

Accepted Answer

No, it's enough to save the bug report and it will be automatically assigned to the Training Center.

Question 10

Are defects with «closed» status included in the limit of 50 defects?

Accepted Answer

Bug reports with «closed» status are not included into the 50 defects limit.

Question 11

What is the acceptable size of photos and videos for a bug report in Mantis?

Accepted Answer

The Mantis bug tracker has a maximum attachment size of 5,000 KB. If your attachment is larger than the specified size then you can place it on a file hosting service, for example, DropBox and add a link to this file in the «Additional Information» block.

Question 12

If the bugs were found on the Training Center website / Personal account / Mantis / TestRail, then who should I write about them? What category should I assign to these bugs?

Accepted Answer

"You can report these bugs in Mantis as part of our course.

It is better to choose the «Feature request» special category or create a bug report without a category.

Question 13

Can I combine two different bugs in one report?

Accepted Answer

If two bugs are not related (the same steps or actions do not lead to them), then they need to be filed as separate reports. Otherwise, one report is drawn up and the list of objects with what the defect is associated is indicated in the «Additional Information» block.
You can find more information in the «How to describe similar bugs or the same bug in different browsers» article.

Question 14

Where I can indicate the information about testing on the emulator?

Accepted Answer

This information can be specified in the «Additional Information» field.

Question 15

What formats of screenshots and videos can I attach to a bug report in Mantis?

Accepted Answer

Screenshots has to be: «.png», «.bmp», «.jpeg» formats. Video should be attached in «.avi», «.mp4», «.mkv» formats.

Question 16

Can I create a bug reports for 404 errors after checking on W3C Link Checker?

Accepted Answer

Students are not allowed to create bug reports with errors found by third-party software. Only manual testing should be used, without access to the code.

Question 17

Will the bug-reports that are sent later than one week after the relevant lecture be evaluated?

Accepted Answer

Bug reports can be created before the end of the course. Reports completed on time can be edited/corrected until the last day of the course. But those reports that will be created after the due date for the corresponding homework are graded and accepted without feedback. For the «Fundamentals of Software Testing» course, without feedback, all bug reports are also accepted starting with the third homework assignment.

Question 18

Is there an opportunity to see examples of homework?

Accepted Answer

Examples of bug reports are in a separate project in the Mantis bug tracker. The students can also find examples of properly designed bug reports in their personal profile in the «Documents» section.

Examples of other homework are provided at each lesson section in the personal cabinet.

Question 19

Is it necessary to create a bug reports only based on the website provided for testing? Or I can test my own resources and report bugs that were found on other websites?

Accepted Answer

For practice, the students of the «Fundamentals of Software Testing» course are provided with a special test website. This resource should be tested throughout the course, each homework assumes working with that website.

However, the course has one special assignment in which students will be able to describe 1-3 interesting bugs found independently on public Internet resources.

Question 20

Should the «what? where? when?» sequence be followed in the bug description?

Accepted Answer

Yes, the sequence of answers must always be preserved. It should be followed in summary, description and results.

There are some exceptions where you may miss out on the «Where» part (to avoid tautology) or «When» (if the bug is displayed without additional actions).

More information about the principle can be found in the article.

Question 21

When testing the website, can a tester report a bug in the code or should the bugs be described only on GUI?

Accepted Answer

Manual testing uses the black box method, i.e. testing without access to the code. Accordingly, it is necessary to report defects obtained through the user interface.

Question 22

How do I attach multiple files at once? Can I add more screenshots only after creating a report?

Accepted Answer

"After creating a bug report, you can add more screenshots. In order to attach a new screenshot/video it is necessary:

1. Click the «Select file» button in the «Upload Files» section;

2. Select the necessary file;

3. Click the «Upload File» button."

Question 23

How do I know what is the expected result? Is the expected result taken from the specification?

Accepted Answer

Since no specification is provided on the course (as on most projects), students need to look for bugs and describe the expected result based on their own knowledge and experience with similar resources/applications, etc.

Question 24

Who should I assign bug reports to?

Accepted Answer

When a bug is created it is given the «assigned» status and it is automatically assigned to the Training Center.
Fixed/updated bug-reports change the «feedback» status to the «assigned» status automatically after editing and saving changes.

More information about the processes of checking and evaluating bug reports can be found in the article: «Life cycle of checking bug reports».

Question 25

How to know that the bug report has been reviewed and does not need improvement?

Accepted Answer

The bug report can be given the «feedback» and «accepted» statuses:

- the «feedback» status - changes should be made to the report according to the comments left;

- the «accepted» status - the report has been accepted and there is no need to edit such report.

More information about the processes of checking and evaluating bug reports can be found in the article: «Life cycle of checking bug reports».

Question 26

Is there any way to remove duplicate bug reports?

Accepted Answer

Duplicates of bug reports cannot be removed, but bug reports with the «closed» status are not counted within the 50 defects limit.

Question 27

Do I have to attach screenshots for each bug?

Accepted Answer

Yes, defect screenshots is a mandatory bug attribute. If the bug needs to be played with the speaker, a video of the defect with voice accompaniment is attached in addition to the screenshot. A screenshot should always be attached, even if there is a video as a bug preview.

Question 28

How to correctly specify the name of buttons if the bug report description is in English and the button is in Ukrainian?

Accepted Answer

Buttons names, links, messages are specified in quotes in the same language in which the website is implemented (without translation).

Question 29

How do I choose the defect priority?

Accepted Answer

Priority is usually chosen by the project manager. When creating a bug report, the student can choose a priority that they think is right. If the priority of a defect is not specified correctly, the evaluation will not decrease, because the main goal of the «Fundamentals of Software Testing» course is to learn how to correctly design bug-reports in a bug tracker.

More information about the bug priority in the Mantis bug tracker can be found in the «Mantis bug tracker glossary» article.

Question 30

How can I compress a video? The bug tracker shows a message that the video is too big?

Accepted Answer

Sometimes it's better not to compress or trim the video. You can upload a video to any file share (dropbox, for example) and specify a link to the video in the «Additional Information» field.

Question 31

What should I write to the «Description» field?

Accepted Answer

One sentence following the «What? Where? When?» principle should be written in the «Description» field in accordance to the subject. You can add 1 more sentence if it contains important information that did not fit into the summary due to the character limit.

Question 32

If a bug report is returned with comments, do I need to change the report itself or the comments under it?

Accepted Answer

It is necessary to make corrections according to the comments directly to the bug-report (after clicking the «Edit» button). Fixed/reassigned bug reports with the «feedback» status are automatically given the «assigned» status after editing and saving changes.

Question 33

Bug reports on the second round come back with the same comment - is that expected?

Accepted Answer

Please contact the Training Center specialists on the current issue and provide a link to a bug report. They will clarify and detail the comments to its design.

Questions can be asked in online support on the website or in your personal cabinet.

Question 34

If a bug report is often returned for refinement, will the points be reduced?

Accepted Answer

If the bug report has been returned for revision and all errors have been corrected, it is assigned a score close to the maximum. In the process of verification, points for edited bug reports may decrease only in case of a decrease in the quality of the data description, deletion of attachments, etc. In the free «Fundamentals of Software Testing» course, the first two homework assignments are checked with 1 feedback, the subsequent ones without. In the «Software Testing: Basics and Practice» course, all tasks are checked with feedback 2 times. More information about the processes of checking and evaluating bug reports can be found in the article: «Bug Report Check Lifecycle».

Question 35

How does a bug report verification notification arrive?

Accepted Answer

A letter will be sent to the students in the email. After that, it is necessary to log in system Mantis and to see what status is given to the bug report:

1. «feedback» means that the report is checked and it should be corrected according to the comments specified in the «Comments» field;

2. «accepted» means that the report has been checked and does not need to be corrected.

More detailed information about the checking process can be found here.

Question 36

Does the «assigned» bug status mean that the bug report hasn't been checked yet?

Accepted Answer

Correct, bug status «assigned» means that the bug report has not yet been checked by Training Center specialists. More detailed information can be found here.

Question 37

Are there any requirements for screenshot file names?

Accepted Answer

No, there are no separate requirements for screenshot file names.

Question 38

Bug reports with mistakes will as well be evaluated in the end?

Accepted Answer

All bug reports will be evaluated. If there are mistakes in the report, the score will be lowered.

Question 39

Can I attach a screenshot or is it better to record a video?

Accepted Answer

It is better to attach a video recording of the defect, but sometimes it’s more efficient to attach a complex screenshot.

Question 40

Which language should bug-reports be reported in?

Accepted Answer

Reports should be reported in the English language.

Question 41

Is a bug-report evaluated when it is indicated as orange?

Accepted Answer

The «accepted» status (orange) means that the report is checked and evaluated, it does not need to be corrected. More information about the processes of checking and evaluating bug-reports can be found in the article: «Life cycle of checking bug reports».

Question 42

If the same defect is displayed in all browsers, do I need to create a one bug-report or several, separately for each browser?

Accepted Answer

You need to create one bug report. The main browser with the version should be indicated in the «Platform» field. In the case when the bug is reproduced in different browsers, you need to specify this in the «Additional Information» section (Do not create several duplicate bug-reports).

More information can be found in the article.

Question 43

Do I need to reassign a bug report after it was fixed?

Accepted Answer

If the student received a bug-report with the «feedback» status and indicating mistakes comments, then he needs to correct the report accordingly to the left comments. Corrected/reassigned bug-reports with the «feedback» status are automatically assigned with the «assigned» status after editing and saving changes. More detailed information can be found here.

Question 44

Will the evaluation be harshly reduced for grammar and spelling errors in English?

Accepted Answer

Yes, during the checking of the reported bug-report, the points are going to be decreased for grammar and spelling errors.

Question 45

Why is it mandatory to write a summary in a Passive Voice?

Accepted Answer

During the bug-reporting process it is preferred to use a passive voice since it is used when a performer is obvious or insignificant, or when the action and its result are more interesting than a performer. And for bug-reports, the performed on the object action is important, unlike a performer. The most recommended tense for using in bug-reports is Present Simple Passive Voice. But there are also exceptions - crashes are reported only in Present Simple Active Voice, and it also may not be appropriate for bug-reports in games, you need to determine its need based on the nature of the bug.

Question 46

Are the bug-reports that are reported during the lecture mandatory? Are they evaluated as a homework?

Accepted Answer

No, they are not mandatory. But all of the reported bug-reports during lectures are tested and evaluated equally with ones reported during the homework.

Question 47

How many points can I get after correcting a bug report?

Accepted Answer

If the student created the report the first time without errors, he will be able to receive the maximum number of points – 1 point for one report.

If the student corrects all errors in his report, he can get from 0.5 to 0.95 points for one report.

The maximum possible amount of points can be found in the scheme of the path to success of the «Fundamentals of Software Testing» course.

Question 48

Which bug report is evaluated: the original version or with corrections made according to the comments?

Accepted Answer

The system accepts the last homework, with adjustments already made.

More information about the procedure for checking and evaluating bug reports can be found in the «The life cycle of checking bug reports» article.

Question 49

Where can I see the grade for my bug report?

Accepted Answer

It is not possible to view points for a bug report. At the end of the online training, an email is sent to all participants with the overall results at the end of the course, which include scores for: bug reports, test types, checklists (and other types of homework) and the exam. However, in the personal cabinet on the course page, there is a scale, which shows the progress of the student on the way to receive a certificate. It is filled in according to the assessment. It will take into account points for all homework (bug reports, checklists, description of types of testing, test cases and other types of homework), optional task and exam.

Question 50

The more «accepted» bug reports, the more points you get?

Accepted Answer

The «accepted» status means that the report has been verified, evaluated and does not need to be corrected. Accordingly, the score for such reports will be higher than for bug reports with «feedback» status. More detailed information can be found here.

Question 51

Why do we need the «Category» field in the bug tracker?

Accepted Answer

The «Category» field indicates the type of testing to what the found defect belongs.

Question 52

What programs can be used to capture screenshots and video bugs?

Accepted Answer

SnagIt can be considered the most convenient program, because this program allows you to both take video from the monitor screen and create screenshots.

There are also other programs that are quite useful:
Fraps is a compact program for recording video from the screen and counting fps;
Bandicam - a program for high-quality video capture and recording;
CamStudio is a convenient program for recording video.
To take screenshots on Ubuntu you can use Shutter, GNOME Screenshot, Joxi and others.

TAG: bug-report

10 the most popular questions

Tags