Reputation
3,202
Next privilege 3,500 Rep.
Protect questions
Badges
1 7 35
Impact
~142k people reached

Feb
19
awarded  Notable Question
Feb
18
awarded  Nice Question
Jan
21
comment Deployment Testing - when to perform
Can the process of creating the RIP be automated?
Jan
21
comment Test team names
We ended up going with a fun acronym that includes "QA". It works for our company culture. We refer to ourselves as testers or SDETs (we're geographically close to Microsoft, so this makes sense). So we're kind of straddling the test / QA argument. Since two of the top 3 answers are defending testing, I'm picking the top test-defending answer. But, I think Joe's answer is a great response, too.
Jan
21
accepted Test team names
Jan
21
comment Test team names
I'd be less worried about internal reputation, and more concerned about external presentation - think hiring. Obviously the company knows what we do or can be educated to better understand it, but we want to send as many signals to potential new hires as we can that will help them understand if they might be a fit for our culture.
Jan
10
awarded  Nice Answer
Jan
9
asked Test team names
Dec
28
awarded  Nice Question
Dec
14
answered Reviewing unit tests before implementation
Dec
6
comment How can my team move away from record-and-playback when not everyone has scripting experience?
+1 for DSLs (Domain Specific Languages - like Cucumber's Gherkin) that allow people to write scripts in English or near-English with code-behind written by a developer.
Sep
20
comment Is my pay fair, just based on the fact I have little experience
Great answer. Career-building skills and experience are worth more early in your career than salary these days. At the same time, don't be afraid to move on if you can get a better offer - as long as you can learn in your new position also.
Sep
20
answered Is there a name for these kinds of tests?
Aug
15
awarded  Nice Question
Jul
23
awarded  Popular Question
Jul
12
revised Fundamental classification- discrepancies
Added note at the end on normalcy of frustration w/ lack of consistent definitions
Jul
12
answered Fundamental classification- discrepancies
Jul
12
comment Are Exhaustive “Brute Force” UI Tests Worth It?
Another point on UI testing for the wrong reasons: Resorting to rigorous UI testing can be a sign of untestable code, that isn't being tested at lower levels well enough. UI testing should be essentially just making sure the UI responds the way it should - and not functionality testing (with some exceptions, e.g., end to end tests). Unit tests, API tests, component tests, etc. should cover functionality. UI tests should be a small part of the overall testing effort in most cases.
Jul
12
comment Suitability of functional testing to problems with many interrelated inputs
Do you know where you read this? A link might help us understand the context of what this person meant by "functional testing".
Jul
2
comment Where should test fixture code live?
Changed the accepted answer to match what I actually did in the end . . apologies if this has led to any confusion