Technical Story: Setup E2E Tests

[MasterEvarior]

Description

To ensure code quality and (hopefully) prevent some bugs, there should be a comprehensiv E2E testing. For this we use Cypress.

The testing should be done in a workflow but should also be possible locally. It should be explained in a README.md, how a developer can execute the tests locally.

To facilitate easier and more maintainable tests down the line, the page object model should be used.

Acceptance Criteria

• Test can be executed locally
• Local test execution is documented
• A GH Actions workflow which checks the E2E tests on each commit should be present
• The workflow should only execute E2E tests if:
  • the linting is OK
  • the unit tests are OK

Dependencies

• Technical Story: Setup Linting (Frontend) #8
• Technical Story: Setup Linting (Backend) #6
• Technical Story: Setup Testing (Backend) #9
• Technical Story: Setup Testing (Frontend) #7
• Technical Story: Docker & Docker Compose #4

Additional Information

• https://github.com/puzzle/okr/blob/5adceef874d43e486d9ee3dcfffd01b8a3df26d1/frontend/package.json#L11
• https://github.com/puzzle/okr/tree/main/frontend/cypress/support/helper

[Miguel7373]

You should also check whether all the Cypress paths in eslint.config.js are correct.