Skip to content

FIT: Recovery Action due to complex reporting failure #184

Description

@TimoSteuerwaldETAS

What

Verifies requirements:

Depends on: #172

Configuration:

  • Extend config in FIT: Launch initial run target #172 by
    • Run Target run_target_app_does_call_report_running_in_time which contains a Component component_does_call_report_running_in_time
    • Run Target run_target_app_does_not_call_report_running_in_time which contains a Component component_does_not_call_report_running_in_time
  • Recovery Action on run_target_app_does_not_call_report_running_in_time configured to switch to Run Target Startup
  • The process involved in component_does_report_krunning does call LifeCycleManager::report_running() in time (500ms below boundary)
  • The process involved in component_does_not_call_report_running_in_time does not call LifeCycleManager::report_running() in time (500ms above boundary)

Test steps:

  • Start Launch Manager process
  • Via score::lcm::ControlClient::ActivateRunTarget(..) activate run_target_app_does_call_report_running_in_time
  • Via score::lcm::ControlClient::ActivateRunTarget(..) activate run_target_app_does_not_call_report_running_in_time

Expected behavior:

  • Launch Manager is started successfully and Run Target Startup is activated initially
  • Run Target run_target_app_does_call_report_running_in_time is activated
  • Run Target run_target_app_does_not_call_report_running_in_time can not be activated
  • Recovery Action is executed and Run Target Startup is activated

Acceptance Criteria (DoD)

Test specification and implementation exists. Test passes.

Metadata

Metadata

Labels

No labels
No labels

Type

No fields configured for Task.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions