How often / when do your teams write automated tests?

EngineeringSoftware Development

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

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

Writing automated tests after big feature releases19%

Writing automated tests after several sprints17%

Writing automated tests at the end of the sprint6%

Writing automated tests at the end of each user story2%

Ensuring each commit has automated tests2%

Test Driven Development3%

Other (please comment)

338 PARTICIPANTS
3.5k viewscircle icon1 Comment
Sort by:
Field CTO in IT Services2 years 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

How are engineering teams using augmented analytics beyond dashboards? Many organizations are exploring augmented analytics to improve speed and quality of decisions. From an engineering perspective, where have you seen practical value so far — and where has it fallen short?

Are context engineering skills a high priority for your organization right now? How does that skill set compare to prompt engineering?

Have you had to help your developers learn to orchestrate AI agents during their coding workflows, or was this something they were able to do without much guidance?

Read More Comments

What benefits drove you to adopt agile practices? Select all that apply.

Enhanced ability to manage changing priorities30%

Accelerated software delivery53%

Increased software maintainability35%

Increased team productivity37%

Improved business & IT alignment35%

Improved project visibility27%

Improved team morale14%

Improved engineering discipline17%

Better management of distributed teams15%

Reduced project cost14%

Reduced project risk9%

Improved response to volatile market conditions7%

Other (please specify)1%

View Results

Is AGI already here—and are we just afraid to admit it? 

Yes—we've already passed the AGI line, but we keep redefining it.18%

Almost—these systems feel general, but something's still missing.45%

No—AGI must be autonomous, embodied, or conscious. We're not there.27%

It doesn’t matter—what we have now is disruptive enough.7%

The term AGI is a distraction. Focus on outcomes, not labels.4%

View Results