diff options
| author | Neels Hofmeyr <neels@hofmeyr.de> | 2018-04-05 16:56:38 +0200 |
|---|---|---|
| committer | Neels Hofmeyr <neels@hofmeyr.de> | 2018-04-06 01:07:15 +0200 |
| commit | 3cf797d7a59a9f5fc05bd22af32d21c23409e60d (patch) | |
| tree | d3dd5b5741ba5e576814b8879319e8d85a076f7b /bin/SCCP_Emulation.ttcn | |
| parent | def4ad4bcefbe065bc3446b20fb8b32769158425 (diff) | |
add compare-results.sh, call from start-testsuite.sh
Compare current test results to the expected results, and exit in error on
discrepancies.
Add compare-result.sh: (trivially) grep junit xml output to determine which
tests passed and which didn't, and compare against an expected-result.log,
another junit file from a previous run. Summarize and determine success.
Include an "xfail" feature: tests that are expected to fail are marked as
"xfail", unexpected failures as "FAIL".
In various subdirs, copy the current jenkins jobs' junit xml outputs as
expected-results.log, so that we will start getting useful output in both
jenkins runs and manual local runs.
In start-testsuite.sh, after running the tests, invoke the results comparison.
Due to the single-line parsing nature, the script so far does not distinguish
between error and failure. I doubt that we actually need to do that though.
Related: OS#3136
Change-Id: I87d62a8be73d73a5eeff61a842e7c27a0066079d
Diffstat (limited to 'bin/SCCP_Emulation.ttcn')
0 files changed, 0 insertions, 0 deletions