automation: Verify SON sends heartbeat at regular interval #251

Closed
opened 2022-01-17 11:06:08 +00:00 by pavel.baykov · 2 comments
pavel.baykov commented 2022-01-17 11:06:08 +00:00 (Migrated from gitlab.com)

Consider an active son configured on some node.

list_active_sons will give you the list of active sons
Verify the current SON status using below command

get_son <<son_account>>
From the previous steps, extract statistics object id.
Check last_active_timestamp using below command
get_object <<statistics_object_id>>
Wait for next heartbeat to be sent ( i.e 3 mins)

Verify last_active_timestamp is updated
get_object <<statistics_object_id>>

Consider an active son configured on some node. list_active_sons will give you the list of active sons Verify the current SON status using below command get_son <<son_account>> From the previous steps, extract statistics object id. Check last_active_timestamp using below command get_object <<statistics_object_id>> Wait for next heartbeat to be sent ( i.e 3 mins) Verify last_active_timestamp is updated get_object <<statistics_object_id>>
pavel.baykov commented 2022-01-17 11:06:08 +00:00 (Migrated from gitlab.com)

assigned to @pavel.baykov

assigned to @pavel.baykov
pavel.baykov commented 2022-01-21 09:07:18 +00:00 (Migrated from gitlab.com)

to test:
pytest -s -v test.py::test_Verify_SON_Sends_Heartbeat

to test: pytest -s -v test.py::test_Verify_SON_Sends_Heartbeat
serkixenos (Migrated from gitlab.com) closed this issue 2022-01-31 01:43:10 +00:00
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Peerplays_Blockchain/peerplays_migrated#251
No description provided.