Bugs, Documentation

Question 1

Most important components of Bug Report?

Answer 1

Short Description (Title);
Steps to reproduce;
Severity;
Priority;
Status.

Question 2

Describe Bug life cycle

Answer 2

Bug found and reported;
Development Manager set “assigned to” and priority;
Developer fixes the bug;
Tester validated that bug was fixed (if not bug going back to developer) and closes the bug.

Question 3

What makes Bug Report good?

Answer 3

Follow WWW rule;
How to reproduce the bug;
Analyze the problem to minimize number of steps to reproduce it;
Complete, easy to understand, non-conflicting

Question 4

Levels of Severity

Answer 4

Critical/Fatal (crash, data corruption, security, hang);

Serious (workaround);

Minor;
Suggestion/Enhancement.

Question 5

Statuses of Bugs?

Answer 5

Open;
Pending;
Fixed/Resolved;
Closed;
Can’t Reproduce;
Deferred;

Question 6

Bug Tracking system is a software application, designed to?

Answer 6

Report bugs;
Track (update) bugs;
Close (fix, defer, move to another system);
To run the statistical analysis, monitor, and summarize the results;
Work on quality improvements.

Question 7

Why do we need Bug Tracking Database?

Answer 7

Accountability;

Communication tool (inter-personal and inter-departmental);

Organization of the information;

Monitoring individual performance;

Question 8

Why we use Test Cases?

Answer 8

Better testing coverage;
Re-usable;
Reviewable;
Traceable - know what is tested;
Tracking test results;
Creates a deliverable.

Question 9

What is Test Suite?

Answer 9

Is a collection of test cases that are intended to be used to test a software program to show that it has some specified set of behaviors

Question 10

What is Traceability Matrix?

Answer 10

Traceability Matrix is a table that correlates requirements (design documents) to test documents.