feat: rosemary selenium in docker enviroment and driver option in rosemary selenium command #55
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains a complete solution that uses selenium-grid for running selenium tests in docker.
Selenium-grid generates a container net controlled by selenium-hub. Selenium-hub container redirects all tests and manages tests queues so that all tests can be runned in nodes. There are 2 nodes, chrome and firefox. Each node has only the standalone version of its browser name.
When using rosemary selenium you can also specify the browser you want to test (chrome or firefox, being the last one the default). This option is also available in local enviroment.
2 selenium tests were fixed and adapted to current uvlhub version.
rosemary selenium now has an option called video. When video it's true, selenium tests are recorded and saved in /docker/tmp/videos. This option is only available for docker enviroment.