Cultivăm dorința de evoluție personală!

Un proiect al Asociației pentru Educație Informală, în colaborare cu:

Griffiths School of Management; Soluții Avansate SRL; Talpoș &
Partners SRL, Organizația Tineret pentru Europa, Scoala
Internationala Cluj Napoca, Fortech, Endava, BCR, RedKiwi,
Psihoselect, BuzzNews si Radio Transilvania.
Prieteni
 Software Bug

• A flaw in a component or system that can

cause the component or system to fail to
perform its required function
• When the expected and actual behavior is
not matching
• Also known as issue, incident, error,
defect, flaw, mistake, failure, or fault in a
computer program
• E.g. the search doesn’t return all results,
the application crashes while login, the
password is not case sensitive
 Issues Types

• Bug
• Improvement
• Question
• Feature
• Task / Sub-task
 Bug Attributes

• Project
• Summary
– a short, clear, easy to understand bug summary
– E.g. Address Book: Error while a contact is edited
• Severity
– the impact of the bug
– E.g. :
• Blocker: blocks development and/or testing work
• Critical: crashes, loss of data, severe memory leak
• Major: major loss of function
• Normal: average loss of function, a workaround can be found
• Minor: minor loss of function or other problem where an easy workaround is
present, UI issues
• Priority
– the importance and order a bug should be fixed
– E.g. P1, P2, P3, P4 or low, normal, high, urgent, immediate
• Affects version
– the version in which the defect was found
 Bug Attributes - Description

Always follows the template:

Preconditions:
Steps to reproduce:
1. <step1>
2. <step2>
3. <step3>
Expected results:
Actual results:
 Bug Attributes

• Environment
– the environment on which the bug was found
– E.g. alpha2, staging
• OS and OS version
– E.g. Windows 7, iOS 7.2, Android 4.4 KitKat
• Component
– E.g. Search, Address Book, Alarms
• Fix version
– the version in which the bug was fixed or the feature was
implemented
• Assignee
– the person in charge to resolve / validate the feature / bug
• Reporter
– the person who found the bug
• Additional information: screenshot, estimations, due date
 Bug Management Tool

- Is a software application that keeps track of

reported software bugs in software development
projects
- Also known as bug tracking system/tool, issue
tracking system/tool, defect tracking system/tool
- Jira, Bugzilla, HP Quality Center (QC), Team
Foundation Server (TFS), Mantis
- Reference:
http://en.wikipedia.org/wiki/Comparison_of_issue-
tracking_systems
 Mantis Bug Tracking Tool

Address:
http://bugs.scoalainformala.ro/

Username:
<prenume>.<nume>

Password:
Received via email
 Report Bugs

Before reporting the bugs:

- Check that the correct app version is tested
- Check the requirements again
- Isolate the steps to reproduce for the bug
- Check that the bug doesn’t exist into the bug
tracking system
- Identify the expected application behavior if
not documented
 Report Bugs

While reporting the bugs:

- Provide clear and easy to follow steps to
reproduce
- Provide all additional information the
developer to be able to reproduce it
- Follow the project rules
- Provide a screenshot if necessary (“a picture
values like a thousand words”)
- Correct English usage
 Bug Life Cycle

Fixing
• New • Fixed • Fixed
• Reopen • Duplicate Validation • Duplicate
Validation • Invalid • Invalid
• Won’t Fix • Won’t Fix
• Cannot • Cannot
• Unassigned Reproduce Reproduce

Resolved
• Assigned

Closed
• Confirmed • No change • No change
required required
Open

• Not fixable • Not fixable

Validation