class 2: Software Testing basics

Life Cycle (SDLC)
Roles of team members during each phase
Responsibilities of

a tester in each phase of SDLC
What is a bug (defect, issue, etc.)?
Lifecycle of a bug
What is a Bug Tracking System?
Introducing JIRA and Bugzilla
What is a bug report?
How to create a perfect bug report

of steps or phases in the development of a software

application
Each phase produces deliverables that serve as inputs to the next phase of the life cycle
First, User Requirements are translated into a design.
Then code is produced according to the design in the development (code) phase
After coding, the application is implemented and ready for the test phase
The test phase verifies the software against requirements
when successfully tested, the software is deployed and ready for use by end users

design)
implementation (create system)
test (unit, integration, system, regression, user acceptance)
deploy (delivery

to user)

plan for the project
design the test per user requirements
execute the

test during the test phase of the software development life cycle
analyze test results and provide statistical reports

test design

test planning

analysis & reporting

test execution

initiation

completion

a developer
fixed and unit tested by developer
re-tested by reporter
re-opened if

test fails
closed if test is successful

fix

re-open

retest

close

assign

defer/decline

new/open

class 2: Software Testing basics: Bug Life Cycle

codes a fix
the developer tests the fix
the tester tests the

fix
the tester closes or re-opens the bug

fix

re-open

retest

close

assign

defer/decline

new/open

class 2: Software Testing basics: Bug Life Cycle

re-classified (not a bug)
it may be deferred
it may be fixed

in a future release

fix

re-open

retest

close

assign

defer/decline

new/open

class 2: Software Testing basics: Bug Life Cycle

Software Testing basics: Bug Tracking Systems

e-mail
class 2: Software Testing basics: Bug Tracking Systems

entire SDLC
class 2: Software Testing basics: Bug Tracking Systems

Bug Tracking Systems

Software Testing basics: Bug Reports

report?

a bug, documented properly in a bug tracking system or

any other way, describing the issue (error) you’ve faced while testing software

The main goal of creating a bug report is to get the bug fixed as soon as possible

the bug report is designed to help the developer reproduce the problem and fix it ASAP.

Bug reports are your primary work product!

report:

Summary (subject, name)

Description

Steps to Reproduce

Expected result (how we would expect

software to behave in this situation as per requirements or user experience)

pass/fail condition

Actual result (the error or issue itself)

bug for the following scenario:

the web site is www.my-address.com (not

a real web site)

I went to the web site to enter my address

I couldn’t enter my home state of Illinois

The page had a drop-list (field with down-arrow) for state code values