End-to-End Testing

[SverreNystad]

Implement comprehensive end-to-end (E2E) testing for the GalacticPathFinder application to ensure the integrated functionality of its features.

Proposed Solution

1. Select E2E Testing Framework: Choose a testing framework compatible with Django and React Typescript (e.g., Cypress, Selenium).
2. Define Test Scenarios: Identify critical user journeys for testing, including grid creation, setting start/end points, algorithm visualization, and heuristic customization.
3. Develop Test Scripts: Write E2E test scripts for each identified scenario.
4. Integrate with CI/CD: Ensure tests run automatically in the CI/CD pipeline.

Acceptance Criteria:

• [x] E2E testing framework selected and integrated into the project.
• [ ] Tests cover: grid creation,
• [ ] Tests cover: Start/end point settings
• [ ] Tests cover: Algorithm visualization
• [x] Tests cover: Heuristic choice
• [x] Tests cover: Algorithm choice
• [ ] Tests automatically run on pull requests and merges in the CI/CD pipeline.
• [x] Documentation updated with instructions for running and writing E2E tests.

[Jensern1]

Is this really necessary for a frontend-heavy application?

[SverreNystad]

Is this really necessary for a frontend-heavy application?

It is mostly for me to learn how to do E2E testing with cypress. It will also make us able to check that all major user stories will be functioning as expected. We have have a lot of integration tests on the backend and I feel like E2E testing would be the cherry on top for testing for this project :)