Aircloak
diff --git a/‎README.md
-45 b/‎README.md
-45
diff --git a/‎deploy.sh
-1 b/‎deploy.sh
-1
diff --git a/‎frontend/.babelrc
-3 b/‎frontend/.babelrc
-3
diff --git a/‎frontend/.gitignore
-3 b/‎frontend/.gitignore
-3
diff --git a/‎frontend/Makefile
-10 b/‎frontend/Makefile
-10
diff --git a/‎frontend/config.json
-6 b/‎frontend/config.json
-6
diff --git a/‎frontend/deploy.sh
-5 b/‎frontend/deploy.sh
-5
diff --git a/‎frontend/logs/.gitkeep b/‎frontend/logs/.gitkeep
diff --git a/‎frontend/package.json
-13 b/‎frontend/package.json
-13
diff --git a/‎frontend/reset_db.sh
-20 b/‎frontend/reset_db.sh
-20
diff --git a/‎frontend/run.sh
-14 b/‎frontend/run.sh
-14
diff --git a/‎frontend/start_dependencies.sh
-16 b/‎frontend/start_dependencies.sh
-16
diff --git a/‎frontend/support/data_source.js
-23 b/‎frontend/support/data_source.js
-23
diff --git a/‎frontend/support/group.js
-18 b/‎frontend/support/group.js
-18
diff --git a/‎frontend/support/random.js
-1 b/‎frontend/support/random.js
-1
diff --git a/‎frontend/support/session.js
-21 b/‎frontend/support/session.js
-21
diff --git a/‎frontend/support/user.js
-37 b/‎frontend/support/user.js
-37
diff --git a/‎frontend/test/group_test.js
-60 b/‎frontend/test/group_test.js
-60
diff --git a/‎frontend/test/login_test.js
-39 b/‎frontend/test/login_test.js
-39
diff --git a/‎frontend/test/profile_test.js
-26 b/‎frontend/test/profile_test.js
-26
@@ -25,48 +25,3 @@ If errors are encountered, a notification email is sent to the address specified
 
 __NOTE__: Because of the way queries are executed (polling is used to wait for a query to complete),
 timing information is accurate only within 1% of the test timeout value or 2 seconds, whichever is greater.
-
-### Frontend tests
-
-The tests driving the system through the frontend are contained in the `/frontend` directory. The deployed version can
-be found on `srv-76-131:/aircloak/tests/frontend`. They are run an hour after the backend tests, on a separate
-instance of cloak/air called `browser_test` that's deployed from master just before running the tests.
-
-#### DB cleaning
-
-The tests run a script (`/frontend/reset_db.sh`) that clears the database before each run. When developing you can login
-to `srv-76-131` and run the script from there to get the same result.
-
-#### Running locally
-
-You can run the tests locally with:
-
-```bash
-make test
-```
-
-This will install node dependencies and download and run a selenium docker image before running the tests.
-
-#### Running one file
-
-Assuming you installed dependencies (`make deps && make start_deps`) you can run a single file with:
-
-```bash
-node_modules/.bin/wdio wdio.conf.js --spec test/file_to_run.js
-```
-
-#### Debugging
-
-You can watch the browser while the tests run if you start a debug version of the selenium image in place of the regular
-one:
-
-```bash
-# Remove current selenium
-docker rm -f selenium
-
-# Download and run the debug version mapping the VNC port 5900
-docker run --name selenium -d -p 4444:4444 -p 5900:5900 selenium/standalone-chrome-debug
-```
-
-You will also need to install a VNC viewer. After that just point your viewer to localhost and provide `secret` when
-asked for a password.
@@ -5,7 +5,6 @@ cd "$(dirname "$0")"
 scp run.sh srv-76-131:/aircloak/tests/integration/
 
 ./backend/deploy.sh # backend files
-./frontend/deploy.sh # frontend files
 
 # Deploy common files
 scp -r common srv-76-131:/aircloak/tests/integration/