871 reputation
611
bio website softwaretestingclub.com/…
location
age
visits member for 4 years, 6 months
seen 11 hours ago

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
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 What quantitative metrics do you use to measure the quality of an offshore testing team?
Traceability matrix is only applicable to some very specific environments: if you're being asked to confirm compliance to requirements, then you would use it. It doesn't tell you anything however, about other quality aspects of the software, and should be regarded as a bad sign if used in an inappropriate project context.
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.
Mar
13
comment Is there value in having new developers (graduates) start as testers / bug-fixers?
Testers might write programmatic test cases, and test manually. I would expect testers to be able to bridge both sides - looking at the app from the technical and the business perspective - in order to create really challenging tests. In my organisation, there is a distinct separate role for "tester" - different training, different mindset, different (but overlapping in some places) skillset.
Mar
12
comment Is there value in having new developers (graduates) start as testers / bug-fixers?
+1 for pointing out the flaw in hiring people to do something, and having them spend the first year doing something else. However, as a tester, I'd say you're wrong about "Hire testers for the things that really need a face in front of the screen". Yes, that is a small part of what I do. But I don't always need my face in front of a screen to find issues - in fact, I often find a lot of issues before the code is even written. You are right that it's a different skill set. The point of having me or my tester colleagues on a team is because we practice looking at things differently.
Mar
11
comment What's the *ISTQB* and are they trustable?
Actually, some savvy employers are starting to say "if you have a certificate: we won't hold it against you", or even that they use it as an anti-filter - they discard any CV that mentions it. A very poorly regarded cert can become an indication of poor judgment.
Feb
26
comment What is the difference between a Software Test Engineer and Software Test Analyst?
There's never been that distinction in any team I've worked on - I'm sure it may exist in some teams, but it's by no means universal.
Feb
21
comment Daily standups- yea or nay?
@Jaco - testers aren't part of your Scrum team?
Feb
20
comment Who was your mentor? Where can I find mine?
Ran out of votes for today, or I'd vote up. I have learned so much from my mentor. I think it's a misunderstanding of what a mentor does: I was already reading and studying on my own, but in our discussions my mentor would challenge me on bad assumptions I'd made, push me to explain my thinking more clearly or to re-examine it for flaws, and point me at useful new ideas and ways of looking at stuff that I wouldn't necessarily have found on my own.
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
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
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.
Feb
19
comment Should testers automate their work?
Identifying button by id rather than location is perfectly possible with some tools. Record and play scripts done like that are STILL horrid to maintain, unfortunately - it doesn't solve the problem of repetition. I don't think there's any getting away from the need to design your test automation carefully, if you actually want to keep any scripts around or create more than a dozen of them. Have you thought of using something keyword-driven like Robot Framework along with Auto-It?
Feb
19
comment Who should write the test plan?
+1 for pointing out that user acceptance tests need to be designed by the user. Although I've suggested an alternative approach in my answer (as it doesn't seem that they actually have any QA resource), user acceptance testing can't be done effectively by non-users. In this situation, it sounds like both dev and users are at a bit of an impasse, so I think dev needs to try to break that somehow.
Feb
19
comment Who should write the test plan?
Good up till the last sentence, but testing should never stick merely to checking the application follows expectations (but should also cover the unexpected!), and knowing at least a bit about how the application was technically designed ALWAYS helps me as a tester to identify the cracks I can get my tester crowbar into to lever the thing wide open. ;) It's a bit of an old-fashioned notion to imagine that testers are better not knowing anything about the implementation.
Feb
19
comment Who should write the test plan?
If you're moving towards Agile, try to hire some people who specialise in testing into your current development team. (Note: read up on the different schools of testing first, some are not compatible with an Agile approach - redcanary.mypublicsquare.com/view/hiring-software )