And A regular step creator with the name "TestStep" and the following properties | 0 ms | Passed |
And I confirm job target has step index 0 and status "PROCESS_FAILED" | 0 ms | Passed |
And I confirm job target has step index 0 and status "PROCESS_FAILED" | 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 job target item | 0 ms | Passed |
And I create a new step entity from the existing creator | 0 ms | Passed |
And I get the KuraMock device | 0 ms | Passed |
And I logout | 0 ms | Passed |
And I query for the job with the name "TestJob" and I find it | 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 "BIRTH" | 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 start the Kura Mock | 0 ms | Passed |
Scenario: Restarting job with invalid Command Execution step two times | 29 ms | Passed |
Then Device status is "CONNECTED" | 0 ms | Passed |
Then I find 1 device event | 0 ms | Passed |
Then I find 1 device event | 0 ms | Passed |
Then I restart a job | 0 ms | Passed |
Then I restart a job | 0 ms | Passed |
Then KuraMock is disconnected | 0 ms | Passed |
When Device is connected | 3 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 for events from device "rpione3" in account "kapua-sys" | 0 ms | Passed |
When I search for events from device "rpione3" in account "kapua-sys" | 0 ms | Passed |