Page : iii /
EUROCONTROL EXPERIMENTAL CENTRE
Brétigny-sur-Orge, FRANCE
AVT
eDEP/eCockpit Integration Project
Technical Document
Component Test Scripts
Issue: 1.0
Issue date: 14 Aug 20071 May 2007
The information contained in this document is the property of the EUROCONTROL Agency and no part should be reproduced in any form without the Agency’s permission.
The views expressed herein do not necessarily reflect the official views or policy of the Agency.
Document Change Log /Rel. / Author / Date of the release / Description of the release / Modifications (sections affected and relevant information) /
0.1 / Graffica (Cooper) / 3rd Sept 2004 / Document Created / All
0.2 / Graffica (Cooper) / 24th Sept 2004 / Updated following on-site testing at EEC (13th-17th Sept, 2004) / All
0.3 / Graffica (Cooper) / 1st Oct 2004 / Added initials and date to comments / All Observations
0.4 / Graffica (Cooper) / 2nd Nov 2004 / Added WP2.4 Tests and updated following comments from EEC. / Added sections for ARTAS, IAS and flight plan modifications.
Added references to STP test cases where omitted.
Added eDEP integration test cases.
0.5 / Graffica (Cooper) / 12th Nov 2004 / Updated WP2.4 tests. / Updated details in tests for ARTAS and IAS section.
0.6 / Graffica (Kirkwood) / 3rd December 2004 / Added WP2.5 CDTI tests. / Section 10
0.7 / Graffica (Kirkwood) / 11th January 2005 / Minor changed to WP2.5 CDTI tests / Section 10
0.8 / Graffica (Cooper) / 1st February 2005 / Added WP2.3 tests. / Section 11
0.9 / Graffica (Kirkwood) / 8th February 2005 / Added UDP forwarding test. / Section 12
0.10 / Graffica (Cooper) / 11th February 2005 / Updated Tests / All Sections.
0.11 / Graffica (Kirkwood) / 15th February 2005 / Extended UDP forwarding tests to include Cat 244 and Cat 62. / Section 12.1
0.12 / Graffica (Cooper) / 22nd February 2005 / Updated tests involving PWP. / Section 11
0.13 / Graffica (Kirkwood) / 12th April 2005 / Updated UDP forwarding tests. / Section 12.1.
0.14 / Graffica (Kirkwood) / 13th April 2005 / Run tests and made observations. / All
0.15 / Graffica (Kirkwood) / 14th April 2005 / Added Test for ARTAS replay tool. / Section 13.
0.16 / Graffica (Kirkwood) / 20th April 2005 / Added Dynamic Flightplan correlation test. / Section 8.2.5
0.17 / Graffica (Kirkwood) / 26th April 2005 / Updated tests. / All
0.18 / Graffica (Kirkwood) / 3rd May 2005 / Updated Test EE_UDP_004, timeOfDay field. / Section 12.1.3
0.19 / Graffica (Kirkwood) / 4th May 2005 / Corrections to Test EE_UDP_005. / Section 12.1.4
0.20 / Graffica (Kirkwood) / 13th May 2005 / Modifications following ARTAS refactoring. / Section 4.4 (Test Removed), Section 7.2.1
0.21 / Graffica (Kirkwood) / 9th June 2005 / Added PM Generated Cat-244 UDP forwarding test. / 12.1.5
0.22 / Graffica (Kirkwood) / 20th June 2005 / Updated resource locations following resource refactoring. / All
0.23 / Graffica (Kirkwood) / 24th June 2005 / Updated tests following refactoring and test run. / All
0.24 / Graffica (Kirkwood) / 29th June 2005 / Updated tests according to AVT action list and following Flightplan based Trajectory ID for PM generated ADSBReports. / All
0.25 / Graffica (Kirkwood) / 21st October 2005 / Added test for eCockpit and PWP coexistence. / Section 14
0.26 / Graffica (Kirkwood) / 1st April 2007 / Added tests for AVT Cristal Med / Sections 7.3, 7.4, 8.2, 15
1.0 / Graffica(Thom) / 14th Aug 2007 / Version number change to Graffica standard / N/A
Acceptance and Reviewing Procedures /
Name (s) / Date of acceptance/ review / Date of approval /
Darren Smith
Mike Vere
Document distribution /
to/cc / Name / Role /
to / Tim Cooper / Graffica Technical Lead
to / Darren Smith / EEC Point of Contact for eCockpit
to / Leo van der Hoorn / AVT Project Manager
Table of contents
1 Introduction 6
1.1 Purpose 6
1.2 Intended audience 6
1.3 Responsibilities 6
1.4 Associated documentation 6
1.5 Test Configuration 6
2 test environment 8
2.1 Related Documents 8
2.2 File Structure 8
2.3 Launcher HMI 8
3 EDEP Integration Tests 8
3.1 Time and IFPL Services 8
3.2 Airspace Service 9
4 ASTERIX Message Tests 10
4.1 Cat21 Message Format 10
4.2 Cat244 Message Format 10
4.3 Cat62 Message Format 11
5 ADS-B Tests 11
5.1 Cat21 Messages 12
5.2 Cat244 Messages 13
5.3 Joint Cat244 and Cat21 Messages 15
6 TIS-B Tests 16
6.1 Cat62 Messages 16
7 ARTAS Proxy Server Tests 18
7.1 Cat62 Messages 18
7.2 Cat32 Messages 19
8 IAS Tests 24
8.1 IAS Connection Tests 24
8.2 IAS Correlation 25
9 Flight Plan Modification Test 32
9.1 ICAO 24-Bit Address 32
10 CDTI Tests 34
10.1 CDTI / ND Plugin framework 34
11 WP2.3 Simulated Environment Tests 38
11.1 PM ADS-B Tests 38
11.2 IAS Tests 46
11.3 CWP Tests 51
11.4 eCockpit Tests 56
11.5 RMI Tests 61
11.6 EDEP ATC Testing 62
12 UDP Forwarding Tests 62
12.1 UDP Forwarding Tests 62
13 ARTAS Replay Tests 71
13.1 ARTAS Replay Tests 71
14 Simulated & cockpit flight coexistence 73
14.1 Simulated and Cockpit flight coexistence 73
STATUS TITLE
Company Ref. Template : normal.dot
eCP_CTSD.docPage : 9 /
1 Introduction
1.1 Purpose
This document contains component level tests for the eDEP/eCockpit Integrated system, being developed for TRSB164/2003.
This document will evolve as the iterations of the project are completed.
1.2 Intended audience
This document is of interest to all eDEP and eCockpit developers.
1.3 Responsibilities
The Graffica project manager is responsible for updating this document.
1.4 Associated documentation
1.4.1 Internal project documentation
Reference / Title / Reference/Filename / Date /1. / eCockpit Software Test Plan / eCP_STP.doc
2. / eCockpit Detailed Design Document / eCockpit_DDD.doc
1.4.2 General documentation
Reference / Title / Authors / Date /eDEP Component Test Script Document / eDEP_CTSD.doc / 07/10/04
1.5 Test Configuration
Ecockpit related tests are run via the eCockpit Launcher. Component tests for the ARTAS, ADSB, TISB and asterix message components are launched via the ATCLive Launcher. AVT configurations are launched via the AVT Launcher.
Each test is run via the selection of a test script. There are 3 styles of test used:
· Static unit test – The scenario runs a JUnit test that evaluates the state of the system. Primarily used in message conversion unit-tests, where a binary message is read in from a file and the data checked against expected values.
· Single cockpit tests and test harness – An eCockpit display is loaded and UDP connections to the test harness are established. The test harness is loaded with a recorded scenario file containing ASTERIX Cat244 data. When the test harness is started it transmits Cat244 messages to the UDP channel, simulating aircraft generation of the messages.
· Multiple cockpit tests and test harness – Two or more eCockpit displays are loaded and connect to the test harness. The test harness converts received Cat244 messages from one eCockpit into Cat21 messages that are forwarded to the other eCockpits.
The test harness is used to simulate the UDP connection to the SMART system. In later iterations the test harness will be replaced with a connection to the SMART / ARTAS system by changing the UDP connections used by the eCockpit displays.
The following diagrams show example configurations of the eCockpit display with the test harness:
Figure 1 – Example of Single eCockpit with Test Harness (ADS-B)
Figure 2 – Example of Two eCockpit displays with Test Harness
Figure 3 – Example of Single eCockpit with Test Harness (TIS-B)
All test cases are detailed for the test cases running with the test harness on one machine and the eCockpit displays running remotely on another machine. In all cases another script has been provided that will run the test harness and all displays on a single machine.
2 test environment
2.1 Related Documents
The eDEP/eCockpit Integration Project Software Test Plan (see Reference 1) defines the high level test cases.
2.2 File Structure
The tests are found within the following locations:
· <eCockpit root>/src/resources/componenttests
· <atclive root>/src/resources/componenttests
· <avt root>/src/resources/componenttests
2.3 Launcher HMI
The eCockpit tests and test harness may be launched via cockpit.Launcher, for which an Eclipse launch script file exists. ARTAS and asterix message tests may be launched via atclive.Launcher. AVT configurations are launched using avt.Launcher.
3 EDEP Integration Tests
The following tests deal with the integration of the eCockpit system with the eDEP services.
3.1 Time and IFPL Services
The following test demonstrates the eCockpit system running using the eDEP time control panel and following a trajectory defined by an eDEP flightplan file.
Scenario ID / INT_SVC_001Tested Functionality / SSP_TS_10
SSP_FL_10
Objective / Demonstrate that:
1. The eCockpit system used the eDEP time control panel for simulation control.
2. The eCockpit flight follows the trajectory defined by an eDEP flightplan file.
Resource File / Launch script:
<eCockpit home>/resources/componenttests/integration/INT_SVC_001.gsdk
Flight Plan File: <eCockpit home>/resources/flightplan/single_aircraft_traffic.dat
Airspace File: <atclive home>/resources/airspace/NFAirspace.dat
ID / Time / Actions / Expectations / Observations
1 / Launch eCockpit / The eCockpit display is shown with a time control panel.
2 / 16:12:00 / Start the eCockpit simulation. / The eCockpit display initialises and starts.
3 / 16:12:10 / Pause the eCockpit simulation. / The eCockpit simulation pauses.
4 / Run the simulation.
Increase simulation speed 5 times. / The eCockpit simulation starts.
The simulation speed increases with each press of the button.
5 / Observe the flight. / The flight is seen to change its speed, altitude and trajectory as it moves between waypoints.
The trajectory followed matches the flightplan specified in the flightplan file.
3.2 Airspace Service
The following test demonstrates the eCockpit system receiving airspace definitions from eDEP.
Scenario ID / INT_SVC_002Tested Functionality / SSP_ARSPC_10
Objective / Demonstrate that the eCockpit system receives airspace definitions from eDEP.
Resource File / Launch script 1:
<eCockpit home>/resources/componenttests/integration/INT_SVC_002.gsdk
Launch script 2:
<eCockpit home>/resources/componenttests/integration/INT_SVC_003.gsdk
Flight Plan File 1: <eCockpit home>/resources/flightplan/traffic.dat
Flight Plan File 2: <eCockpit home>/resources/flightplan/single_aircraft_traffic.dat
Airspace File 1: <atclive home>/resources/airspace/airspace.dat
Airspace File 2: < atclive home>/resources/airspace/NFAirspace.dat
ID / Time / Actions / Expectations / Observations
1 / Launch script 1. / The eCockpit display is shown with a time control panel.
2 / 16:12:00 / Start the eCockpit simulation. / The eCockpit display initialises and starts.
3 / Observe the airspace. / The airspace shown matches the eDEP airspace file ‘airspace.dat’. The flight is travelling between ‘WP1’ and ‘WP0’, with ‘WP3’ to the left of the flight and ‘WP4’ to the right of the flight.
4 / Launch script 2. / The eCockpit display is shown with a time control panel.
5 / 16:12:00 / Start the eCockpit simulation. / The eCockpit display initialises and starts.
6 / Observe the airspace. / The airspace is different from the previous scenario, and represents North France. The contents of the airspace matches the eDEP airspace file ‘NFAirspace.dat’. The flight is travelling between ‘CENT’ and ‘ARDEN’, with ‘KATIL’ to the left of the flight and ‘REM’ to the right.
4 ASTERIX Message Tests
These tests are used to verify that the eDEP/eCockpit integration project software can correctly read formatted ASTERIX messages from binary data, in this case a sample binary message read from a file. There is one test for each of the formats supported, Cat21, Cat244, Cat62 and Cat32. Each test can be run independently, reads messages from a file and compares the contents against the expected results. No interaction is required other than launching the test script specified.
The tests are run using JUnit. The expected output from each test is that the test has been passed.
4.1 Cat21 Message Format
Scenario ID / ATX21_001Tested Functionality / SSP_AP_10
Objective / Check that binary data can be correctly identified as a Cat21 message, with access to the fields defined by the message specification.
Resource File / Launch script:
<atclive home>/resources/componenttests/asterixmessages/ATX21_001.gsdk
File containing single binary message:
atclive/resources/binarymessages/singleCat21.bin
ID / Time / Actions / Expectations / Observations
1 / Launch the atclive scenario ATX21_001.gsdk. / Console output shows the text content of the Cat 21 message read from the binary data file.
The message content is checked within the unit test and passes successfully.
4.2 Cat244 Message Format
Scenario ID / ATX244_001Tested Functionality / SSP_AP_20
SSP_ACP_20
Objective / Check that the integrated asterix reader software can correctly generate binary data containing a Cat244 message.
Resource File / Launch script:
<atclive home>/resources/componenttests/asterixmessages/ATX244_001.gsdk
File containing single binary message:
atclive/resources/binarymessages/singleCat244.bin
ID / Time / Actions / Expectations / Observations
1 / Launch the atclive scenario ATX244_001.gsdk. / Console output shows the text content of the Cat 244 message read from the binary data file.
The message content is checked within the unit test and passes successfully.
4.3 Cat62 Message Format
Scenario ID / ATX62_001Tested Functionality / SSP_TP_10
SSP_TCP_10
Objective / Check that the integrated asterix reader software can correctly read binary data containing a Cat62 message.
Resource File / Launch script:
<atclive home>/resources/componenttests/asterixmessages/ATX62_001.gsdk
File containing single binary message:
atclive/resources/binarymessages/singleCat62.bin
ID / Time / Actions / Expectations / Observations
1 / Launch the atclive scenario ATX62_001.gsdk. / Console output shows the text content of the Cat 62 message read from the binary data file.
The message content is checked within the unit test and passes successfully.
5 ADS-B Tests
These tests deal with the generation and processing of ADS-B Cat21 and Cat244 messages within eCockpit. Test cases that are greyed out are related to the actual visualisation of information within the eCockpit display, and are dependent on upgrades to the CDTI display.