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 future32%

Writing automated tests after big feature releases23%

Writing automated tests after several sprints23%

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)

341 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

Proven outcomes – Documented success stories and measurable KPIs39%

Implementation confidence – Detailed plan, risk mitigation, and resource readiness45%

Total cost – Clear TCO, price protections, and exit terms38%

Innovation & future readiness – Ability to scale, adapt, and support emerging needs16%

Vendor relationship strength – Cultural fit, governance model, and executive commitment13%

View Results

Strongly agree12%

Somewhat agree58%

Neither agree nor disagree17%

Somewhat disagree8%

Strongly disagree2%

View Results