816 reputation
47
bio website
location Durham, NC
age 44
visits member for 3 years, 2 months
seen Jan 2 '13 at 16:53

May
4
awarded  Yearling
Jan
27
awarded  Notable Question
May
4
awarded  Yearling
Sep
28
awarded  Popular Question
May
4
awarded  Yearling
Mar
28
answered test cases for conversation unsubscription in a email
Mar
15
answered How do people express their ability to test software?
Jan
4
awarded  Nice Question
Sep
19
answered The role of a software tester in an agile environment?
Aug
15
answered How does a tester decide how much debugging/investigation to do before handing an issue over to development?
Aug
2
comment Which tools should I start with?
My question is why do you say "boring"? If it is the study guides and classes, then I get that... school can be boring. But if you find the idea of testing boring, then I wonder how satisfied you will really be in this career? Just because you are playing with tools doesn't remove the fact you still need to understand the concepts of testing & how to best apply them. Maybe I'm just reading too much into that. But something to think about before you possibly invest too much into a career you won't be happy in.
Aug
2
comment Which tools should I start with?
I agree with Joe whole-heartedly. Knowing a tool if you don't know when and how to best utilize it doesn't mean much. You could be the most skilled person in the world & create lovely automated tests, but if they provide no value to the project they aren't worth anything.
Jul
15
answered How can a conference attendee get the most out of a testing conference?
Jun
22
answered Can exploratory testing replace executing manual functional tests?
Jun
15
answered Should a test method test only one condition?
Jun
7
comment Recommend a Good QA Book
@John. I agree there are some very good classics out there, but unfortunately for my certification anything too old I'm not able to count towards my annual hours. So I lean towards newer books.
Jun
6
awarded  Student
Jun
6
asked Recommend a Good QA Book
Jun
2
comment Who is ultimately responsible for issues that are found after software is released?
+1 Code doesn't start with the coder & end at test. There are many cooks in the kitchen so to speak. Incorrectly understood customer needs, poor requirements, lack of equipment/tools, unidentified hardware, etc. can all contribute to defects. Use the post-mort to determine what slipped through & why so you can catch it next time around.
May
20
awarded  Commentator