You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* merge in new auth token and some qa users
* update tests to use new users from config
* get current tests to pass with new qa users
* change dev to qa for thurloe url
* Save screenshot on test failure.
* udpate ctmpls
* put / in front of chrome path
* add pem ctmpl and fix template render stuff
* documentation for automation
* fix failure screenshot rendering
* Added clean-up to registration test and migrated it to the new test users.
Added passing of FireCloud-Id to Thurloe calls.
Fixed a bug with xpath of checking for an element with text.
* don't use ivy cache
* add dsde-toolbox pull to runtests script
* Added Thurloe service
* changing local orch api
* use different auth domain
* get default auth domain from vault
* add host name to test runner
* fixed loading of particpants.txt for DataTabSpec
* fail whole script if tests fail
* Improved reliability of test for creating a billing project.
Don't hide the test failure if there is a problem capturing a screenshot.
Avoid stalled headless chrome nodes (SeleniumHQ/docker-selenium#87).
* Re-throw error when logging.
Be a little more quiet about clean-up failures.
* Avoid instability with Google sign-in when the popup window automatically closes.
Copy file name to clipboardExpand all lines: README.md
+25Lines changed: 25 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -68,3 +68,28 @@ To compile and build the `broadinstitute/firecloud-ui` docker image, run
68
68
```
69
69
./script/build.sh compile -d build
70
70
```
71
+
72
+
## Selenium tests
73
+
74
+
Selenium tests are found in the `automation` directory. They should run against a firecloud-in-a-box (FiaB).
75
+
76
+
### Running with docker
77
+
78
+
First build the docker image
79
+
```
80
+
docker build -f Dockerfile-tests -t automation .
81
+
```
82
+
83
+
Then run the run-tests script with the newly created image. This script will render the `application.conf` and `firecloud-account.pem` from vault to be used by the test container. Note that if you are running outside of docker you will need to generate these files manually.
84
+
```
85
+
cd automation/docker
86
+
./run-tests.sh 4 qa <ip of FiaB>
87
+
```
88
+
89
+
### Running locally
90
+
Note that you will need to render `automation/docker/application.conf.ctmpl` and copy it to `automation/src/resources/`, as well as `automation/src/firecloud-account.pem.ctmpl`, which should be saved in `/etc`.
91
+
Your local `/etc/hosts` file will need to be configured so that Firecloud DNS names are pointing to the IP of your running FiaB. For more
92
+
```
93
+
sbt test -Djsse.enableSNIExtension=false -Dheadless=false
0 commit comments