Best practices are everywhere and they are very trendy. Everyone should have a list of best practices for their domain on their blog just for the google traffic. Here are my best practices for good testing:
- Do not interrupt busy testers more than once a day.
- Be willing and able to test anything even if it’s not finished and get meaningful results – if you can’t you need to focus on best practice #3.
- Learn a new testing skill every day.
- Understand and use multiple oracles to find bugs.
- Understand and isolate bugs before reporting them.
- Always understand the project context and how it affects the determination that something is a “bug” vs. being an unfinished feature.
- Solve your own problems as much as possible.
- Know and acknowledge your limitations – don’t pretend you can do security testing if all you know is a simple XSS attack that you learned on my blog.
- Advocate for bug fixes without turning the rest of the team against you.
- Tell managers who break best practice #1 to leave you the hell alone.
Now here are some ads.
Stumble it!
3 responses so far ↓
1 Lee Copeland // Sep 30, 2009 at 7:54 pm
Like all (alleged) best practices, I can think of a context in which each of these is a bad idea.
2 davidray // Sep 30, 2009 at 8:12 pm
That's so awesome. I love you true-to-the-faith context guys. I'm not being facetious – I really do.
I should have had something in the list about context trumping everything because I totally agree with you, but I didn't really intend anyone to take me seriously. I think everything on the list is a good tip under the right circumstances, but I was really just trying to poke fun at best practices by making ten of them up in less than two minutes.
3 Dave Whalen // Sep 30, 2009 at 11:04 pm
OK….maybe its just me but….
Is marketing the Context-Driven School as a "best practice" a violation of the Context-Driven School?
Leave a Comment