Port Selenium tests to Cypress

Nobody has claimed this yet.

Use the Selenium-to-Cypress breakdown in this issue as the work map, starting with the linked child issues #9337–#9347 and the existing CI test setup. Review which Selenium tests are skipped or failing, then compare their coverage with the current Cypress tests. Done means the listed end-to-end coverage has been ported so it runs under Cypress instead of Selenium.

Written by the indexing model from the issue text.

Currently, we do e2e testing in both selenium and cypress, two different testing frameworks. This slows down our workflows and requires more effort to maintain. Most of our selenium tests are also flagged to be skipped on CI mostly due to the lack of necessary components. The codebase has changed significantly while all of these tests were being skipped, so it is likely that a majority of them need major refactor if they are to work at all with the current or future codebase.

Furthermore, the tests that do work in CI fail most of the time. Workflows often need to be re-run 3-4 times before they pass selenium. This makes ongoing development challenging and slows productivity.

Hence, we will be gradually porting over the selenium tests to cypress so we can run all of our e2e tests under the single framework, saving time and energy.

Here is the breakup of our current selenium tests that need to be rewritten in Cypress, along with their complexity (represented with ✦'s), and the number of tests that are currently being run in CI:

#9337
- Relies on java dependency and config files
#9338
- Currently fails the most often (on merge_threads)
#9339
#9340
#9341
- Out of sync with latest sample queue data
#9342
#9343
#9344
#9345
#9346
#9347

Assessment

Research direction

Description

Contributor guide

First steps

More from Submitty/Submitty

Similar issues