Results from the November 2012 Agile Testing Survey
|This survey was performed late October through mid November 2012 and there was 178 respondents. The survey was announced on the IT Surveys page, via twitter, a posting to the Disciplined Agile Delivery (DAD) discussion forum, and to attendees of the Agile Testing Days 2012 conference held in Potsdam (hence the large percentage of European responses). The primary goal of this survey was to find out what testing and quality strategies people have adopted on agile project teams.||
Some findings include:
Figure 1. Primary approach to acceptance testing.
Figure 2. Primary approach to developer testing.
Table 1. The most difficult challenges when adopting agile testing approaches.
|50%||Getting all testing done in the current iteration/sprint|
|37%||Adopting test-driven development (TDD) approaches|
|33%||Validating non-functional requirements|
|33%||Getting stakeholders/customers involved with testing|
|27%||Getting developers to test their own code|
|21%||User interface testing|
|16%||Learning to test throughout the agile lifecycle|
|13%||Adopting new agile testing tools|
|12%||Migrating existing testing and quality professionals to agile|
|8%||Using our existing testing tools to support agile development|
|8%||Remaining regulatory compliant|
You may use this data as you see fit, but may not sell it in whole or in part. You may publish summaries of the findings, but if you do so you must reference the survey accordingly (include the name and the URL to this page). Feel free to contact me with questions. Better yet, if you publish, please let me know so I can link to your work.
I'm sharing the results, and in particular the source data, of my surveys for several reasons:
This site owned by Ambysoft Inc.