Extend the previously created E2E tests for the Discovery page to run against a dockerized Platform API
Ideally, this would not need to change anything in the E2E tests themselves.
Patches:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Goal | dang | T362865 🔵 [Proposal] Experiment with Dependabot self-merging updates | ||
| Resolved | Andrew-WMDE | T364463 🔵[UI Dependabot experiment] Run tests for the Discovery page against a dockerized Platform API |
@Fring Looking back to when this ticket was created I was wondering if you have a memory of the "why" for this ticket? Specifically: was there a reason that the mock API became insufficient for testing the discovery feature?
I was also wondering if we considered running these tests against a kubernetes (rather than docker compose) orchestrated version of the api
basically I'm trying to figure out how this might fit into the bigger picture task of the parent (Experiment with Dependabot self-merging updates)
The why is mostly to cover for extending the tests to also cover the "meat" of the application: wiki management. If we say main and discovery page are all we ever want to cover, it's probably not needed.
Dockerized and In-Kubernetes are probably interchangeable here.