Add some functional CORS tests

If you've got selenium installed (and working), the whole thing can be
automated pretty well; run main.py, wait while some windows pop up (or
use xvfb-run to run things on a virtual display), then check out what
tests were run on which browsers and whether any of them failed. Exit
code is the number of failed tests.

Includes tests against:
- Account
- Containers, with various ACLs/CORS settings
- Objects
- /info
- SLOs
- DLOs
- Symlinks

Include a gate job that runs the tests in firefox.

Areas for future work:

- Install chromium and chromedriver in the gate; tests should
  automatically pick up on the fact that it's available
- Capture the web browser's console logs, too, so we can get
  more info when things go wrong

Change-Id: Ic1d3a062419f1133c6e2f00a598867d567358c9f

1 files changed, 25 insertions, 0 deletions

diff --git a/tools/playbooks/cors/post.yaml b/tools/playbooks/cors/post.yaml
new file mode 100644
index 000000000..b0e4ba438
--- /dev/null
+++ b/tools/playbooks/cors/post.yaml
@@ -0,0 +1,25 @@
+- hosts: all
+  become: true
+  tasks:
+    - name: Copy geckodriver log from worker nodes to executor node
+      synchronize:
+        src: '{{ ansible_env.HOME }}/geckodriver.log'
+        dest: '{{ zuul.executor.log_root }}'
+        mode: pull
+        copy_links: true
+        verify_host: true
+
+    - name: Copy CORS tests output from worker nodes to executor node
+      synchronize:
+        src: '{{ ansible_env.HOME }}/cors-test-results.txt'
+        dest: '{{ zuul.executor.log_root }}'
+        mode: pull
+        copy_links: true
+        verify_host: true
+
+    - zuul_return:
+        data:
+          zuul:
+            artifacts:
+              - name: CORS test results
+                url: cors-test-results.txt