robotframework / robotframework/SeleniumLibrary
Review GitHub Actions setup regarding webdrivers and system configuration
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
Because we check the robot logging at various levels for specific messages, if we rely on the selenium manager to setup the drivers and browser then the logs change. So as not to be constantly fighting the execution of the atests and the verification of the log messages we should settle on some system configuration.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the repository's GitHub Actions setup and the atests that verify Robot Framework logging. Determine how Selenium Manager, browser, and webdriver configuration changes the logged messages, then establish a stable system configuration whose atest log checks remain reliable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100