Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

IT-EL QUIZ > Week 7 - Defect/Bug Life Cycle in Software Testing > Flashcards

Week 7 - Defect/Bug Life Cycle in Software Testing Flashcards

goodluck ><

1
Q

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

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

A

Defect/Bug Status

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

Defect States Workflow

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
4
Q

Defect States Workflow

When a developer makes a necessary code change and
verifies the change, he or she can make bug status as “____”,

A

Fixed

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

Defect States Workflow

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, the status assigned is “________”.

A

Pending re-test

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

Tester does the retesting of the code at this stage to
check whether the defect is fixed by the developer or not and
changes the status to “________”.

A

Re-test

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

Arrange this defect state flow in a correct order:
Assigned, retest, pending Retest, Verified, closed, new, open, fixed.

A

new => assigned => open => fixed =>pending retest => retest => verified => closed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
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. Bug report helps to identify similar bugs in future so it can be avoided.

A

Bug Reporting

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

is a systematic process to identify and fix bugs

A

Defect Management

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

What are the 6 Defect Management Process?
(D, C, R, V, C, R)

A

Discovery, Categorization, Resolution, Verification, Closure and Reporting.

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

3 Discovery Phase
(D, R, A)

A

Discover defect,
Report defect,
Accept defect

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

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

A

Defect categorization

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

[ Choose the Correct Priority ]

Critical | High | Medium | Low

The website performance is too slow

A

High

The performance bug can cause huge inconvenience to user

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

[ Choose the Correct Priority ]

Critical | High | Medium | Low

The GUI of the website does not display correctly on mobile devices

A

Medium

The defect affects the user who use Smartphone to view the website.

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

[ Choose the Correct Priority ]

Critical | High | Medium | Low

Some links doesn’t work

A

Low

the user can still still access the site without these links

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

is a step by step process of fixing the defects

A

Defect Resolution

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

6 step to fix the defects

A

Assignment, schedule fixing, fix the detect, report the resolution, verificaiton and closure

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

When a ____ defect is logged and posted for the first time. It is assigned a status as ____.

A

New

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

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
20
Q

The tester re-tests the bug after it got fixed by the developer. If there is no bug detected in the software, then the bug is fixed and the status assigned is “________.”

A

Verified

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

If the bug persists even after the developer has fixed the bug, the tester changes the status to “________”. Once again the bug goes through the life cycle.

A

REopen

22
Q

If the bug is no longer exists then tester assigns the status “_____.”

A

Closed

23
Q

If the defect is repeated twice or the defect corresponds to the same concept of the bug, the status is changed to “_______.”

A

Duplicate

24
Q

If the developer feels the defect is not a genuine defect then it changes the defect to “________.”

A

Rejected

25
Q

If the present bug is not of a prime priority and if it is expected to get fixed in the next release, then status “________” is assigned to such bugs

A

Deferred

26
Q

If it does not affect the functionality of the application then the status assigned to a bug is “________”.

A

Not a bug

27
Q

Unique identification number for the defect

A

Defect ID

28
Q

Detailed description of the Defect including information about the module in which Defect was found.

A

Defect description

29
Q

________ of the application in which defect was
found.

A

Version

30
Q

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

A

Steps

31
Q

Date when the defect is raised

A

Date Raised

32
Q

where in you Provide reference to the documents like . requirements, design, architecture or maybe even screenshots . .

A

Reference

33
Q

Name/ID of the tester who raised the defect

A

Detected By

34
Q

Name/ID of the developer who fixed it

A

Fixed by

35
Q

Date when the defect is closed

A

Date Closed

36
Q

which describes the impact of the defect on the application

A

Severity

37
Q

which is related to defect fixing urgency.

A

Priority

38
Q

In the _______ _______, the project teams have to discover as many defects as possible, before the end customer can discover it.

when it is acknowledged and accepted by the developers.

A

Discovery Phase

39
Q

help the software developers to prioritize their tasks.

A

Categorization / Defect categorization

40
Q

The defects that need to be fixed immediately

A

Critical

41
Q

defect impacts the product’s main features

A

High

42
Q

defect causes minimal deviation from product requirement

A

Medium

43
Q

defect has very minor affect product operation

A

Low

44
Q

in software testing is a step by step process of fixing the defects.

A

Defect Resolution

45
Q

Steps to fix the defect

Assigned to a developer or other technician to fix, . .

A

Assignment

46
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

47
Q

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

A

Fix the defect

48
Q

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

A

Report the resolution

49
Q

After the development team fixed and reported the defect,
the testing team verifies that. . .

A

Verification

50
Q

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

A

Closure

51
Q

in software testing is a process in which test managers prepare and send the defect report to the management team for feedback . .

A

Defect reporting

52
Q
A

IT-EL QUIZ (8 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions