Commit 12d32752 authored by Georges Racinet's avatar Georges Racinet 🦑
Browse files

Started to document what I've understood

parent 684f8d528484
# Heptapod automated functional tests
## Installation
### Client-side install
- tox: `pip install --user tox`
- [ChromeDriver](https://sites.google.com/a/chromium.org/chromedriver/home):
+ Fedora 29: `dnf install chromedriver`
+ Debian 9: `apt install chromium-driver`
### Heptapod install
It's currently not possible to configure details about the heptapod install
(URL, passwords etc)
- Run a fresh Docker container named `heptapod`, and answering on
`http://localhost:81`. The tests will issue both `docker exec` commands
and HTTP requests.
- The Gitlab root password will be initialized by the test.
## Running the tests
Just do: `tox` from the `heptapod-tests` directory, as an user that can
issue Docker commands.
This will test the current state of your Heptapod container.
### Choosing the version to test
By default, the `Dockerfile` from `omnibus/heptapod_docker` is loaded with
the head of the `heptapod` branch from `https://mirrors.octobus.net/heptapod`.
To test your local heptapod clone:
- mount your local `heptapod` clone in the container (assuming below it's seen
as `/home/heptapod` from the container)
- execute the following in the container:
```
cd /var/opt/gitlab/embedded/service/gitlab-rails
hg pull /home/heptapod
hg rev -r WISHED_REVISION app lib
gitlab-ctl restart unicorn
```
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment