Reputation
872
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
6 11
Newest
 Yearling
Impact
~12k people reached

  • 0 posts edited
  • 0 helpful flags
  • 582 votes cast
Feb
12
comment What are good requirements for a QA engineer?
That says rather a lot more about the kind of companies you've worked for than it does about testers in general. As Ethel says, you get what you expect - if you expect your testers to be mundane and pay accordingly, you simply won't attract really skilled testers.
Feb
12
comment Onsite Interview : QA Engineer with more Emphasis on Java Skills
+1 Great answer. I really like the idea of "framing" the interview in that way, and realised reading your answer that's actually how I've thought of all the successful interviews I've had: "cool, here's a chance to chat to nice new people about stuff we're both interested in".
Feb
3
comment Can you recommend a good test plan template?
Excellent - glad it was helpful. For brainstorming, have you thought about using mindmaps? This Lisa Crispin blog post describes how they used mindmapping for theme planning: lisacrispin.com/wordpress/tag/mind-maps
Feb
1
comment What quantitative metrics do you use to measure the quality of an offshore testing team?
I agree absolutely that it doesn't make sense to say bug fixes generally introduce a lot more bugs - and some of that >10% was likely just revealed by the fix, not introduced. However, I was responding to Jim's outlined scenario of code delivered that doesn't even run - in that case, yes, something is very wrong with that development process. I wouldn't expect those teams to be doing a great or even adequate job of bug fixing, as whatever caused the original problem is likely to apply just as much to the bug fixing. Sorry if that wasn't clearer in my original comment.
Jan
30
comment Where can I find statistics / figures on how long testing should / could take?
Then that's really a different question to the one you originally asked.
Jan
30
comment What quantitative metrics do you use to measure the quality of an offshore testing team?
Jim +1 for time given to test. It's a classic problem in a waterfall environment - test comes at the end, and always gets squeezed. To my mind, if you're 75% of the way through testing time before you get code that actually runs - this should be a huge red flag for the project manager that either the programmers did not get enough time to develop the product, or they did such a bad job that attempting to patch up the mess will only get you so far.
Jan
30
comment What quantitative metrics do you use to measure the quality of an offshore testing team?
Unfortunately, testers don't put the bugs in. They only find them. If the system is chock-full of bugs in the first place (and being fixed, cack-handedly by the same folks who created the original bugs, then your testing team will look bad by this metric, no matter how good they are, as each bug they report and get fixed will introduce several more.
Dec
10
comment What mistakes do your users make, and how can you update your application to handle them?
+1 for users "learn your software through exploration".
Dec
5
comment Do you believe it's a good idea for Software Engineers to have to work as Quality Assurance Engineers for some period of time?
Er, that assumes you're working in a place that pays skilled QA folk less than devs. I know some places do, but it doesn't reflect my experience - when I've known people's salaries they've generally been on a par.
Nov
30
comment How To Know When To Stop Testing?
I think you'd find Michael Bolton's blog post about stopping heuristics for testing useful to read: http://www.developsense.com/blog/2009/09/when-do-we-stop-test/ You may recognise some of the heuristics people have suggested in this thread.