0% found this document useful (0 votes)

39 views

Continental Test Lab: August 2014

....

Uploaded by

Ana Maria

Available Formats

Download as PPTX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

39 views

Continental Test Lab: August 2014

....

Uploaded by

Ana Maria

Available Formats

Download as PPTX, PDF, TXT or read online on Scribd

You are on page 1/ 20

Continental Test Lab

August 2014

Interior Infotaiment and Connectivity R&D Romania

Agenda

1Error, bug, fault, failure

2Defect Lifecyle
3TestCase creation
4Homework 2

Interior Infotaiment and Connectivity R&D Romania

2 11-03-26 Autor, © Continental Automotive Romania SRL
Bug, fault & failure

…is an “ERROR”??
…is a “Bug”??
…is Fault, Failure??

Interior Infotaiment and Connectivity R&D Romania

3 August 2014 , © Continental Automotive Romania SRL

Bug, fault & failure

A person makes an Error

That creates a Fault in software

That can cause a Failure in operation

Error : A human action that produces an incorrect result

Bug=Defect=Problem=Fault : A flaw in a component or system that can cause the

component or system to fail to perform its required function.

Failure : Deviation of the software from it`s expected result.

Interior Infotaiment and Connectivity R&D Romania

4 August 2014 , © Continental Automotive Romania SRL

Bug, fault & failure

Defects occur because:

Human beings are fallible

There is time pressure

Complexity of the code

Many system interactions

Example:

Function that implements the Current Balance for ATM view in a bank account.

GetUserCurrentBalance()

{ return sum/0; } – Human error

When the user will try to view the balance on the ATM it will be a bug, the module will crash.

At the end of the month, the bank will try to do the balance for all customers, the total balance
module will try to call this function for every customer, this will result in a failure.

5/
Autor
/Interior Infotaiment and Connectivity R&D Romania
Datu
m ©
Conti
Agenda

1Error, bug, fault, failure

2Defect Lifecyle
3TestCase creation
4Homework 2

Interior Infotaiment and Connectivity R&D Romania

6 11-03-26 Autor, © Continental Automotive Romania SRL
Defect lifecycle

Interior Infotaiment and Connectivity R&D Romania

7 August 2014 , © Continental Automotive Romania SRL

Defect lifecycle

It varies from organization to organization and also from project to project as it is governed
by the software testing process and also depends upon the tools used

In software development process, the bug has a life cycle

The bug should go through the life cycle to be closed
A specific life cycle ensures that the process is standardized. The bug attains different states
in the life cycle

A lifecycle is a set of rules that govern how users can modify and transition reported bugs.
For example, the lifecycle controls how the Bug Reporting Tool moves a reported problem
from one state to the next, such as from the entered state to the completed state

It starts when defect is found and ends when a defect is closed, after ensuring it’s not
reproduced

Interior Infotaiment and Connectivity R&D Romania

8 August 2014 , © Continental Automotive Romania SRL

Defect lifecycle

Defect Life Cycle Implementation Guidelines

Make sure the entire team understands what each defect status exactly means.
Make sure the defect life cycle is documented

Ensure that each individual clearly understands his/her responsibility as regards each
defect

Ensure that enough detail is entered in each status change. For example, do not simply
DROP a defect but provide a reason for doing so

Interior Infotaiment and Connectivity R&D Romania

9 August 2014 , © Continental Automotive Romania SRL

Defect lifecycle

Log new defect

When tester logs any new bug the mandatory fields are:
- Submitter name, Build version, Submit On, Product, Module, Severity, Synopsis and Description
to Reproduce, Occurrences
- Priority and ‘Assigned to’ fields

Can add some optional fields like:

Test Case ID -Test case identification for a particular defect. It is useful to track progress
Keyword(s) -This field contains some particular information about the bug, which can help in
minimizing the number of records to be searched.
Requirement / external reference – This field is to point to a specification of the functionality for
with the problem was reported

On successful logging the bug is reviewed by a supervisor and can set the bug status as Open
(depending on the tool), can Assign the bug to developer or bug may be deferred until next
release

Interior Infotaiment and Connectivity R&D Romania

10 August 2014 , © Continental Automotive Romania SRL

Defect lifecycle

When bug gets assigned to developer he can start working on it

Developer can set bug status as won’t fix, Couldn’t reproduce, Need more information or
‘Fixed’

If the bug status set by developer is either ‘Need more info’ or Fixed then tester responds
with specific action

If bug is fixed then tester verifies the bug and can set the bug status as verified closed or
Reopen

Interior Infotaiment and Connectivity R&D Romania

11 August 2014 , © Continental Automotive Romania SRL

Defect lifecycle

Bug status description:

These are various stages of bug life cycle. The status caption may vary depending on the
bug tracking system you are using

New: When the tester finds and reports the new bug
Triage Discussion:
Prioritize defects brought into Triage meeting
Determine which Release/Build the fix will be made in

Deferred (Postponed): If the bug is not related to current build or can not be fixed in
this release or bug is not important to fix immediately then the project manager can set
the bug status as deferred

Interior Infotaiment and Connectivity R&D Romania

12 August 2014 , © Continental Automotive Romania SRL

Defect lifecycle

Assigned: ‘Assigned to’ field is set by project lead or manager and assigns bug to
developer
Reproduce the defect, change status to OPEN
Recognize the bug and change status to 'Duplicate' of another bug and specify what
it is a duplicate of
Reproduce bug, recognize problem, make fix, unit test, check in code and change
status to 'Fixed'

Open: At this state the developer has started analyzing and working on the defect fix

Interior Infotaiment and Connectivity R&D Romania

Defect lifecycle

Resolved/Fixed: When developer makes necessary code changes and verifies the
changes then he/she can make bug status as ‘Fixed’ and the bug is passed to testing
team

Could not reproduce: If developer is not able to reproduce the bug by the steps given
in bug report by tester then developer can mark the bug as ‘CNR’
- Tester needs action to check if bug is reproduced and can assign to developer with
detailed reproducing steps

Need more information: If developer is not clear about the bug reproduce steps
provided by tester to reproduce the bug, then he/she can mark it as “Need more
information’
- In this case tester needs to add detailed reproducing steps and assign bug back to dev
for fix

Interior Infotaiment and Connectivity R&D Romania

Defect lifecycle

Test - The Defect is fixed and integrated and is ready for testing

Verified - The Defect that is retested and the test has been verified by tester

Closed: If bug is verified by the test team and if the fix is ok and problem is solved then
tester can mark bug as ‘Closed’

Reopen: If tester is not satisfy with the fix and if bug is still reproducible even after fix
then tester can mark it as ‘Reopen’ so that developer can take appropriate action

Rejected/Invalid: Some times developer or team lead can mark the bug as Rejected or
invalid if the system is working according to specifications and bug is just due to some
misinterpretation