Browser end-to-end tests

A step of the Cloud application tree on Gradus, in the Frontend area: Second app, UI, browser tests.

A small browser suite over the first journey against the deployed frontend, in three engines, at phone and desktop widths and in both colour schemes.

Usually comes after: Deploy the frontend.

Prompt for your AI assistant

Add a browser test suite with Playwright or the tool the frontend decision record in docs/decisions names, run against a fresh deploy of the frontend and the service. Cover the first journey end to end in Chromium, WebKit and Firefox, at 1440, 375 and 320 pixels wide and in light and dark mode. Start each test with empty storage, so a first visit is tested as a stranger sees it, and make it fail on a console error, a failed request, a hydration warning or a page wider than the screen. Validate the HTML of each page once. Run the suite in CI after every deploy and keep it under five minutes.

This is https://gradus.kazet.blog/tree/cloud-application/step/browser-e2e-tests as plain HTML. In a browser the page also lets you mark the step forged and copy a message for your AI assistant.