-
Notifications
You must be signed in to change notification settings - Fork 0
Running EZID tests in docker and GitHub action #18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Add test-runner-ezid-status to docker-compose file Save apitest account passowrd as github repo secret Setup environment variables for the secret
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested out both doing docker compose manually with setting the environment variable and using the run_ezid_tests.sh script. Both worked well for me.
At first I had forgotten if this was to run tests against local code for checking functionality or to check what was on the servers, but then I remembered. It ran well for me and I tried both dev and stage.
This isn't running against pull requests to EZID, also, is it?
Feel free to merge and it seems useful!
|
@sfisher Thank you Scott for reviewing and testing. Jing |
@sfisher Hi Scott,
Here are the major changes:
Added files:
.env: used to trigger GitHub actionezid-tests.yml: define GitHub workflowdocker-compose.yml: define theseleniarm/standalone-chromiumand EZID test containersDockerfile: to build a Docker image for EZID testsezid_ui_tests_docker.py: Docker version EZID UI tests derived fromezid_ui_tests.py. The major change was to use a remote Selenium server instead of a local installed one.run_ezid_tests.sh: a wrapper to combine functional tests (defined inverify_ezid_status.py) and UI tests (defined in `ezid_ui_tests_docker.py" in one scriptPlease take a look and let me know if you have questions.
Thank you
Jing