|
2 | 2 |
|
3 | 3 | ## Running tests |
4 | 4 |
|
5 | | -To run the entire test set, run: |
| 5 | +To run the entire test set, first set the following environment variables: |
| 6 | + |
| 7 | + - `DOCKERNAMESPACE` to your docker hub account |
| 8 | + - `VERBOSE` to `1` (default is empty) |
| 9 | + - `LONG` to `1` (default is empty, which skips lots of tests) |
| 10 | + - `ARANGODB` to the name of a community image you want to test, |
| 11 | + default is `arangodb/arangodb:latest` |
| 12 | + - `ENTERPRISEIMAGE` to the name of an enterprise image, you want to |
| 13 | + test, if not set, some tests are skipped |
| 14 | + - `ARANGO_LICENSE_KEY` to the enterpise license key |
| 15 | + - `KUBECONFIG` to the path to some k8s configuration with |
| 16 | + credentials, this indicates which cluster to use |
6 | 17 |
|
7 | 18 | ```bash |
8 | | -export DOCKERNAMESPACE=<your docker hub account> |
9 | 19 | make clean |
10 | 20 | make build |
11 | 21 | make run-tests |
12 | 22 | ``` |
13 | 23 |
|
| 24 | +To run only a single test, set `TESTOPTIONS` to something like |
| 25 | +`-test.run=TestRocksDBEncryptionSingle` where |
| 26 | +`TestRocksDBEncryptionSingle` is the name of the test. |
| 27 | + |
14 | 28 | ## Preparing a release |
15 | 29 |
|
16 | 30 | To prepare for a release, do the following: |
17 | 31 |
|
18 | 32 | - Make sure all tests are OK. |
| 33 | +- To run a complete set of tests, do the following: |
| 34 | + |
| 35 | + Then do |
| 36 | + |
| 37 | +~~~ |
| 38 | +make run-tests |
| 39 | +~~~ |
| 40 | + |
19 | 41 | - Update the CHANGELOG manually, since the automatic CHANGELOG |
20 | 42 | generation is switched off (did not work in many cases). |
21 | 43 |
|
|
0 commit comments