SQA - Bug Report Flashcards Preview

Software Testing > SQA - Bug Report > Flashcards

Flashcards in SQA - Bug Report Deck (9)
Loading flashcards...
1
Q

What is a bug?

A

Mismatch between actual behavior of a software application and its intended(expected) behavior. We learn about expected behavior from requirements, specifications, and other technical documentation.

2
Q

Which type of testing results in highest number of bugs found?

A

Negative testing (versus Positive testing of same type)

3
Q

What are bug report component?

A
  1. Short description(problem summary)
  2. Steps to reproduce
  3. Severity(Critical, Serious, Minor, Suggestion)
  4. Priority (High, Medium, Low)
  5. Status (Open, Pending, Fixed, Closed, cannot reproduce,etc)
4
Q

What is a bug life cycle?

A
  1. Bug found
  2. Bug reported
  3. Bug assigned (to developer)
  4. Bug fixed (by developer)
  5. Bug fixed verified (by QA)
  6. Bug closed
5
Q

How can a tester be sure that bug was fixed?

A

Execute the steps (steps to reproduce) in the bug report

6
Q

What is bug tracking system?

A

A software application that:

  1. report bugs
  2. track bugs
  3. close bugs
  4. run analysis; monitor and summarize results
  5. quality improvement
7
Q

How do you write a bug report?

A
  1. Rule of WWW - What happened, where it happened , under which circumstance ?
  2. One bug report for each fix to be verified
  3. As complete as possible
  4. As concise as possible
  5. Report a bug immediately, DO NOT postpone
  6. User technical terms
8
Q

If you find a bug and the developer say it is as-designed, what can you do?

A
  1. find an exact requirement, which defines the way it should be designed
  2. if there is no specific requirement compare to same feature implemented in quality applications (ask your manager which applications to compare to)
9
Q

What would you do if developers cannot reproduce your bugs?

A

As a tester, you:
Reproduce on your computer;
Then reproduce on 1-3 other computers;

If you can reproduce the defect:
Compare developer’s and your working environment;
If environment is the same, make sure that steps to reproduce used by both are exactly the same;
Ask developer to debug on QA environment with his/her tools.