meta user
network profile
| bio | website | none |
|---|---|---|
| location | Calgary, AB, Canada | |
| age | 26 | |
| visits | member for | 2 years |
| seen | yesterday | |
| stats | profile views | 92 |
Moderator on sqa.stackexchange - we welcome your QA questions!
Are you a part-time or freelance graphic designer looking for a lightweight project? I'm looking for some sprites :) hit me up at racket.game@gmail.com
Formally known as 'glowcoder'.
|
May 16 |
comment |
How do you adapt agile testing techniques to a regulated industry? tl;dr The primary goal is to keep flaming/fighting to a minimum, and usefulness to a maximum. (Re: Signal to noise ratio) Objectivity lends itself to usefulness, but so can reasoned professional opinion! |
|
May 16 |
comment |
How do you adapt agile testing techniques to a regulated industry? In regards to the "subjective question quasher", I suspect the "How do you" is an automatic flag for subjectivity. In my experience, both on SO and this board, subjective questions answered based on experience and research and that meet the criteria in the FAQ welcome, and I feel unavoidable. I believe you cannot objectively answer a "how" question, because there are many ways to approach a problem, all equally valid (even if one is going to be the best) but that doesn't mean it's not allowed. There's a lot of subjective questions on SQA, and many are truly good questions. |
|
May 16 |
reviewed | Reject suggested edit on reporting cumulative test results |
|
May 14 |
comment |
What is meant by “Automated tests don't find new bugs”? I wouldn't say it's any sadder than any of the other misconceptions and mis-defined words and phrases in software development. For a set of people who make or break programs based on the tiniest change, it's surprising not only what we are willing to accept as incorrect, but often refuse to change even when corrected. |
|
May 14 |
comment |
What is meant by “Automated tests don't find new bugs”? In all honesty, every place I've worked has dropped the word regression and called what you would call "automated regression tests" simply "automated tests." Whether it be proper or not, I find it to be fairly common. |
|
May 13 |
comment |
How to deal with automation naysayers? Actually, I find that while people don't resist things that are easier, they do resist things that are different with no logical reason why other than they're afraid of it being different. |
|
May 13 |
reviewed | Approve suggested edit on Can every test be done by automation? |
|
May 13 |
answered | When writing manual test cases and scripts, how much detail is too much detail when documenting the steps? |
|
May 12 |
comment |
How do you approach a new project from a testing perspective? +1 It's incredible. Excel is simultaneously the worst tool and best tool for so many things. It's the worst because we really abuse the idea of a spreadsheet when there are tools out there that do things (like this, and many others) so much better. At the same time, it's the best tool because of how versatile it is and how effective we can be in it, despite the availability of 'better' tools. |
|
May 12 |
revised |
How do you approach a new project from a testing perspective? edited title |
|
May 12 |
reviewed | Approve suggested edit on How do I educate that it's not test automation framework? |
|
May 12 |
comment |
What are the forms of testing that testers commonly forget? I like this question, but it does fall into a category of 'avoided subjectivity', specifically "every answer is equally valid." I'm not sure how to rephrase the question such that it conforms, and I don't really want to vote to close as it has great potential to be a useful resource, but I do have a small issue with it's current form. |
|
May 12 |
comment |
php undercontrol replacement I have to agree with Bruce - we need to ask questions that don't necessarily limit the answers. If you're looking for a replacement, don't seed the question with a replacement. On an unrelated note, if Bruce is up (being from Australia) I should probably be in bed (being from the US...) :-O |
|
May 12 |
comment |
How do you prepare yourself for a testing position? It seems to be sound advice. I would like to clarify one point (and I think you know it, but I want to put it out here for others who might come across this thread.) I would like my appearance in an interview to be a reflection of my actual understanding of SQA. I'm not looking to game an interview. With that out of the way, I'm essentially turning the answers to this question into a draft with some check lists. I have a private project I'm working on, and am going to try to fit some of the advice here into it as a pilot for how to integrate it into the workplace. |
|
May 12 |
comment |
How do you prepare yourself for a testing position? He is just a regular developer who just wants to be making the best software he can. He's frustrated with his current environment and wants to make it better. He also seems to be talking about himself in the third person... which is a little awkward. He's gonna stop that. Probably... |
|
May 12 |
comment |
How do I educate that it's not test automation framework? +1 We certainly live in the era of buzzwords. How many of us are 'agile'? :-) |
|
May 12 |
asked | How do you prepare yourself for a testing position? |
|
May 11 |
revised |
1.5 Million lines of code. 0 tests. Where should we start? added 638 characters in body |
|
May 11 |
comment |
Testing interactions with external systems @Ethel I totally agree with making sure you eventually do E2E testing. After all, why would we use a service that never changed? That would mean it never got maintained, which would make it fairly unreliable. Raise your hand if you trust any developer/product to get the API right from the start (Looking at you, Java 1.0...) |
|
May 11 |
comment |
How do I convince management that we need a formal QA department? Unfortunately, we don't have access to the end users. 7200 users, 10 devs, and all communication to them is funneled through BAs, and then plant managers. They actually see many bugs: their solution is to report it, open a new project, and fix it. About 80% of the projects, which take about 50% of the time, are 'bugs'. Of course, a 'bug' is defined as 'when it doesn't do what we want.' So, if they requirements change, it's now a bug. You could say it's an uphill battle but surely I'm not the first person to go down this path before. :) |
