Menu

Your Tests Find Bugs. Why Is Shipping Still Slow?
📰

Your Tests Find Bugs. Why Is Shipping Still Slow?

DEV Community: cicd·Markus Gasser·6 days ago
#MozzzcLW
#devtocicd#devto#dev#test#tests
Reading 0:00
15s threshold

A CI build goes red at 4:47 p.m.

The failing step is click Save . The screenshot shows a modal. The error message says the element wasn't clickable.

Was the button covered by a loading spinner? Did the API reject the request? Did the browser render something differently? Nobody knows yet.

The test took 40 seconds to run. Figuring out what happened might take the rest of the afternoon.

This is the part of test automation that gets surprisingly little attention. We spend weeks comparing frameworks and building test coverage, then give engineers almost nothing useful when a test fails.

I think that's backwards. The point isn't to have more automated tests. It's to make it easier to ship changes without guessing.

A green checkmark isn't the product

The conversation usually starts with a framework choice.

Should the team use Playwright or Puppeteer? Both can drive a browser. Both can click a button and check the result.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.