Bugs Flashcards

1
Q

What is a bug?

A

Mismatch between actual behavior of a software app and its intended/expected behavior (we learn about expected behavior from requirements, specifications and other technical docs)

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

Name components of bug report

A

ID, title/summary, description, steps to reproduce, severity, priority, assigned to, environment, browser, device, status, attachments, actual result, expected result

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

Describe bug life cycle

A

Bug found and reported, dev manager sets ‘assigned to’ and priority, developer fixes the bug, tester validates that bug was fixed and closes bug (if not fixed - reopen)

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

When should you write bug report?

A

Right after found bug

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

Why do you need to write bug report?

A

Getting the bug fixed

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

What makes a good bug report?

A

Good title (where did the bug happened, what happened, under which circumstances), how to reproduce the bug, analyze the problem to minimize number of steps to reproduce, complete, easy to understand, non-conflicting

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

Who assigns severity and priority in bug report?

A

QA assigns severity, PO/Dev Manager assigns priority

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

Name levels of bug severity

A

Blocker (blocks from using functionality/crash), critical (unable to use functionality properly), major (functionality is not performing up to benchmarks), minor (inconvenient to use), trivial (cosmetic)

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

Which bug tracking system do you know?

A

Jira, Bugzilla, Mantis

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

What statuses can a bug have?

A

Open, Pending, Fixed/Resolved, Closed, Not reproducible, Deferred

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

What to do if Dev says that he can’t reproduce bug?

A

Make sure it’s reproducible on your side;
If was able to repro on your Pc, try to repro on couple more computers;
If reproducible, check that you and dev are working under same variables (e.g.: OS, app version, environment, browser and browser version, etc);
If needed show how to repro it or dev can show how he tried to repro bug; also, can ask Dev to debug in QA environment with his tools

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

What to do if Dev marked your defect “As Designed”?

A

Verify requirements; if there are no requirements - talk to the authority

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

What is Bug Tracking system used for?

A

Report bugs, track/update bugs, close/fix/defer/move to another system, to run statistical analysis, monitor and summarize results, work on quality improvements

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

Why do we need bug tracking DB?

A

Accountability, communication tool (between people and between departments), organize information, monitor individual performance

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