Override the default of /usr/bin with the environment variable of the
same name, if set.
Related: OS#4564
Change-Id: I245ae368a97558006fc9f85d4fcb4e4cd52fb19a
The compare-results.sh is annoyingly slow. Since our ttcn3 tests containers
support Python 2, re-implement in Python for much quicker evaluation.
Change-Id: I0747c9d66ffc7e4121497a2416fca78d7b56c8e6
Sometimes it's useful to test with a non-installed locally-compiled
version of Eclipse TITAN. This adds an example on how to do that.
Change-Id: I6a8c26becff868a3d2fcd3a01e2c03adfc748e0a
The license of the build or execution scripts doesn't affect the license
of the actual program, and we want to explicitly state that these scripts may
be used in any kind of context.
Change-Id: I553925cd88b05903aab52ae1afb093aa9ab9d035
The Eclipse titan.core may not only be installed to hard-coded
'/usr/lib/titan' patch, but to any other location too. In the
later case, one would have to make sure that the custom path
is in $LD_LIBRARY_PATH. So we shall not override it.
Change-Id: I1ec28e8c3081d5de1bea90a7451791ac8cbbd27c
The set -e will not interfere with the next command,
as it's executed and not included.
The exit code of the last command is returned with and without -e.
Change-Id: I820d59b29b4ba4a1d094c5c2a2af367e6ef4e5b6
'make clean' as generated by ttcn3_makefilegen removes all *.log files, which
of course cleans out expected-results.log, which should not happen. Since this
is a junit XML file, rename the suffix to .xml.
Change-Id: Ic334f6b758eef865e3a497aa430691a3ae696d25
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
The name of the parameters is a little misleading, since the second
parameter could just be a testname.
Change-Id: Ibe207a83c477c918a865a8a34cad7ca5d45c7eac
Oliver Smith
Neels Hofmeyr
Harald Welte
Daniel Willmann
Pau Espin