- 24 Sep, 2018 3 commits
-
-
See !289
-
See #3444.
-
Mikaël Salson authored
The coverage must happen after tests (otherwise it's not very meaningful). Corrects f80461d5
-
- 14 Sep, 2018 1 commit
-
-
Mikaël Salson authored
Functinal testing should be performed before releasing or deploying. Fixes #3463
-
- 08 Aug, 2018 4 commits
-
-
Mathieu Giraud authored
See #3431.
-
Mathieu Giraud authored
See #2465.
-
Mathieu Giraud authored
See #3431.
-
Mathieu Giraud authored
We want to regularly run all our tests (and not to rely only on branch names).
-
- 20 Jul, 2018 2 commits
-
-
Ryan Herbert authored
-
Ryan Herbert authored
-
- 19 Jul, 2018 2 commits
-
-
Mikaël Salson authored
On demand for the development always when releasing.
-
Mikaël Salson authored
- Automatically test for releases - Manually test whenever we want
-
- 18 Jul, 2018 4 commits
-
-
Ryan Herbert authored
we now do this in the test launcher script
-
Ryan Herbert authored
-
Ryan Herbert authored
so we can use sed to edit it when executing functional tests in docker with gitlab-ci
-
Mathieu Giraud authored
See #3310.
-
- 17 Jul, 2018 2 commits
-
-
Ryan Herbert authored
-
Ryan Herbert authored
-
- 16 Jul, 2018 4 commits
-
-
Mikaël Salson authored
1. missing semi-colon 2. Needed `-T` to the `ln` command so that the link is not done inside the `next` directory
-
Mikaël Salson authored
-
Ryan Herbert authored
-
Mikaël Salson authored
-
- 13 Jul, 2018 4 commits
-
-
Ryan Herbert authored
-
Ryan Herbert authored
-
Mikaël Salson authored
-
Mikaël Salson authored
-
- 12 Jul, 2018 1 commit
-
-
Requires the environment variable COMPILERS to be defined Test unit+should+valgrind: unit+should+shouldvdj took almost 3h. Fix #3310 see vdj#450 for compiler installations on the slave.
-
- 10 Jul, 2018 1 commit
-
-
We use this for reorganizing where tests are launched
-
- 09 Jul, 2018 12 commits
-
-
Ryan Herbert authored
-
Ryan Herbert authored
Since in gitlab-ci we are launching the unit tests on the host, and the database initialisation needs to be launched on the docker container, we want to separate the two.
-
Ryan Herbert authored
-
Ryan Herbert authored
starting it in the background doesn't seem to be working. The detached mode must exist for this purpose
-
Ryan Herbert authored
due to our runner meccano having the i686 architecture, for which there is no official image for MySQL, and alternatives were causing issues.
-
Ryan Herbert authored
since we're running docker-compose in the background, we need to wait for our containers to have started before attempting to run our tests
-
Ryan Herbert authored
-
Ryan Herbert authored
-
Ryan Herbert authored
hopefully this will resolve the syntax error
-
Ryan Herbert authored
Since we are building the image in gitlab ci, we should not attempt to build it in docker-compose. We should also match the build tag to the docker-compose file.
-
Ryan Herbert authored
-
Ryan Herbert authored
fix issue with bash syntax for launching docker-compose in the background.
-