2,882 reputation
424
bio website linkedin.com/in/ethelevans
location Seattle, WA
age 31
visits member for 2 years, 11 months
seen Mar 7 at 21:08

SDET with 5 years of experience in software testing & BS in Computer Science. I'm also not very good at filling out "About Me" sections. I'm not as much of an expert as I'd like to be, so am trying to soak up knowledge as fast as I can while balancing work and "real life".


May
11
comment What is meant by “Automated tests don't find new bugs”?
The statement, "If you run a test with the same input, it should have the same output" breaks down for other types of testing besides fuzzing - stability testing often is "run until it breaks", testing features with inherent randomness can't have this feature (e.g., I'm testing a random sampling feature right now), etc. Someone distinguished between "testing" and "checking" once, but I can't find the articles - but I thought that was a useful distinction.
May
11
awarded  Commentator
May
11
comment What is meant by “Automated tests don't find new bugs”?
Thanks, Bruce, I thought that was the distinction you were aiming at. I appreciate your patience in clarifying these terms for me. I think the concepts got conflated because testers so naturally added in semi-random data with their random testing (since it's a fairly small set of changes to the fuzzing tool to have it run semi-random data as well).
May
11
comment What kind of testing should a developer do before passing a build to the QA team?
The one change I would make is to make step 4 be step 1. Do the reviews on the plans first. This allows the developer to build in testability features and helps the tester avoid writing useless tests or missing key areas for testing. A review after coding might also be good, but I think a pre-review is much more important. @glowcoder, with the modification I mentioned, we do this on our (small, Agile) team, and I saw this at Microsoft as well (large, branch-and-merge). Both hire management with experience as senior developers, which seems key.
May
10
answered Testing interactions with external systems
May
10
comment What is meant by “Automated tests don't find new bugs”?
Thanks, I wasn't getting the idea that the bug 'isn't a bug' if it's fixed so quickly that it doesn't really spend any time in the code. Do you have more information / good links to read on 'test data generators'? I'm trying to figure out if the people I've worked with have used the term 'fuzzing' loosely when they were doing what you are talking about at least some of the time, or if there is a greater distinction that I'm just not familiar with. When I've seen people 'fuzz' in the past, they did have x% of the tests be category A, y% category B, etc., where A & B are defined by a regex.
May
10
answered Are your UI automated tests dependent or ordered?
May
10
awarded  Student
May
10
asked What is meant by “Automated tests don't find new bugs”?
May
10
answered Has automated UI regression testing helped you in finding critical defects in system?
May
10
comment How can I report coverage on an n-dimensional test matrix?
I second Tangurena's comment. Drilldown reports are very handy for displaying this kind of information.
May
10
comment How can I report coverage on an n-dimensional test matrix?
This is what I was thinking! I've never used it either, but all pairs or something similar sounds promising.
May
10
comment Testing techniques repository?
Maybe something like a Design Pattern archive for developers, but with testing techniques? I could see that being useful. It seems analogous to this site dofactory.com/Default.aspx
May
10
comment Suggested books to start on software testing
It's getting a little outdated IMO, but for an absolute beginner I still don't know of anything better.
May
6
awarded  Teacher
May
6
comment How to organize test documentation?
+1 for team wiki. I love, love, love this solution. I've seen every one of these solutions, but like the wiki best (followed by source control).
May
6
comment How to organize test documentation?
I would disagree. For just one example, it's pretty rare that a person will want to read a test plan without also reading the functional spec, and that kind of cross-referencing needs to be easy to do.
May
6
answered How to deal with testers who do more than test
May
6
comment What's the difference between “testing” and “quality assurance”?
I think the answers to these questions really show the difference between the QA / test mindset and the developer mindset . . . devs would just shrug and say, "However you want to define them is fine." Testers, on the other hand, want to have the RIGHT answer!
May
6
answered What's the difference between “testing” and “quality assurance”?