IVCT_Framework
IVCT_Framework copied to clipboard
For IVCT Framework Developers. Core System for the IVCT (Integration, Verification and Certification Tool) for HLA Federates
The current IVCT version is build with JDK 8, which is no longer supported by Oracle with public updates. The latest JDK version is 11, which is supported by Oracle...
Add support for kubernetes deployments by providing helm charts and documentation.
Define how to export badges from the badge database and how to integrate them into the IVCT runtime configuration.
The certified conformance statement shall be digitally signed. The solution shall be in-line with the HLA PDG COM66 "Trusted Federation" Concept
Travis.org has changed policies and offers only limited credits to build. GitHub Actions is free and offers better configurability of build actions. Suggestion: migrate travis scripts into gitHub actions
Currently, the IVCT requires an operator to peform manual operations to start testing a SuT: - Select a SuT + Conformance Statement - Configure TcParams for the tests to perform....
IVCT should provide an implementation for the HLA 4.0 authorization feature. Linked with #245
Test suite developers need to able to maintain the definition files for their test suites independend from the framework. Consequently the framework need to be enabled to import such definition...
The Test Suites and Badges under `RuntimeConfig` have a version number or date in the file name. This should not be the case.
The current IVCTool does not support multiple user. This effects the GUI/UI, the Command Messages on the JMS bus, the test case engine, and the log-file generation.