Convert current Cypress `e2e` tests into `component` tests

[audiodude]

Currently we use what Cypress calls "e2e tests". Some of them actually require a working WP1 API backend (#689), even though they mock almost all other API calls and are mostly used for testing individual pages and components in the app.

We should look into converting these tests to what Cypress calls "component" tests

[arybhatt4533]

Hi @audiodude, I'm interested in helping with the conversion of e2e tests to component tests. I've set up the project locally and I'm currently exploring the existing Cypress tests. Any specific component you'd like me to start with as a trial?

[audiodude]

Well its interesting, because while we have "components" in the app, most of them represent full pages on the site. What I mean is that there isn't a lot of composition.

Maybe you could try ZimFile.vue?

[arybhatt4533]

@audiodude, thank you for the suggestion. I agree that starting with ZimFile.vue is a great way to test component isolation. Before diving into the implementation, I want to take a deep dive into the current structure of ZimFile.vue and how it interacts with the state. This will help me write a more robust component test rather than just a surface-level one. I’ll study the component's logic today and start working on the test trial once I have a clear understanding of its props and events. Will keep you posted