TEAM Engine (Test, Evaluation, And Measurement Engine) is an engine for testing web services and other resources written in JAVA. It executes test scripts written in Compliance Test Language (CTL), TestNG and other languages. It is lightweight and easy to run as a command line or to setup as a service. It can be used to test any type of service or encoding. It is also the official tool used by the Open Geospatial Consortium (OGC) for compliance testing.
Apache License 2.0
45
stars
41
forks
source link
Missing log link even though test is executed #585
Sometimes tests are executed and the logs are generated properly, but a link is missing in the parent log.
To Reproduce
It's unfortunately not easy to reproduce this locally as this only happens in one case of our scripts, namely the GDI-DE INSPIRE metadata tests. The easiest way to reproduce this is probably by using the GDI-DE testsuite, where the latest TEAM engine release is integrated. Run the 'GDI-DE Konventionen für INSPIRE-konforme Metadaten (v2.0)' tests against an ISO metadata dataset (should be a 'dataset' or 'series' metadata document, else the tests in question are not run). This behaviour happens whether the test passes or fails.
Since the scripts depend on custom java classes it is not easy to provide a full example here, however, here are the corresponding CTL scripts:
Describe the bug
Sometimes tests are executed and the logs are generated properly, but a link is missing in the parent log.
To Reproduce
It's unfortunately not easy to reproduce this locally as this only happens in one case of our scripts, namely the GDI-DE INSPIRE metadata tests. The easiest way to reproduce this is probably by using the GDI-DE testsuite, where the latest TEAM engine release is integrated. Run the 'GDI-DE Konventionen für INSPIRE-konforme Metadaten (v2.0)' tests against an ISO metadata dataset (should be a 'dataset' or 'series' metadata document, else the tests in question are not run). This behaviour happens whether the test passes or fails.
Since the scripts depend on custom java classes it is not easy to provide a full example here, however, here are the corresponding CTL scripts:
scripts.zip
The missing link concerns the test called in
inspire_only.ctl
in line257
, defined inGDI-DE.ctl
from line2728
.Expected behavior
See the attached logs. Therein you find
d320e65_1/d180e511_1/log.xml
, however, it is not linked fromd320e65_1/log.xml
.logs.zip