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
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
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.
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
revised Who should write the test plan?
deleted 11 characters in body
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 )
Feb
19
answered Who should write the test plan?
Feb
15
comment Are there any unions for software developers?
It is worth pointing out that in the UK for instance, the time you spend as a union member has NO effect on whether you get a role. The restrictions this answer discusses just aren't relevant to the way unions work here.
Feb
14
comment Should programmers help testers in designing tests?
This is such a strange idea. My mind is plenty polluted already - I'm a tester, by definition I'm a nosy type who pokes around looking at everything. I've never met a dev who could "pollute" my mind just by talking about their own test ideas - test ideas spawn more test ideas in my experience. And knowing what your prejudices and blind spots are can be very useful.
Feb
14
comment Do you count a Masters in CS as a negative?
Yes, good point - I'd completely forgotten about those.
Feb
13
awarded  Critic
Feb
13
answered Should testers automate their work?
Feb
13
awarded  Editor