How often / when do your teams write automated tests?

No automated tests, and no intention to ever write them4%

No automated tests, but have an intention to write them in the future37%

Writing automated tests after big feature releases23%

Writing automated tests after several sprints18%

Writing automated tests at the end of the sprint4%

Writing automated tests at the end of each user story3%

Ensuring each commit has automated tests3%

Test Driven Development3%

Other (please comment)

340 PARTICIPANTS
3.5k viewscircle icon1 Comment
Sort by:
Field CTO in IT Servicesa year ago

Really suprised that TDD is, amongst this audience, so little used. The idea of taking a user story, experssing the requirements in gherkin type language, then using that spec to create tests in a red/green/refactor approach has stood my developers (and the supporting QA engineers) move faster, deliver code that meets the spec, and given us assurance on system and regression testing long after the original code and test code were written. I dont belive that you need automated tests for everything but you do need it for the majority of things.

Content you might like

Very inclined: I believe in constantly pushing for innovation and improvement, even if the current systems are effective46%

Moderately inclined: I'm open to innovation and change, but only if it clearly enhances or adds value to the existing systems48%

Not inclined: If the current systems are working effectively, I prefer to maintain stability and avoid unnecessary changes5%

View Results

Completely confident 18%

Moderately confident57%

Slightly confident25%

Not at all confident

View Results