Unit 7 Flashcards

1
Q

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.

A

Defect life cycle

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

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

A

Defect Status

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

what defect status??

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

A

new

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

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

A

Assigned

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

what defect status??

The developer starts analyzing and works on the defect fix

A

Open

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

what defect status??

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

A

Fixed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

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,

A

pending retest

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

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

A

retest

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

what defect status??

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

A

Verified

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

what defect status??

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

A

Reopen

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

what defect status??

If the bug is no longer exists

A

Closed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

what defect status??

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

A

Duplicate

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

what defect status??

If the developer feels the defect is not a
genuine defect

A

Rejected

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

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

A

Deferred

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

If it does not affect the functionality of the
application

A

Not a bug

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are the Defect status

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

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.

A

Bug report

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

What are the details in reporting a bug?

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

This part of Bug Report is

Unique identification number for the defect

A

Defect ID

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Bug Report should is

including information about the module in which Defect was found.

A

Defect Description,

21
Q

Bug Report should is

Version of the application in which defect was
found.

A

Version

22
Q

Bug Report should is

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

A

steps

23
Q

Bug Report should is

Date when the defect is raised

A

Date Raised

24
Q

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.

A

Reference

25
Q

Bug Report should is

Name/ID of the tester who raised the defect

A

Detected By

26
Q

Bug Report should is

Status of the defect

A

Status

27
Q

Bug Report should is

Name/ID of the developer who fixed it

A

Fixed by

28
Q

Bug Report should is

Date when the defect is closed

A

Date Closed

29
Q

Bug Report should is

which describes the impact of the defect on the
application

A

Severity

30
Q

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

A

Priority

31
Q

is a systematic process
to identify and fix bugs

A

Defect Management

32
Q

What are the Defect Management Process?

A

Discovery, Categorization, Resolution, Verification, Closure, Reporting

33
Q

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.

A

Discovery phase

34
Q

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.

A

Categorization phase

35
Q

Four types of defect categorization

A

Critical, high, medium, low

36
Q

types of defect categorization

The defect has very minor affect product operation

A

Low

37
Q

types of defect categorization

The defect already causes minimal deviation from product requirements

A

medium

38
Q

types of defect categorization

The product impacts the product’s main purpose

A

High

39
Q

types of defect categorization

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

A

Critical

40
Q

is a step by step process of fixing the defects.

A

Defect Resolution

41
Q

Defect Resolution process helps to fix and track defects easily.

A
  • 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.
42
Q

Steps to fix the defect

A

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

43
Q

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

A

Assignment

44
Q

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

A

schedule fixing

45
Q

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

A

fixing the defect

46
Q

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

A

report the solution

47
Q

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

A

Verification

48
Q

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

A

Closure

49
Q

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.

A

Defect Reporting