Specification and Writing of E2E-Tests

AkrosAG / Akros-Marketplace

Apache License 2.0

4 stars 5 forks source link

Specification and Writing of E2E-Tests #117

Closed stefanleminh closed 1 year ago

stefanleminh commented 2 years ago

We currently have integrated Cypress into our frontend as well as a Github Action to run tests but no tests outside of one that tests whether the UI is reachable. As we now have the basic functionality down, we should start thinking about E2E tests.

We need to specify what tests are to be written
The tests should be specified by at least the PO but of course can be supported by the rest of the team
The tests that can already be executed on the current functionality should be written

int0x81 commented 2 years ago

As discussed with @TimmyAeberli I will take care of this US. The goal with be to

Specify 2-3 E2E tests that represent actual User journeys
The test will be written with the Playwright framework. (The actual language is to be determined by the team)
If possible, the tests will run in GitHub Actions
After the points above have been achieved the results will be shared with the team

akrguda commented 1 year ago

As we discussed it in the meeting of the 13th november 2022 we do not work on this ticket. This ticket were in progress from the developer called Finn and he left the project already for customer works. We decided, that we do not on this ticket anymore.