This repository will be used for the development of the NETN Test Suite. Currently it contains ETR test cases for SuT in tasker and task receiver roles.
The current test suite design uses the ServiceLoader interface feature of the IVCT framework. This is only available in the latest snapshot releases and not yet included in the production release.
This test suite verify the NATO Education and Training Network (NETN) Federation Object Model (FOM). See also https://github.com/AMSP-04/NETN-FOM
The test suites modules are aligned to the badge structure.
Booster Config for PITIS-223 Test Environment:
- crc.PITIS-223@localhost:8688
local pRTI
- localhost:8989
These settings may be set via the SettingsDesignator setter of the test case object ("tc"), like
tc.setSettingsDesignator("crcAddress=localhost:8989");
or via the LRC.settings within the pRTI installation setup.
There is the possiblity to run the test cases on command line with gradle. There are two test cases ETR_0001 (SuT in role task receiver) and ETR_0002 (SuT in role tasker). To run a dedicated test case TC use the following command:
./gradlew :NETN-ETR:test --tests "org.nato.netn.etr.NetnEtrTestSuiteTest.[TC]", where the method TC can be one of
| TC | Description |
|---|---|
| testETR_0001atLocalhost | test case ETR_0001 with local RTI |
| testETR_0001atPITIS223 | test case ETR_0001 with PITIS connection set |
| testETR_0002atLocalhost | test case ETR_0002 with local RTI |
| testETR_0002atPITIS223 | test case ETR_0002 with PITIS connection |
There is one single configuration file TcParam.json in NETN-ETR/src/main/resources for both test cases:
{
"federationName" : "NETN4",
"sutFederateName" : "Pitch Actors",
"supportedActions" : ["MoveByRoute"],
"publishedTasks" : ["MoveByRoute", "MoveToLocation"],
"subscribedReports" : ["ObservationReport", "PositionStatusReport"],
"taskId" : "77e004e5-a3b3-43be-b655-0f9167ec051b",
"speed" : 88,
"route" : [{"x": 58.38580, "y" : 15.55502}, {"x" : 58.37753, "y" : 15.56698}],
"selfTest" : true,
"cancelTask" : false
}The meaning of the parameters and which test case uses them is described in the following table:
| Parameter | Used By | Description |
|---|---|---|
| federationName | ETR_0001,2 | the name of the federation |
| sutFederateName | ETR_0001,2 | the name of the SuT to be tested |
| supportedActions | ETR_0001,2 | the list of the actions supported by the SuT (1) or the entity to be tasked (2) according to the CS |
| publishedTasks | ETR_0002 | the list of tasks the tasker should have published according to the CS |
| subscribedReports | ETR_0002 | the list of report types the tasker should have subscribed according to the CS |
| taskId | ETR_0001 | the task Id the tasker uses for the task sent to the SuT (task receiver) |
| speed | ETR_0001 | the speed in m/s used for each waypoint in the WaypointStruct of the MoveByRoute task |
| route | ETR_0001 | the list of waypoints used for the aypointStruct of the MoveByRoute task |
| selfTest | ETR_0001 | a boolean value to control a sef test mode, in case of true the SuT is simply simulated |
| cancelTask | ETR_0001 | a boolean value to control the use of the Cancel task (i.e. the task will not complete instead should break after receiving this task and answer with ETR_TaskStatus(Cancelled) |
Copyright 2025 NATO/OTAN
Licensed under the Apache License, Version 2.0