After one year of trying to improve and fix our E2E tests, we removed them and started from a clean slate. In this article we explain the whys and how we came to this extreme decision.

Hasura's platform is a resource for developers, offering insights into GraphQL APIs, serverless architecture, and modern application development. Through articles, tutorials, and documentation, Hasura offers insights into building scalable and real-time applications with GraphQL. Readers can learn about data modeling, schema stitching, and authentication strategies to create robust APIs and streamline frontend-backend communication.

Hasura

Stefano Magni deleted 95% of our E2E tests of Hasura Console, main Hasura's front-end application. The main problems were: they were slow, and they were flaky, he says. He says fixing/refactoring them was hard because they were long, terse, and had many abstractions.

Why we deleted 95% of our E2E tests

The server team used the E2E tests also to test the server

<p>I can mostly agree with the approach and outcomes. But the hardest part of any of this is going to be spreading the responsibility and getting developers to apply the same level of craftsmanship and care to the additional testing they’ll need to do.</p>


<p>Moving most of the interaction tests to Storybook level was the key to solve the issue IMO. You can also automatically visually test components in Storybook which eliminates the need of writing a bunch of UI testing code like “check if the background is grey on disabled state”.</p>
