How to write a bug

First step is to find it.

After you find the bug

Dont be so happy, you will have to check
it. First be sure that the steps you find for the reproduction of the bug are correctly. Second be sure that is not a DUPLICATE. Third check if the bug occurs somewhere else or how is affecting the game.

You have a Bug

Open the Jira Database

http://mdc-tomcatjira15.ubisoft.org/jira/secure/Dashboard.jspa (for training only).

Create new issue

Select Training as project and Bug Qc as Issue Type than click NEXT

Summary

This is usually a sentence as short as possible but most descriptive as possible. The nomenclature followed is; [The map where the bug can be found] A sentence describing the bug (and the platform if specific to a platform). For example: [Ep05 Beach05] AI Check Error when speaking to Locked

Description

This section is used to further describe a bug in details. As much information should be provided here.

Expected Behavior

The expected behaviour of a bug should be described here. It is basically what should occur in the game.

Steps to Reproduce

Used to list the steps followed in order to reproduce the bug. List them using: 1-, 2-, 3-, etc. Also there is an template that we use for writing the bug: Ex: For a graphic bug that occurs on a specific place on the map. When the user:

1. Enters the map. 2. Goes to the location shown in

picture. 3. Look at the tree. The following occurs:

1. The texture is flickering.

Note: The lines that are written with red are very important and must be written at all the bugs

Platform / Module

Specify on which platform the bug occurs on.

Affects Version/s

Specify the version where the bug was found. At no point in time should this field be modified. If the bug was checked on a later version and still occurs, the field Last Observed Product is used to specify that when editing a bug. (Ex. Lost_202)

Location

Specify the location where the bug can be found.

Sub Location

Specify the sub location of where the bug can be found

Severity
Give a severity to the bug depending on its gravity. IMPORTANT : Be sure that you chose correct severity.

Milestone

The milestones are the dead-lines established for different stages of the game. Ex: alpha, beta, master, etc.

Walkthrough Break

A field that allows the tester to set a bigger severity on a bug. All walkthrough breakers are S1 by default.

Workaround
Specify, using the drop-down list, if the bug can be avoided. ATTENTION!!! All the steps from the steps to reproduce must be respected. Once you eliminate or put one step the workaround is no longer available.

Component/s

Select the component that best describes the type of bug. On training you will choose Training Romania.

Assignee

Unless otherwise specified, the Components section will automatically send the bug. Therefore, this field need not to be filled unless an Assignee has been identified. For the training you will choose Ionut Socolovici.

Scope

Select the scope(s) that best describe the type of bug. Restrict from using multiple scopes if not needed. ATTENTION: The scope you chose is very important because if you dont choose the good scope(s) the bug can be assigned to a wrong developer.

Attachment

Select the picture files to be attached. Video files are also accepted but only used when a bug cannot be identified from a picture. The maximum file upload size if 10 MB, and up to 4 attachments can be posted. If a(n) attachment needs to be deleted/replaced, please see your Lead. ATTENTION: The pictures and movies that you attached must be clear and precise !!! Also must be renamed like in the following example: Ionut Socolovici that works at Lost on PS3. Isoc_Lost_Ps3_001.jpg(avi)

Repro Rate

Technical reproducibility usually should be 100% but if you cant find the steps that makes the bug 100% repro you will declare it at a small repro with the steps that you have. Also the reproducibility is not necessary based on percentage some leads might ask you to wrote how many tries on how many times occurs. Ex: a bug that appears 7 times on 15 tries will have a 7 of 15 repro.

Now you have the basics

by Soco