A good bug ticket, for it to be validated, must be as clear, concise and complete as possible. To do this, you must fill in the fields described below according to a precise and rigorous nomenclature.
Here is a golden rule to describe a bug correctly: any information not present in the description of the test step must be included in the bug description to ensure that it is understood.
Title of the bug ticket. It must be concise and explicit. Bear in mind that someone who is not familiar with the project should be able to understand the issue simply by reading the title of the ticket. It may happen that a particular nomenclature is requested by the customer. In other cases, you can use this rule : [Page name/area] Concise description of the bug.
Examples [My account] The profile image is squished vertically [My Orders] With all accounts, the numbers behind the decimal point are not displayed [My Orders] With the account[Data Set], the dates are displayed in the US format [Home page] The login button does not prompt any actions
With information received prior to the project, the DM lays out the sections of the product to be tested (usually the pages or functions of a site). In this case, the tester must indicate in which section his bug is located, by selecting it from the drop-down list of choices (only one possible choice for each bug).
Examples Home page My orders Cart Checkout Process
When testing on different versions of the product, the DM provides the version numbers to be tested (application build or site version). The tester must indicate in which version(s) his bug is located, by selecting them in the drop-down list of choices (several choices possible for a bug). It is possible that the DM will use this "Version" field for other purposes, in this case, follow the instructions given by the DM.
Examples Build v1.0.3 Build v1.0.4 Version 5.1 Version 5.2
This is where the tester describes his bug. This part must contain a precise and accurate description of the defect found during the tests. If necessary, additional information for a good understanding of the defect should be added here (including the Data sets used so that the customer/developer has all the necessary informations).
Examples Absence of the separation bar between several products The help icon "No IMEI" touches the top frame At the scroll down on the "Meals" page, we arrive at an area without content, all white for several seconds before reaching the end of the page When you launch a search for a product that cannot be found in the "Product search" tab, you get infinite loading When filling in the "Change my billing address" form, the "Country of residence" field crashes the application when you click on it.Account used: email: abcd@gmail.com password: abcd1234 When the user arrives on the home page and wants to click on “options”, nothing happens, the link is either dead or no longer current After filling in all the registration information and validating it, the page loads for a few moments, then the registration page is displayed again with an error message in the "Email confirmation" field If the user clicks on "View my last scanned items" he is blocked on the page indicating that he has not scanned an item yet. The user is therefore forced to close the application to be able to start browsing again
Describe here the normal behavior of the product expected by the developers.
For an exploratory test, the tester must rely on their experience to describe the expected behaviour.
For a guided test, the tester must reiterate the expected result of the stage concerned.
Examples The "Menu" popup is composed of the following elements: “Close” button on the top right "Rules of the game" button (in blue) "Terms and Regulations" button (in blue) “Sound” button "Exit the game" button (in red) The "My Account" window opens Each time you click on the left navigation arrow, the previous page is displayed with no apparent issues The confirmation page is displayed after the validation of the registration form. After launching a search for a product that cannot be found, the application indicates this to the user with the message "Product not found" The page indicating that the user has not scanned any items has a "back" button When completing the "Change my billing address" form, the "Country of residence" field displays a list of possible countries of residence The Pop-in window closes
The steps to reproduce indicate all the actions necessary to find or reproduce the defect.
For guided tests, be careful not to use the test description as written in the Test Suite without any reflection. In some cases, the steps from the Test Suite are sufficient, but this description may sometimes differ from the actual steps needed to reach the page and reproduce the anomaly. They must be as precise and complete as possible, containing all necessary information, so that the person in charge of checking the defect can do so without knowing the test environment.
Examples 1. Click on "Store".
2. Fill in the search bar field with the city "Marseille".
3. Select the "Marseille-La Valentine" store.
4. Click on "News".
5. Scroll down to the bottom of the page1. Launch the application and log in to your account
2. Choose a favorite store
3. Go to a PLP (e.g. "Televisions")
4. In the filter box, choose the display grid on two columns
5. Check the display1. Be logged out
2. Click on the register button
3. Enter the requested information except the phone number
4. Confirm by clicking on the "Register" button1. Login
2. Click on "My Cart"
3. Click on the "+" button in order to increase the quantity
We identify 5 main types of bugs: Graphical, ergonomical, functional, performance/stability and wording.
A graphical bug is a bug that alters the display of one or more elements of a tested page. This bug category therefore refers to the visual (format, neatness, layout of elements, etc.).
Examples Blurred, pixelated, cut image Picture in the wrong place, offset Trimmed button The display of an element differs/not in accordance with the reference model Font or line spacing not suitable Text misaligned vertically or horizontally A graphical element protrudes/overflows from the element containing it A graphic element is distorted/stretched/squished A graphic element is too close/stuck to another A graphic element is blurred/pixelated One graphic element is overlapping another A non-functional graphic element is missing A word is cut off/displayed on two or more lines One graphic element is not aligned either vertically or horizontally with respect to the others A watermark is present on an image Non-consistent lateral margins
An ergonomic bug concerns an anomaly related to a bad implementation of the UI. It reports a problem related to a feature that is difficult to access. The element works but its layout or appearance is not optimal for the user.
This type of bug is rare, and is brought up especially when a suggestion is made.
Examples The back button is not in the same place from one page to another The validation button is red in color, a color commonly accepted as a cancellation or stop. It should be more of a green colour The sequence of pages is not logical
A functional bug concerns an anomaly involving a function not being performed or deviating from the expected result. This is a bug that alters the functioning of one or more elements.
The absence of a feature is also a functional bug.
Examples A function giving no result or a different one than expected Unable to enter text in editable fields An unexpected error message appears Radio button inactive Broken or missing image Return button unresponsive Inactive carousel No email notification Scrolling the page is not possible Absence of sound Non-operational geolocation Absence of zoom in and out actions Virtual keyboard not closing automatically Displaying a loading wheel infinitely Being unable to install the application No data refreshing Bluetooth pairing not working Form auto-completion not working The shopping cart appears empty (although it contains items) Sharing on social networks does not work The data entered by the user is deleted after a page change Opening the default alphabetical keyboard instead of the numeric one Blank choice pop-in Redirection to the production version of the site Redirection to a 404 error Being able to create an account even when the necessary conditions are not met (incompatible date of birth...) PDF download impossible Text entry impossible Tutorial absent when starting the application Selection of filters impossible An anchor redirecting to the wrong position Link, missing button
A bug causing, for example, slowdowns that can be measured: slowness at launch, poor management of loading times... or even causing a shutdown of the tested product.
Special cases for application crashes
The criticality of a crash must be as follows:
Examples A site or application is very slow or crashing regularly A random crash of the application Delay between character entry and appearance in the field Page slow to react to scrolling/swiping Page taking more than x seconds to loadFreeze of the applicationJerky video (due to loading)
Wording bugs concern issues relating to the text contained within the tested product. They can affect typography, spelling, grammar, syntax, translation or even differing labels.
Examples Double spaces Typographical errors (missing non-breaking spaces) Semantic error Wrong spelling, grammar or language Different fonts in the same sentence Double punctuation Text not conforming with the reference model Typing errors
On WAT we assign the following three levels of severity to bugs: Blocking, Major, Minor. In the Severity field we added "Suggestion" in the case of feedback rather than a bug.
The bug prevents access to a feature or module; it stops the progress of the tests. This is the highest severity.
Examples The link/button "X" is not present When you click on the "Validate" button, the page reloads Unable to add credit to my account The page does not load (infinite loading) Text entry not possible Scrolling the page is impossible During the validation the shopping cart empties and the order is not confirmed Valid information is not accepted as such The application systematically crashes at point "X" The "X" box to be checked is missing Unable to install the application "X" page is not reachable
The bug is very inconvenient for the user, but it does not block any important functionality, or test progress; it can be bypassed.
Examples The pop-in does not contain any text Page that takes more than X seconds to load Broken or missing image The page is not responsive Filter selection not possible Absence of sound Information cannot be shared on social networks The "X" field is not indicated as mandatory
The bug represents only a small inconvenience for the user, it does not block any functionality, and does not hinder the proper use of the product by the user.
Examples Typing errors A graphic element is blurred/pixelated Pictures in the wrong place, offset Font with different writing in the same sentence Video not playing automatically An anchor redirecting to a wrong position When hovering over the button, it does not change color One graphic element is overlaid on top of another Text or block alignment problem Ability to enter numbers in a text field The information is not pre-filled
Suggestion severity does not exist in test, but for practical reasons, it was decided to create this type of severity in order to be able to record the testers' feedback through an anomaly ticket.
Examples The report is sent without message or subject. An error message indicating to the user that these fields are empty would be welcome The "Play" button downloads another applicatio. You should rename this button because the term "play" implies that you will play in the same application and you may be surprised to see an unwanted download.
This field allows you to give additional information on the frequency of the fault occurring. The tester indicates if it is unique, random, present all the time or if he has not tested it by choosing the corresponding item from the drop-down list.
The tester chooses from the list the device(s) impacted by the bug he is describing. A bug must be linked to at least one or more devices.
Each bug must be justified when possible:
Each graphical bug must be supported by a screenshot with highlighted elements or by a video if necessary
Each crash of an application must be provided with a crash log
In the Bugtracker, once you have clicked on the "Start" (or "Resume") button in front of the device you need to test, go to the Bug List.
If you encounter a bug that has already been reported, you can confirm this bug by clicking on the + icon at the end of the bug line.
You will then be asked to prove your confirmation by adding a screenshot taken from your test device.
You can also do the same thing into the bug page.
Click on the bug to open it then :
You will get a remuneration corresponding to a part of the total remuneration of this bug.
For more information about the remuneration, please consult this page.
You will need computer tools to be able to properly perform your tasks on WAT. We remind you that you must not disclose any information or data that passes through We Are Testers. Thus we ask you not to use any online tool on which you would have to send these data (a screenshot/video for example) for any treatment. You must therefore use exclusively tools on your computer. Here are some examples:
You will (often) have to take screenshots to justify a bug ticket. Remember to frame in color the precise elements of the visual bug.
It may be necessary to take a video rather than a Screenshot to illustrate and explain a bug.
For Android :
For iOS :
Connect your iOS device to your computer.
Sync the device with iTunes, so that all crash-related information is copied to your computer.
Access the following directory to retrieve the log files:
On Mac OS X : ~/Library/Logs/CrashReporter/MobileDevice/
On Windows XP : C:\Documents and Settings\(User_name)\Application Data\Apple computer\Logs\CrashReporter\
On Windows Vista and Windows 7, 8 or 10 : open a runtime window by pressing the Windows key (between CTRL and ALT) and R at the same time, and type the following command: %USERPROFILE%\AppData\Roaming\Apple Computer\Logs\CrashReporter\MobileDevice\
Follow these steps to retrieve your UDID:
The easiest way is to download one app dedicated to retrieve it for you. You can download either Device ID by Redphx or Device ID by Evozi.
A good practice to implement is to create a first "template" bug with the expected nomenclature (by the client/the Project Manager) for the tickets on this mission, which will have to be removed at the end of the mission (leave it as submitted so as not to forget it).