Some time ago last year, we tried cypress and are definitely fond of it : the ability to define API responses ends up avoiding to mock 100 test data which are shared between each tests. Cypress allows us to make each tests independent one from another, covering more scenarii with less hassle.
The task here is to migrate all selenium tests into cypress. It's quite huge, so feel free to split it by page, and free to split as well the sets of flow into individual pages.
[ ] Find a dojo
[ ] i18n
[ ] My tickets
[ ] Book tickets flow
[ ] Dojo details
[ ] Login
Selenium tests have been commented out from the CI, while still being in the codebase for the time being.
While it's recommended to run them until we migrate them fully, do expect some failures in the meantime
Some time ago last year, we tried cypress and are definitely fond of it : the ability to define API responses ends up avoiding to mock 100 test data which are shared between each tests. Cypress allows us to make each tests independent one from another, covering more scenarii with less hassle. The task here is to migrate all selenium tests into cypress. It's quite huge, so feel free to split it by page, and free to split as well the sets of flow into individual pages.
Selenium tests have been commented out from the CI, while still being in the codebase for the time being. While it's recommended to run them until we migrate them fully, do expect some failures in the meantime