1. Not finding the time to read all the books and blogs on testing that I want to.
2. Testing being seen as a checklist.
2a. Not realising until later (too late) that instead of complaining about it I should have worked on explaining testing.
4. W...
A lot of these items hit home for me. One in particular that seems to be a popular gripe is when a build is "thrown over the fence" with little or no error checking done on the developers' side. I'm wondering if anybody has come up with an eloquen...
Try reading What Is a Good Test Case ? by Cem Kaner
or this blog post How Much Detail Should I Write In My Test Case - I saw this talk at a recent SIGIST and it gave me some food for thought
Managers that ask for a QA strategy. After you spend time doing it they shorten everything for lack of time or resources. Why bother writing a strategy then?
I think it's feasible to at least classify/categorize results in a way that helps you prioritize your root cause analysis efforts. One tool I am aware of for this is DV Notebook from Achilles Test (www.achillestest.com) but I would be very interes...
I'm just wondering about the criteria for including a blog feed in the TESTER FEEDS section of the home page.
Many of them are useful feeds from individual testers' blogs. Good stuff. Kep them coming!
But a few are clearly just marketing, with no useful professional content. For example, we've recently been treated to a series of "look, we've won an award" blog entries from uTest. I think this dilutes the usefulness of these feeds to include such marketing hype.