Chapter 19


1:

Cite a few reasons that a bug might not be fixed.

A1:

There's not enough time in the schedule, it's not a bug, it's too risky, it's not worth it, and the bug wasn't reported properly.

2:

What basic principles can you apply to your bug reports to give them the best chance of getting the bug fixed?

A2:

Log them as soon as possible. Effectively describe the bug, making sure it's minimal, singular, obvious and general, and reproducible. Be nonjudgmental in your approach. Follow the report through its life cycle.

3:

Describe a few techniques for isolating and reproducing a bug.

A3:

Record what you do and review it carefully. Use white-box test techniques to look for race conditions, boundary conditions, memory leaks, and other similar problems. See if the bug is state related, such as initial state or later state dependent. Consider resource dependencies and even hardware problems as the source of the bug.

4:

Suppose that you're running tests on the Windows Calculator and find that 1+1=2, 2+2=5, 3+3=6, 4+4=9, 5+5=10, and 6+6=13. Write a bug title and bug description that effectively describes this problem.

A4:

Title: Adding two even numbers gives an answer that's one too much.

Description:

Test Case: Simple addition

Setup Steps: Start Version 1.0 of Calculator

Repro Steps: Try adding two even numbers such as 2+2, 4+4, and 6+6.

Expected Result: Correct answer for all calculations2+2=4, 4+4=8…

Actual Result: For two even numbers, the answer is one too high2+2=5, 4+4=9, 6+6=13, and so on.

5:

What severity and priority would you give to a misspelling in a company's logo on the software's start-up screen?

A5:

Probably Severity 3 (minor problem), Priority 2 (must fix before release).

6:

What are the three basic states of a software bug's life cycle and the two common additional states?

A6:

Open, Resolved, and Closed are the basic states. Review and Deferred are two possible other states.

7:

List a few reasons that a database bug-tracking system is so much more useful than a paper-based system.

A7:

You can see at a glance what a bug's life cycle has beeneven if it has been complex. The current status of a bug can be instantly known. Bugs can't be lost or neglected as easily. Project statistics can be quickly obtained.



    Software Testing
    Lessons Learned in Software Testing
    ISBN: 0471081124
    EAN: 2147483647
    Year: 2005
    Pages: 233

    flylib.com © 2008-2017.
    If you may any questions please contact us: flylib@qtcs.net