As we add more features to API View, manual testing becomes increasingly unreliable due to the growing number of cases to validate.

This applies to both the server (which has unit testing but lacks working E2E tests) and especially the UI.

I want to avoid investing significant time testing every scenario manually, or worse, breaking functionality because a scenario was overlooked.

Adding E2E testing has significant implications and concerns, including flaky tests, authentication challenges, and more.

I'd like to start by narrowing the scope to get E2E tests running locally first, with the eventual goal of running them in CI. For now, we can begin with local execution and make commitments to adding and running these tests consistently.

For example, this issue was reported this week is a clear example of regressions:

• [APIView UI] Comment box text is cleared after scrolling away briefly #12994