100% satisfaction guarantee Immediately available after payment Both online and in PDF No strings attached
logo-home
2. Reporting and analyzing bugs with 100% correct answers £8.31   Add to cart

Exam (elaborations)

2. Reporting and analyzing bugs with 100% correct answers

 0 view  0 purchase

Reporting and analyzing bugsTo write a fully effective report you mustKind of error to reportwhy do testers have to sell bugs?objectives of selling bugsfollow-up testingtypes of follow-up testingmake old bug new bugshow it is more generalthings that make programmers resist fixing the bugreasons for...

[Show more]

Preview 1 out of 3  pages

  • January 3, 2023
  • 3
  • 2022/2023
  • Exam (elaborations)
  • Questions & answers
All documents for this subject (9)
avatar-seller
HIGHSCORE420
2. Reporting and analyzing bugs



To write a fully effective report you mustcorrect answers- Explain how to reproduce the
problem.
- Analyze the problem to describe it with a minimum number steps.
- Write complete, easy to understand, non-antagonistic report.

Kind of error to reportcorrect answers- Coding error.
- Design issue.
- Requirements issue.
- Documentation/Code mismatch.
- Specification/Code mismatch.

Bug reportscorrect answers- is a tool used to sell the programmer on the idea of
spending his time and energy to fix a bug.
- your primary work product as a tester.
- the best tester is the one who gets the most bugs fixed.

why do testers have to sell bugs?correct answerstime is in short supply so if you want
the programmer to spend his time fixing your bug, you have to sell him on it.

objectives of selling bugscorrect answers- motivate the buyer
- overcome objections

follow-up testingcorrect answerswhen find a failure, keep testing it to prove that it is:
- more serious than it first appears.
- more general than it first appears.

types of follow-up testingcorrect answers- vary the behavior.
- vary the options and settings of the program.
- vary the configuration (sw/hw environments).

make old bug new bugcorrect answersargue that an old bug should be treated as new if
you can find a new variation/symptom that didn't exist in previous release.

show it is more generalcorrect answers- look for configuration dependence.
- uncorner your corner cases (try extreme, mainstream inputs)

things that make programmers resist fixing the bugcorrect answers- cannot replicate the
incident.

The benefits of buying summaries with Stuvia:

Guaranteed quality through customer reviews

Guaranteed quality through customer reviews

Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.

Quick and easy check-out

Quick and easy check-out

You can quickly pay through credit card for the summaries. There is no membership needed.

Focus on what matters

Focus on what matters

Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!

Frequently asked questions

What do I get when I buy this document?

You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.

Satisfaction guarantee: how does it work?

Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.

Who am I buying these notes from?

Stuvia is a marketplace, so you are not buying this document from us, but from seller HIGHSCORE420. Stuvia facilitates payment to the seller.

Will I be stuck with a subscription?

No, you only buy these notes for £8.31. You're not tied to anything after your purchase.

Can Stuvia be trusted?

4.6 stars on Google & Trustpilot (+1000 reviews)

75323 documents were sold in the last 30 days

Founded in 2010, the go-to place to buy revision notes and other study material for 14 years now

Start selling
£8.31
  • (0)
  Add to cart