Requesting e2e tests

[kenoir]

What?

We should have some end-to-end tests around item requesting. We'd like to do some discovery work around mocking items-api interactions in order to gauge the difficulty of creating these tests.

Why?

We are missing these at present and could miss breaking functionality associated with requesting when we deploy wellcomecollection.org

Background

We've had a framework for these tests in the past but recently removed it as they weren't exercising the expected functionality: https://github.com/wellcomecollection/wellcomecollection.org/pull/10578

We're looking at an approach where we mock items-api interactions in playwright via various mechanisms:

• https://mswjs.io/docs/getting-started
• https://playwright.dev/docs/mock
• https://playwright.dev/docs/network

Meeting document, discussing options.

We think mocking the items-api and testing up to viewing request state is a good compromise given the difficulty of other approaches.

Done when

• [ ] We demonstrate that we can either successfully mock items api requests, or not
• [ ] We have implemented a happy-path e2e test for logging in and viewing item results that are (a) requestable, (b) requested by me.

[LFBaily]

Moving a few of these which I think are on the wrong board.