SDL behavior in case 'HeartBeat' param is empty

[LitvinenkoIra]

Occurrence: Always

Description

SDL behavior in case 'HeartBeat' param is empty

Preconditions

• SDL and HMI are started.
• App is registered and activated.

Steps to reproduce

1. "HeartBeat" param is empty in .ini file

Actual result

SDL does not send HeartBeat messages to App

Expected result

SDL must set the default value = 5000 ms
respond ACK to HeartBeat_request from mobile app
send HeartBeat_request to mobile app

Environment

Attachments

Expected delivery

• Source code updates
• Code comments
• UTs add/update (not required)
• ATF tests add/update
• Manual tests (not required)
• Add/update CI plans/jobs (not required)
• SDD updates (not required)
• Guidelines update (sdl_core_guides) (not required)
• Guidelines update (sdl_hmi_integration_guidelines) (not required)

[dboltovskyi]

Priority was set to Low since there is no significant functionality loss and default value of 'HeartBeatTimeout' parameter is present in .INI file

[robinmk]

1. What is the actual result?
2. Is the Mobile App initiating this flow by triggering a heart_beat request?

[dboltovskyi]

@robinmk

1. Actual result is provided in updated description
2. Correct - Mobile App initiates heartbeat flow

[iCollin]

Closed via #2513