Unit 7 Flashcards by ITABLE JUSTINE

The purpose of __________ is to easily coordinate and communicate current status of defect which changes to various assignees and make the defect fixing process systematic and efficient.

Defect life cycle

How well did you know this?

Not at all

Perfectly

in defect life cycle is the present state from which the defect or a bug is currently undergoing.

Defect Status

How well did you know this?

Not at all

Perfectly

what defect status??

When a new defect is logged and posted for the first time.

new

How well did you know this?

Not at all

Perfectly

what defect status??

Once the bug is posted by the tester, the lead of the tester approves the bug and assigns the bug to the developer team

Assigned

How well did you know this?

Not at all

Perfectly

what defect status??

The developer starts analyzing and works on the defect fix

Open

How well did you know this?

Not at all

Perfectly

what defect status??

When a developer makes a necessary code change and verifies the change,

Fixed

How well did you know this?

Not at all

Perfectly

what defect status??

Once the defect is fixed the developer gives a
particular code for retesting the code to the tester. Since the software testing remains pending from the testers end,

pending retest

How well did you know this?

Not at all

Perfectly

what defect status??

Tester does the retesting of the code at this stage to check whether the defect is fixed by the developer or not

retest

How well did you know this?

Not at all

Perfectly

what defect status??

The tester re-tests the bug after it got fixed by the developer. If there is no bug detected

Verified

How well did you know this?

Not at all

Perfectly

what defect status??

If the bug persists even after the developer has fixed the bug,

Reopen

How well did you know this?

Not at all

Perfectly

what defect status??

If the bug is no longer exists

Closed

How well did you know this?

Not at all

Perfectly

what defect status??

If the defect is repeated twice or the defect
corresponds to the same concept of the bug

Duplicate

How well did you know this?

Not at all

Perfectly

what defect status??

If the developer feels the defect is not a
genuine defect

Rejected

How well did you know this?

Not at all

Perfectly

what defect status??

If the present bug is not of a prime priority and
if it is expected to get fixed in the next release

Deferred

How well did you know this?

Not at all

Perfectly

If it does not affect the functionality of the
application

Not a bug

How well did you know this?

Not at all

Perfectly

What are the Defect status

New,
assigned,
open,
fixed,
pending retest,
retest,
verified,
reopen,
closed,
duplicate,
rejected,
deferred,
not a bug

How well did you know this?

Not at all

Perfectly

contains each detail
about bugs like description, date
when bug was found, name of
tester who found it, name of
developer who fixed it, etc. ______ helps to identify similar bugs in future so it can be avoided.

Bug report

How well did you know this?

Not at all

Perfectly

What are the details in reporting a bug?

Defect ID,
Defect Description,
Version,
Steps,
Date Raised,
Reference,
Detected By,
Status,
Fixed by,
Date Closed,
Severity,
Priority

How well did you know this?

Not at all

Perfectly

This part of Bug Report is

Unique identification number for the defect

Defect ID

How well did you know this?

Not at all

Perfectly

Bug Report should is

including information about the module in which Defect was found.

Defect Description,

Bug Report should is

Version of the application in which defect was
found.

Version

Bug Report should is

Detailed ___ along with screenshots with which the developer can reproduce the defects.

steps

Bug Report should is

Date when the defect is raised

Date Raised

Bug Report should is

where in you Provide _______ to the
documents like . requirements, design, architecture or
maybe even screenshots of the error to help understand the defect.

Reference

Bug Report should is Name/ID of the tester who raised the defect

Detected By

Bug Report should is Status of the defect

Status

Bug Report should is Name/ID of the developer who fixed it

Fixed by

Bug Report should is Date when the defect is closed

Date Closed

Bug Report should is which describes the impact of the defect on the application

Severity

Bug Report should is which is related to defect fixing urgency. could be High/Medium/Low based on the impact urgency at which the defect should be fixed respectively

Priority

is a systematic process to identify and fix bugs

Defect Management

What are the Defect Management Process?

Discovery, Categorization, Resolution, Verification, Closure, Reporting

What phase in DMP is this? the project teams have to discover as many defects as possible, before the end customer can discover it. A defect is said to be discovered and change to status accepted when it is acknowledged and accepted by the developers.

Discovery phase

help the software developers to prioritize their tasks. That means that this kind of priority helps the developers in fixing those defects first that are highly crucial.

Categorization phase

Four types of defect categorization

Critical, high, medium, low

types of defect categorization The defect has very minor affect product operation

Low

types of defect categorization The defect already causes minimal deviation from product requirements

medium

types of defect categorization The product impacts the product's main purpose

High

types of defect categorization The defects that needs to be fixed immediately because it may cause great damage to the product

Critical

is a step by step process of fixing the defects.

Defect Resolution

Defect Resolution process helps to fix and track defects easily.

* Defect resolution process starts with assigning defects to developers * then developers schedule the defect to be fixed as per priority * then defects are fixed * developers send a report of resolution to the test manager.

Steps to fix the defect

Assignment, schedule fixing, fixing the defect, report the solution

Assigned to a developer or other technician to fix, and changed the status to Responding.

Assignment

The developer side take charge in this phase. They will create a schedule to fix these defects, depend on the defect priority.

schedule fixing

While the development team is fixing the defects, the Test Manager tracks the process of fixing defect compare to the above schedule.

fixing the defect

Get a report of the resolution from developers when defects are fixed.

report the solution

After the development team fixed and reported the defect, the testing team verifies that the defects are actually resolved.

Verification

Once a defect has been resolved and verified, the defect is changed status as closed.

Closure

is a process in which test managers prepare and send the defect report to the management team for feedback on defect management process and defects’ status.

Defect Reporting