And A regular step creator with the name "TestStep" and the following properties | 0 ms | Passed |
And Command pwd is executed | 0 ms | Passed |
And I add targets to job | 0 ms | Passed |
And I confirm job target has step index 0 and status "PROCESS_OK" | 0 ms | Passed |
And I confirm job target has step index 0 and status "PROCESS_OK" | 0 ms | Passed |
And I confirm the executed job is finished | 0 ms | Passed |
And I confirm the executed job is finished | 0 ms | Passed |
And I create a new step entity from the existing creator | 0 ms | Passed |
And I get the KuraMock devices | 0 ms | Passed |
And I logout | 0 ms | Passed |
And I select account "kapua-sys" | 0 ms | Passed |
And I wait 1 second | 0 ms | Passed |
And I wait 1 second | 0 ms | Passed |
And I wait 1 second | 0 ms | Passed |
And Search for step definition with the name "Command Execution" | 0 ms | Passed |
And The type of the last event is "COMMAND" | 0 ms | Passed |
Given I add 2 devices to Kura Mock | 0 ms | Passed |
Given I create a job with the name "TestJob" | 0 ms | Passed |
Given I query for the job with the name "TestJob" and I find it | 0 ms | Passed |
Given I query for the job with the name "TestJob" and I find it | 0 ms | Passed |
Scenario: Restarting job with valid Command Execution step and multiple devices two times | 42 ms | Passed |
Then Devices status is "CONNECTED" | 0 ms | Passed |
Then I restart a job | 0 ms | Passed |
Then I restart a job | 0 ms | Passed |
Then KuraMock is disconnected | 4 ms | Passed |
When Devices are connected | 1 ms | Passed |
When I login as user with name "kapua-sys" and password "kapua-password" | 0 ms | Passed |
When I query for the execution items for the current job and I count 1 | 0 ms | Passed |
When I query for the execution items for the current job and I count 2 | 0 ms | Passed |
When I search events from devices in account "kapua-sys" and 2 events are found | 0 ms | Passed |
When I search events from devices in account "kapua-sys" and 3 or more events are found | 0 ms | Passed |