In addition to Michael Durrant's excellent answer :
Take time to make accurate bug reports. My rules of a thumb(I've been on both sides of the equation, which helps) :
- Every hour spent in digging into the bug from the tester's point of view spares one day of work for the developer. Properly checking the exact conditions of the bug, the exact parameters, helps a lot for the correction.
- Every bug report completed in less than 15 minutes is doomed to lead to a correction that is not correct. Make both screenshots & a full text description of what's happening.
"Entering low amounts in the tax fields crashes randomly" is far less informative to the developer than:
"in the tax field
when the customer has an address abroad
when the tax amount is strictly inferior to 1.00$
when you press the continue button
a technical pop-up appears with the following information
tested on machine blahnlah version 3.14159, occurs also on machine blublu with the same version 3.14159 - worked fine on version 3.14158"
If you add a few screenshots to show what's happening, the developer will have an easy job. And they are going to like you.
OTOH, if you limit yourself to the first line, without any screenshots or additional information, they're going to doubt your added value.