/explore
|
You are here 
|
lisacrispin.blogspot.com | ||
| | | | |
team-agile.com
|
|
| | | | | Early on when trying to apply Agile methods to software development I found a lot of the challenges were in the area of software testing. Not just because a lot more automated testing was being done, but because requirements would shift and change rapidly. Many levels of rapid feedback needed to be in place to | |
| | | | |
lisacrispin.com
|
|
| | | | | The Twitterverse and other social media continue to host many discussions on topics such as "Do testers need to code?" As Pete Walen points out in his recent post, the "whole team" approach to delivering software, popularized with agile development, is often misunderstood as "everyone must write production code". The "Whole Team Approach" in practice [...] | |
| | | | |
agiletester.ca
|
|
| | | | | Our definition of "agile testing" Thanks everyone for your input on our original definition. We've changed it slightly based on new conversations and comments. Definition of agile testing: (by Lisa Crispin and Janet Gregory) Collaborative testing practices that occur continuously, from inception to delivery and beyond, supporting frequent delivery of value for our customers. Testing [...] | |
| | | | |
lisacrispin.blogspot.com
|
|
| | | Gojko Adzic has been doing some good writing on acceptance testing in agile development. See his article here: http://gojko.net/2008/09/17/ ... | ||
