Automated end-to-end tests

As part of preparing the product for transition to a stable basic operating mode, we aim to improve overall test coverage and address existing gaps in testing. This will help increase the product’s maintainability, reliability, and long-term stability.

The initial focus will be on strengthening unit and service-level tests, as they provide fast, reliable feedback and are easier to maintain.

Once a solid foundation is established, we will consider selective automation of end-to-end (E2E) tests, prioritizing only the most critical user journeys. This approach helps avoid unnecessary maintenance overhead, as E2E tests tend to be more brittle and costly to maintain.

Start by reviewing the existing unit and service-level test coverage to identify the gaps described in the issue. Confirm which critical user journeys are candidates for later E2E automation, then define a focused test scope and completion criteria with the maintainers; the issue does not name specific files, tests, or journeys.

Written by the indexing model from the issue text.