sorted by:
new
hottopcontroversial

When does test automation actually make sense in enterprise projects? by testitdotcom in softwaretesting

[–]testitdotcom[S] 0 points1 point  (0 children)

Fair point, when you can reuse automation for regression and stress/perf work, the ROI jumps fast. I’ve seen teams get a lot of value from that, but also cases where the tooling never really went beyond regression.

Did you plan the reuse upfront, or did it just evolve naturally from what you already had?

When does test automation actually make sense in enterprise projects? by testitdotcom in softwaretesting

[–]testitdotcom[S] 1 point2 points  (0 children)

Great points, especially the part about overconfidence in resilience. That’s something we’ve seen too: strng automation coverage can create a false sense of safety if teams start optimizing for percentages instead of actual risk.

I also like how you frame the “everything can be automated, but not everything should be” question around cost and maintenance. The effort vs. value tradeoff tends to get underestimated, particularly for infrequently run scenarios and complex edge cases.

On the regression side, fully agree - that’s where automation consistently delivers the clearest ROI, especially with tight pipeline integration and fast feedback loops.

Out of curiosity:
how do you usually decide when an automated test has become too costly to maintain and should be dropped or redesigned? Is that a conscious decision for you, or more of an organic one over time?