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

  • 0 posts edited
  • 0 helpful flags
  • 582 votes cast
Apr
13
comment What I need to do to learn Quality Assurance?
Your understanding of "exploratory testing" seems to be somewhat lacking - try Cem Kaner's definition first: satisfice.com/kaner/?p=42 (he coined the term), and then try reading this: developsense.com/blog/2008/09/evolving-understanding-about There is nothing in the definition of "exploratory testing" that excludes any type of functional or non-functional testing.
Apr
7
answered What's a good book to help non-technical management understand software development?
Apr
4
answered What should I know or learn to get up to speed on being a software QA engineer?
Apr
4
comment What should I know or learn to get up to speed on being a software QA engineer?
The paper sounds a lot more relevant to a manufacturing environment than to a development environment: what made you recommend it?
Apr
3
comment Key phrases showing benefits performing certified software testing for “your” company?
And what benefit does that certification give the customer - does ISTQB promise to indemnify your customer against your (potential) incompetence? Do they promise to decertify you if a customer provides evidence that you have behaved improperly? Or is it just intended as a marketing aid?
Mar
28
answered Is it reasonable for QA department to get higher average salary than that of development department?
Mar
16
comment Can an agile shop really score 12 on the Joel Test?
@Simon - if your agile testers don't care to call themselves testers, I guess they've never heard of Elisabeth Hendrickson, Lisa Crispin, Janet Gregory...
Mar
13
comment How to Structure Bonuses for Software Developers?
I've seen extreme versions of this, where different depts would not cooperate on anything that ran the risk of reducing their bonus score. It really didn't matter if it cost the company money, it was purely "will I get my bonus? Then I don't care if we lost 2 highly trained engineers to the competition".
Mar
13
comment How to Structure Bonuses for Software Developers?
If people are slacking in an otherwise well-performing group, and this isn't due to some temporary issue (health problems, recent bereavement, etc), then surely the way to deal with this is to ask them to improve, or leave? Carrying a team member who is incapable or unwilling to do the work is a huge destroyer of morale. I don't think incentives are a good way to deal with that issue. +1 for your point in the first paragraph.
Feb
22
awarded  Civic Duty
Feb
21
comment Daily standups- yea or nay?
@Jaco - testers aren't part of your Scrum team?
Feb
21
awarded  Good Answer
Feb
20
awarded  Mortarboard
Feb
20
comment How To Know When To Stop Testing?
Though I'd completely agree: it's not done until it's tested. (I tend to agree with the idea that we'd be better off using the term "fixing phase" than a testing phase.) My disagreement is just that I think testing is inherently open-ended - you can never draw a line and say "there are no more tests we could possibly do now", just "there are no more tests we think it's worth doing now".
Feb
20
awarded  Nice Answer
Feb
20
comment Mock Objects for Testing - Test Automation Engineer Perspective
@Evans - I agree with user9009, your comment deserves to be one of the answers. It's useful info and may be missed by people who don't read all the comments.
Feb
20
awarded  Suffrage
Feb
20
comment How To Know When To Stop Testing?
+1 for continuous small deliveries and early testing. This also has the effect that defects are easier to fix, as the original programmer is still in context and hasn't moved on to another area. I'm now working in an environment where we do this and it's scary how much more productive everyone is.
Feb
20
comment How To Know When To Stop Testing?
As a system tester, I've rarely been in the position where the release date got delayed for more testing. I know I will never test anything completely - what I try to do is prioritise. Obviously, the quality of the calls I make about which areas to test first are dependent on the information I get about technical risk and business importance. The most important thing is that it should ALWAYS be a business decision and not a dev/test decision about what level of risk the company is willing to take on. We can advise, but it's the business that must decide.
Feb
20
comment How To Know When To Stop Testing?
The rate of finding new bugs is highly dependent on external factors, and sadly - some project managers will game this. Cem Kaner cites examples of the test team being sent to the movies so that the bug discovery rate would drop, and the PM could ship.