search

IVCTool / IVCT_Framework

For IVCT Framework Developers. Core System for the IVCT (Integration, Verification and Certification Tool) for HLA Federates
Apache License 2.0
16 stars 4 forks source link

IVCT-VRF-Encoding tests: improve result reporting #130

Closed bergtwvd closed 6 years ago

bergtwvd commented 6 years ago

Attached the last part of the console output of the encoding tests against VR-Forces, now also with spatial data.

To determine what is wrong better result reporting is necessary.

IVCT-VRF-Encoding-1.txt

ducana commented 6 years ago

Added more details of names, handles and hex dump of buffer to help find the error.

bergtwvd commented 6 years ago

Agreed to wait on an IVCT version where the TC param values can be set via env variables. This makes it much more easier to run these tests. See https://github.com/MSG134/IVCT_Framework/issues/112.

ducana commented 6 years ago

There seems to be a misunderstanding here: no plan exists to change all the TCparam values to env variables. There was a proposal to look into having some values such as RTI host address or federation name as env variables. The other TCparam values typically vary for each badge (and maybe test case) for each SUT. To manage these values for a large number of badges, test cases and SUTs as env variables is not easy. Are there ideas how that would work?

ducana commented 6 years ago

Added current position in byte buffer where the error is detected. The position uses the Java/C++ standard where the buffer starts at position 0 (zero). Changed buffer analysis code to throw exceptions rather than use return values, since the return values were not checked in every case. Java compiler warns about not catching exceptions.