Browse Source

A note about tests and docker

tags/3.17
parent
commit
c798128e66
Signed by: hristoast <me@hristos.triantafillou.us> GPG Key ID: 5FC7664AD47AA1C5
1 changed files with 2 additions and 7 deletions
  1. +2
    -7
      CONTRIBUTING.md

+ 2
- 7
CONTRIBUTING.md View File

@@ -118,18 +118,13 @@ If you just want to run a local version of the site, you should now be set.

## Testing

Tests depend on a working install of both the chrome and gecko webdrivers for selenium.
Their installation and setup is (for now) outside the scope of this document, but all
that's necessary is to have `chromedriver` and `geckodriver` binaries for your OS in
your `$PATH`.
Tests depend on a working install of both the chrome and gecko webdrivers for selenium, as well as a working local manual install of the application. Docker-based setups are not yet supported. Their installation and setup is (for now) outside the scope of this document, but all that's necessary is to have `chromedriver` and `geckodriver` binaries for your OS in your `$PATH`.

To run tests:

make test

After a short time, a chrome or chromium instance will pop up with a note about it being
controlled by software. After a bit more time it will close and then firefox will open
and do the same. This is normal and part of the test suite.
After a short time, a chrome or chromium instance will pop up with a note about it being controlled by software. After a bit more time it will close and then firefox will open and do the same. This is normal and part of the test suite.

### Source formatting/linting



Loading…
Cancel
Save