Neels Hofmeyr | c0827c4 | 2017-04-23 15:04:19 +0200 | [diff] [blame] | 1 | [[trials]] |
| 2 | == Trial: Binaries to be Tested |
| 3 | |
| 4 | A trial is a set of pre-built binaries to be tested. They are typically built |
| 5 | by jenkins using the build scripts found in osmo-gsm-tester's source in the |
Neels Hofmeyr | b52df17 | 2017-05-14 20:09:35 +0200 | [diff] [blame] | 6 | 'contrib/' dir, see <<install_add_build_slave>>. |
Neels Hofmeyr | c0827c4 | 2017-04-23 15:04:19 +0200 | [diff] [blame] | 7 | |
| 8 | A trial comes in the form of a directory containing a number of '*.tgz' tar |
| 9 | archives as well as a 'checksums.md5' file to verify the tar archives' |
| 10 | integrity. |
| 11 | |
| 12 | When the osmo-gsm-tester is invoked to run on such a trial directory, it will |
| 13 | create a sub directory named 'inst' and unpack the tar archives into it. |
| 14 | |
| 15 | For each test run on this trial, a new subdirectory in the trial dir is |
| 16 | created, named in the form of 'run.<timestamp>'. A symbolic link 'last-run' |
Neels Hofmeyr | b52df17 | 2017-05-14 20:09:35 +0200 | [diff] [blame] | 17 | will point at the most recently created run dir. This run dir will accumulate: |
| 18 | |
| 19 | * the rendered configuration files used to run the binaries |
| 20 | * stdout and stderr outputs of the binaries |
| 21 | * a test log |
| 22 | * *TODO*: jenkins parsable XML reports |
| 23 | |