osmo-ttcn3-hacks/sysinfo
Neels Hofmeyr 3cf797d7a5 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
2018-04-06 01:07:15 +02:00
..
Test.cfg Add "SourceInfoFormat := Single;" to all test configs 2018-01-17 11:11:29 +00:00
Test.ttcn Merge duplicate SI3 in GSM_RR_Types and GSM_SystemInformation 2018-02-25 16:17:33 +01:00
expected-results.log add compare-results.sh, call from start-testsuite.sh 2018-04-06 01:07:15 +02:00
gen_links.sh ignore results of .ttcnpp files 2018-03-16 18:25:58 +01:00
regen_makefile.sh generalize shared code from regen_makefile.sh into shared helper script 2017-12-13 01:04:42 +01:00