Analyzing test run results
Testground outputs structure
Testground test plans emit
outputs that you can collect and analyse after the test run concludes.The outputs structure is as follows:
1
/
2
|___ <group id> (coming from the composition)
3
| |____ <instance id or index>
4
| |__ run.out
5
| |__ run.err
6
| |__ ...
7
| |__ dht_events.json
8
| |__ heap.out
9
| |__ cpuprofile01.out
10
| |__ cpuprofile02.out
11
| |__ cpuprofile03.out
12
| |____ <instance id or index>
13
| |____ <instance id or index>
14
|___ <group id> (coming from the composition)
15
| |____ <instance id or index>
16
| |____ <instance id or index>
Copied!
How to collect Testground outputs
The logic for
outputs collection is runner-dependent, e.g.- the
cluster:k8srunner will download from AWS EFS. - the
local:dockerrunner will fetch the outputs from the$TESTGROUND_HOMEdirectory.
1
$ testground collect --runner=local:docker <run-id>
2
​
3
$ tar -xzvf <run-id>.tgz
Copied!
Testground also supports automatic outputs collection after a testplan run completes, with the
--collect flag, which instructs the Testground client to download the outputs in the current working directory after the run concludes.1
$ testground run single \
2
--plan=network \
3
--testcase=ping-pong \
4
--builder=docker:go \
5
--runner=local:docker \
6
--instances=2 \
7
--collect
8
​
9
...
10
​
11
>>> Result:
12
​
13
INFO finished run with ID: 975b9bc15b3b
14
​
15
>>> Result:
16
​
17
INFO created file: 975b9bc15b3b.tgz
Copied!
Processing the Testground outputs
At the moment Testground doesn't provide any tools for post-processing of outputs. You are free to submit ideas and pull requests and contribute to this feature.
One way to review all messages sent to
stdout by test plan instances, is with the following command:1
$ cd <run-id>
2
​
3
$ find . | grep run.out | xargs awk '{print FILENAME, " >>> ", $0 }'
Copied!
Last modified 2yr ago