#3,519 in Computers & technology books
Use arrows to jump to the previous/next product

Reddit mentions of Managing the Testing Process: Practical Tools and Techniques for Managing Hardware and Software Testing

Sentiment score: 1
Reddit mentions: 1

We found 1 Reddit mentions of Managing the Testing Process: Practical Tools and Techniques for Managing Hardware and Software Testing. Here are the top ones.

Managing the Testing Process: Practical Tools and Techniques for Managing Hardware and Software Testing
Buying options
View on Amazon.com
or
    Features:
  • John Wiley Sons
Specs:
Height9.25 Inches
Length7.375 Inches
Number of items1
Release dateJuly 2009
Weight2.64995638924 Pounds
Width1.52 Inches

idea-bulb Interested in what Redditors like? Check out our Shuffle feature

Shuffle: random products popular on Reddit

Found 1 comment on Managing the Testing Process: Practical Tools and Techniques for Managing Hardware and Software Testing:

u/soundstesty ยท 5 pointsr/QualityAssurance

For reporting the bugs, use one bug report card per bug, not one Trello card per type of bug. So if you find 3 broken links in the same page/floater plus one crash when clicking OK, write 4 bug reports.

Try to gauge the size of each bug, and try to allocate your own time accordingly. If you think it's a nasty bug, spend more time being specific about it. If it's a typo or a minor issue, spend less time. Just make it reproducible.

Follow this general template for creating bug reports, especially in a tool like Trello where you really just get a freeform text field plus a few extras. Each bug report should contain:
Summary (card title): Brief sentence saying what the problem actually is.
Steps to Reproduce:

    1. Note each step you took
    1. To make the bug happen
    1. Just like this.
    1. Include what ACTUALLY happened
    1. And include what you EXPECTED to happen.

      Try reproducing it several times and note your success rate. e.g. Reproduced 3/5 attempts.

      That's a really basic start (not complete at all!) to at least get you to a basic level you can build on piece by piece.

      If you're going to do this for more projects, a good book to invest in is Rex Black's Managing The Test Process. It basically gets you set up as an independent QA consultant able to approach any project, whether at a big company or a little company with zero QA.

      There are many routes into and through QA, but good bug reporting and basic bug management is a core skill you'll use all career long.

      Best of luck!

      Edit: minor formatting