Reputation
1,651
Next privilege 2,000 Rep.
Access moderator tools
Badges
5 13
Impact
~50k people reached

  • 0 posts edited
  • 0 helpful flags
  • 177 votes cast
Jun
16
comment Bugs keep reappearing in our GUI software during development. How should this be addressed?
I'd agree with the test plan portion of this answer, if you have areas that continually regress you need a checklist, or plan, to make sure certain areas are ALWAY covered regardless. Whether this is automated, but might be hard if you have continual changes, or a checklist that can be used by Devs to check after they make changes you need something structured. I do the same when I have code that is continually changing, and also continually has issues.
Jun
13
comment What goes in your definition of done (DoD) ?
Never heard the term steel thread, but I like it. +1
Jun
10
answered Are code reviews considered part of QA?
Jun
10
comment How do you adapt agile testing techniques to a regulated industry?
I like this way of thinking, it takes documentation out of the "as needed bucket" and moves it to a feature and in this case I think covers it nicely.
Jun
2
comment Who is ultimately responsible for issues that are found after software is released?
I think when you note "coverage not good enough" as a rationale you also need to note schedules, sometimes the date is fixed and no manner of testing is going to get all your tests in a short window. You can try, but sometimes you have to pick and choose while dates slip. Sadly, this is still a case to consider.
Jun
1
comment Who is ultimately responsible for issues that are found after software is released?
+1 Very true, this is the way I have always looked at it
Jun
1
answered what should I do if my stability tests cycle is longer than the release cycle ?
Jun
1
comment Is testing a product your company uses different than a product shipped to customers ?
In some places it's been mine as QA and Release Manager, and in others it's been a group decision within Engineering. The advantage of being in small, web based product companies is the decisions are more egalitarian.
May
31
answered Is testing a product your company uses different than a product shipped to customers ?
May
27
revised What are good guidelines to determine when to automate a test?
adding in deterministic to the list
May
27
comment What are good guidelines to determine when to automate a test?
Good point, I'll add that to the list.
May
26
answered What are good guidelines to determine when to automate a test?
May
25
comment What proficiency should a software tester have in SQL?
You could look for someone who knows the basics as well as someone who is willing to learn, I was in your position where I only knew simple statements then learned how to do joins. Mostly its an educational aspect depending on the position.
May
25
answered How to avoid duplicated bug reports, described from different user perspective ?
May
24
awarded  Scholar
May
24
comment What do you do when you encounter overloaded terminology in your workspace?
Agreed, diplomacy is everything in QA.
May
24
comment What do you do when you encounter overloaded terminology in your workspace?
I'm going to be biased with this one since I am using, and working with, SharePoint now. It's become our repository for everything. And not just because I know Joe from other forums....
May
24
accepted What do you do when you encounter overloaded terminology in your workspace?
May
24
answered Does automating your manual tests give you good automated tests?
May
24
comment Approaches to Testing a Scientific Library
If the Unit Tests are failing the build should never have made it into Test in the first place, the Acceptance Test will tend to be more generic and often times be "Happy Path" since its only going to demonstrate that functionality has been achieved. glowcoder definitely links the two rightly though, as they are both Tests and may cover the same things but not in the same way.