action #109899
Updated by szarate about 2 years ago
See Parent's description for more background, as far as this task goes, we want to know:
1. How do we hook selenium to openQA? How could that look like?
1. How can the testcases look like? for Selenium? where are they located (hint, not in data/)
1. How difficult is to write the test (1 to 10) + the driver?
1. Could it be that in the future, we can have some bigger tests written this way (see for instance?
1. What could be a birds eye view on how the architecture could look like?
1. What are the advantages?
1. Conclusions after the experiment
## Acceptance Criteria
1. Very basic test for Element (matrix client), Rancher Desktop, VSCodium or Discord
1. Findings are documented in this ticket, with all pull requests related to it
1. Above questions answered (during the Sprint review)
### Considerations
This task doesn't necessarily need to be fully done, in such case, we'll be looking still at the findings during the sprint review. If you see a risk, raise it during a daily or talk about on slack!
## Suggestions
Take a look at the Electron's documentation on testing: https://www.electronjs.org/docs/latest/tutorial/automated-testing#with-selenium (make sure you only look at selenium for now) while we don't necessarily need to use Javascript, we might have to do some research before writing code.