blob: bc9fe0502617b984cd519703be40e0b5255507e7 [file] [log] [blame]
Neels Hofmeyrc0827c42017-04-23 15:04:19 +02001[[trials]]
2== Trial: Binaries to be Tested
3
4A trial is a set of pre-built binaries to be tested. They are typically built
5by jenkins using the build scripts found in osmo-gsm-tester's source in the
Pau Espin Pedrolf5c83da2017-11-02 15:48:10 +01006'contrib/' dir, see <<install_add_jenkins_slave>>.
Neels Hofmeyrc0827c42017-04-23 15:04:19 +02007
8A trial comes in the form of a directory containing a number of '*.tgz' tar
9archives as well as a 'checksums.md5' file to verify the tar archives'
10integrity.
11
12When the osmo-gsm-tester is invoked to run on such a trial directory, it will
13create a sub directory named 'inst' and unpack the tar archives into it.
14
15For each test run on this trial, a new subdirectory in the trial dir is
16created, named in the form of 'run.<timestamp>'. A symbolic link 'last-run'
Neels Hofmeyrb52df172017-05-14 20:09:35 +020017will 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
Pau Espin Pedrol0b512ba2017-11-02 17:16:21 +010021* pcap files for processes doing relevant network communication
Neels Hofmeyrb52df172017-05-14 20:09:35 +020022* a test log
Pau Espin Pedrol0b512ba2017-11-02 17:16:21 +010023* jenkins parsable XML (Junit) reports
24
25The script in 'contrib/jenkins-run.sh' takes care of related tasks such as
26
27* creating the dir structure,
28* generating md5 sums for the various tar.gz containing software builds to be tested,
29* cleaning up after the build,
30* saving extra logs such as journalctl output from ofonod,
31* generating a final .tar.gz file with all the logs and reports.