Summary: | UI tests: Selenium 4 support or setup Cypress to make them rewritable with it | ||
---|---|---|---|
Product: | Koha | Reporter: | Victor Grousset/tuxayo <victor> |
Component: | Test Suite | Assignee: | Victor Grousset/tuxayo <victor> |
Status: | ASSIGNED --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | jonathan.druart |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Bug Depends on: | 27055 | ||
Bug Blocks: |
Description
Victor Grousset/tuxayo
2021-10-20 13:45:13 UTC
Is this one still valid? Unfortunately yes and no. Yes because Firefox is stuck at some old version (2 or 3 years old) because only Selenium 4 supports recent ones. No because Selenium tests are less reliable so higher maintenance. So the work (kinda unpredictable like from Selenium 2 to 3) to change our Selenium lib would not be worth for just prolonging their use. The alternative is setting up Cypress to be able to replace Selenium. As opposed to today. Jonathan told me a few months what are the limitations: No DB access to inject and delete/rollback data. That's why current Cypress usage mocks all network queries. Path forward would be to read koha-conf and use cypress-mysql (see cypress-studio in Jonathan's GitLab repo) Then the issue is data generation (no TestBuilder!) and cleaning. «IMO there shouldn't be time spent on a migration to Selenium (at least for now)» That doesn't look a small task to find a trick to use TestBuilder or recode it plus the rest so we are kinda stuck at the crossroads between the two ways. > Yes because Firefox is stuck at some old version
In case someone needs the info, it's Firefox 92, from September 2021.
|