-
Notifications
You must be signed in to change notification settings - Fork 6
Expand file tree
/
Copy pathpull_request.yaml
More file actions
56 lines (49 loc) · 2.13 KB
/
Copy pathpull_request.yaml
File metadata and controls
56 lines (49 loc) · 2.13 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
# config/default.yaml
version: "1.0" # Configuration schema version
run_id: "daily-conformance-check" # An optional identifier for the run
# Details of the Flight Blender deployment under test
flight_blender:
url: "http://localhost:8000"
auth:
type: "none" # For using the dummy-oauth provider
audience: "testflight.flightblender.com" # Audience for OAuth tokens, default for local testing
scopes: ["flightblender.write", "flightblender.read"] # Scopes for write and read access
# Details for connecting to the OpenSky Network API
opensky:
auth:
type: "none" # 'none' for no auth, 'oauth2' for OAuth2 client credentials
client_id: "your-client-id"
client_secret: "your-client-secret"
# Default air traffic simulator settings (can be overridden per step in scenario YAML)
air_traffic_simulator_settings:
number_of_aircraft: 3
simulation_duration: 10
single_or_multiple_sensors: "multiple" # this setting specifies if the traffic data is submitted from a single sensor or multiple sensors
sensor_ids: ["a0b7d47e5eac45dc8cbaf47e6fe0e558"] # List of sensor IDs to use when 'multiple' is selected
data_files:
trajectory: "config/bern/trajectory_f1.json" # Path to flight declarations JSON file
flight_declaration: "config/bern/flight_declaration.json" # Path to flight declarations JSON file
geo_fence: "config/bern/geo_fence.geojson"
# List of test scenario IDs to execute
suites:
pull_requests:
scenarios:
- name: add_flight_declaration
- name: F1_happy_path
trajectory: "config/bern/trajectory_f1.json"
- name: F2_contingent_path
trajectory: "config/bern/trajectory_f2.json"
- name: F3_non_conforming_path
trajectory: "config/bern/trajectory_f3.json"
- name: opensky_live_data
- name: geo_fence_upload
- name: openutm_sim_air_traffic_data
# Reporting configuration
reporting:
output_dir: "reports"
formats: ["json", "html", "log"] # 'json' is raw, 'html' is summarized
# A place to add metadata about the system under test
deployment_details:
name: "Local Flight Blender Dev Instance"
version: "v0.12.0"
notes: "Running against local Docker Compose setup."