with agile testing i'm thinking about work to improve quality, and work to reveal quality (or lack thereof).
first an interesting idea for learning:
testing dojos
http://www.methodsandtools.com/archive/archive.php?id=114
http://www.testingdojo.org/Public+Dojos
a few people:
Gojko Adzik
- http://gojko.net/
- http://specificationbyexample.com/
- (books - esp. the above, twitter)
- focus on living documentation/ spec by example
- ex
Michael Bolton
- http://www.developsense.com
- http://www.developsense.com/blog/
- (blog, twitter, book)
- focus a bit on sentient testing
- don't like scripts so much... (unless automated)
- don't like testing certification so much
- "infoslides", pdf
- ex:
- http://www.developsense.com/resources.html#exploratory
- http://www.developsense.com/blog/2011/12/what-exploratory-testing-is-not-part-2-after-everything-else-testing/
- http://www.developsense.com/blog/2011/12/what-exploratory-testing-is-not-part-4-quick-tests/
- http://www.developsense.com/blog/2011/12/what-exploratory-testing-is-not-part-5-undocumented-testing/
Lisa Crispin
- http://lisacrispin.com
- (blog, twitter, book: agile testing)
- focus a bit on whole team aspect
- ex: http://lisacrispin.com/wordpress/2011/11/08/using-the-agile-testing-quadrants/
No comments:
Post a Comment