Test Result

452 failures (+452) , 3,684 skipped (+3680)
11,543 tests (+11375)
Took 1 hr 7 min.

All Failed Tests

Test NameDurationAge
 Scenario: Start broker for all scenarios.Given Start Broker1 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms1
 Scenario: Find correct number of messages by corresponding metric.Then I prepare a number of messages with the following details and remember the list as "TestMessages"2 ms1
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric2 ms1
 Scenario: Finding correct number of messages by corresponding two metrics.Then I prepare a number of messages with the following details and remember the list as "TestMessages"2 ms1
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics3 ms1
 Scenario: Finding all messages by selecting all metrics.Then I prepare a number of messages with the following details and remember the list as "TestMessages"4 ms1
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics4 ms1
 Scenario: Finding messages with incorrect metric parameters.Then I prepare a number of messages with the following details and remember the list as "TestMessages"2 ms1
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters2 ms1
 Scenario: Start broker for all scenarios.Given Start Broker2 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms1
 Scenario: Start broker for all scenarios.Given Start Broker2 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms1
 Scenario: Start broker for all scenarios.Given Start Broker2 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms1
 Scenario: Find correct number of messages by corresponding metric.Then I prepare a number of messages with the following details and remember the list as "TestMessages"6 ms1
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric6 ms1
 Scenario: Finding correct number of messages by corresponding two metrics.Then I prepare a number of messages with the following details and remember the list as "TestMessages"1 ms1
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics2 ms1
 Scenario: Finding all messages by selecting all metrics.Then I prepare a number of messages with the following details and remember the list as "TestMessages"1 ms1
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics1 ms1
 Scenario: Finding messages with incorrect metric parameters.Then I prepare a number of messages with the following details and remember the list as "TestMessages"1 ms1
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters1 ms1
 Scenario: Start broker for all scenarios.Given Start Broker2 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms1
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"6 ms1
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed7 ms1
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"4 ms1
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY5 ms1
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown4 ms1
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account5 ms1
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Then An exception was thrown2 ms1
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed4 ms1
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"3 ms1
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms1
 Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown5 ms1
 Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed7 ms1
 Scenario: Start broker for all scenarios.Given Start Broker24 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios24 ms1
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"3 ms1
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY5 ms1
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"3 ms1
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY5 ms1
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown4 ms1
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account6 ms1
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Then An exception was thrown7 ms1
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed9 ms1
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"4 ms1
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed6 ms1
 Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme/foo"4 ms1
 Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed6 ms1
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown1 ms1
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed2 ms1
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"3 ms1
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms1
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown2 ms1
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms1
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"5 ms1
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY7 ms1
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"3 ms1
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY5 ms1
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown3 ms1
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account4 ms1
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"3 ms1
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed5 ms1
 Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme/foo"3 ms1
 Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed4 ms1
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown3 ms1
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed4 ms1
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"11 ms1
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed11 ms1
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"15 ms1
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY15 ms1
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"4 ms1
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY17 ms1
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown2 ms1
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account3 ms1
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Then An exception was thrown3 ms1
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed4 ms1
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"2 ms1
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed4 ms1
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Then Broker doesn't receive string "Hello broker" on topic "acme/foo"2 ms1
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed4 ms1
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"4 ms1
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms1
 Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown6 ms1
 Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed7 ms1
 Scenario: Start broker for all scenarios.Given Start Broker1 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms1
 Scenario: Send BIRTH message and then DC message.And Bundles are requested6 ms1
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message7 ms1
 Scenario: Start broker for all scenarios.Given Start Broker1 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms1
 Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Then Device is connected with "localhost" server ip2 ms1
 Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Scenario: Send BIRTH message and then DC message while broker ip is set by config file5 ms1
 Scenario: Start broker for all scenarios.Given Start Broker1 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms1
 Scenario: Send BIRTH message and then DC message while broker ip is set by System.Then Device is connected with "localhost" server ip2 ms1
 Scenario: Send BIRTH message and then DC message while broker ip is set by System.Scenario: Send BIRTH message and then DC message while broker ip is set by System4 ms1
 Scenario: Start broker for all scenarios.Given Start Broker2 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms1
 Scenario: Start broker for all scenarios.Given Start Broker2 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms1
 Scenario: Stealing link scenario.And Client named "client-2" is not connected4 ms1
 Scenario: Stealing link scenario.Scenario: Stealing link scenario6 ms1
 Scenario: Start broker for all scenarios.Given Start Broker2 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms1
 Scenario: Connect to the system and publish some data.Then Device sim-1 for account kapua-sys is registered after 5 seconds4 ms1
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data6 ms1
 Scenario: Start broker for all scenarios.Given Start Broker1 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms1
 Scenario: Starting and stopping the simulator should create a device entry and properly set its status.Then Device sim-1 for account kapua-sys is registered after 5 seconds3 ms1
 Scenario: Starting and stopping the simulator should create a device entry and properly set its status.Scenario: Starting and stopping the simulator should create a device entry and properly set its status5 ms1
 Scenario: Installing a package.Then Device sim-1 for account kapua-sys is registered after 5 seconds9 ms1
 Scenario: Installing a package.Scenario: Installing a package11 ms1
 Scenario: Start broker for all scenarios.Given Start Broker1 ms1
 Scenario: Start broker for all scenarios.Given Start Broker2 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms1
 Scenario: Restarting job with Command Execution step.And A new job target item2 ms1
 Scenario: Restarting job with Command Execution step.Scenario: Restarting job with Command Execution step3 ms1
 Scenario: Restarting job with Asset Write step.And A new job target item1 ms1
 Scenario: Restarting job with Asset Write step.Scenario: Restarting job with Asset Write step2 ms1
 Scenario: Restarting job with Configuration Put step.And A new job target item2 ms1
 Scenario: Restarting job with Configuration Put step.Scenario: Restarting job with Configuration Put step2 ms1
 Scenario: Restarting job with Bundle Start step.And A new job target item2 ms1
 Scenario: Restarting job with Bundle Start step.Scenario: Restarting job with Bundle Start step2 ms1
 Scenario: Restarting job with Bundle Stop step.And A new job target item2 ms1
 Scenario: Restarting job with Bundle Stop step.Scenario: Restarting job with Bundle Stop step2 ms1
 Scenario: Restarting job with Package Install step.And A new job target item2 ms1
 Scenario: Restarting job with Package Install step.Scenario: Restarting job with Package Install step2 ms1
 Scenario: Restarting job with Package Uninstall step.And A new job target item1 ms1
 Scenario: Restarting job with Package Uninstall step.Scenario: Restarting job with Package Uninstall step2 ms1
 Scenario: Restarting job with two Bundle Start steps.And A new job target item2 ms1
 Scenario: Restarting job with two Bundle Start steps.Scenario: Restarting job with two Bundle Start steps3 ms1
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.And A new job target item1 ms1
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.Scenario: Restarting job with Bundle Stop and Bundle Start steps2 ms1
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.And A new job target item2 ms1
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices3 ms1
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices3 ms1
 Scenario: Restarting a job with Package Uninstall and Bundle Start steps.And A new job target item1 ms1
 Scenario: Restarting a job with Package Uninstall and Bundle Start steps.Scenario: Restarting a job with Package Uninstall and Bundle Start steps2 ms1
 Scenario: Restarting a job with Command Execution and Bundle Start steps.And A new job target item2 ms1
 Scenario: Restarting a job with Command Execution and Bundle Start steps.Scenario: Restarting a job with Command Execution and Bundle Start steps4 ms1
 Scenario: Restarting a job with Asset Write and Bundle Start steps.And A new job target item1 ms1
 Scenario: Restarting a job with Asset Write and Bundle Start steps.Scenario: Restarting a job with Asset Write and Bundle Start steps2 ms1
 Scenario: Restarting a job with Configuration Put and Bundle Start steps.And A new job target item2 ms1
 Scenario: Restarting a job with Configuration Put and Bundle Start steps.Scenario: Restarting a job with Configuration Put and Bundle Start steps3 ms1
 Scenario: Restarting job with Bundle Start step and multiple devices.Then I count 21 ms1
 Scenario: Restarting job with Bundle Start step and multiple devices.Scenario: Restarting job with Bundle Start step and multiple devices2 ms1
 Scenario: Restarting job with Bundle Stop step and multiple devices.Then I count 21 ms1
 Scenario: Restarting job with Bundle Stop step and multiple devices.Scenario: Restarting job with Bundle Stop step and multiple devices2 ms1
 Scenario: Restarting job with Package Download/Install step and multiple devices.Then I count 21 ms1
 Scenario: Restarting job with Package Download/Install step and multiple devices.Scenario: Restarting job with Package Download/Install step and multiple devices2 ms1
 Scenario: Restarting job with Package Uninstall step and multiple device.Then I count 21 ms1
 Scenario: Restarting job with Package Uninstall step and multiple device.Scenario: Restarting job with Package Uninstall step and multiple device2 ms1
 Scenario: Restarting job with Asset Write step and multiple devices.Then I count 21 ms1
 Scenario: Restarting job with Asset Write step and multiple devices.Scenario: Restarting job with Asset Write step and multiple devices2 ms1
 Scenario: Restarting job with Configuration Put step and multiple devices.Then I count 22 ms1
 Scenario: Restarting job with Configuration Put step and multiple devices.Scenario: Restarting job with Configuration Put step and multiple devices3 ms1
 Scenario: Restarting job with Command Execution step and multiple devices.Then I count 24 ms1
 Scenario: Restarting job with Command Execution step and multiple devices.Scenario: Restarting job with Command Execution step and multiple devices6 ms1
 Scenario: Restarting job with two Bundle Start steps and multiple devices.Then I count 22 ms1
 Scenario: Restarting job with two Bundle Start steps and multiple devices.Scenario: Restarting job with two Bundle Start steps and multiple devices3 ms1
 Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices.Then I count 22 ms1
 Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices.Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices2 ms1
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.Then I count 22 ms1
 Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device.Then I count 22 ms1
 Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device.Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device3 ms1
 Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices.Then I count 22 ms1
 Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices.Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices3 ms1
 Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices.Then I count 21 ms1
 Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices.Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices2 ms1
 Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices.Then I count 21 ms1
 Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices.Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices2 ms1
 Scenario: Starting a job with Command Execution step.And A new job target item2 ms1
 Scenario: Starting a job with Command Execution step.Scenario: Starting a job with Command Execution step3 ms1
 Scenario: Starting a job with Asset Write step.And A new job target item1 ms1
 Scenario: Starting a job with Asset Write step.Scenario: Starting a job with Asset Write step2 ms1
 Scenario: Starting a job with Bundle Start step.And Bundles are requested2 ms1
 Scenario: Starting a job with Bundle Start step.Scenario: Starting a job with Bundle Start step3 ms1
 Scenario: Starting a job with Bundle Stop step.And Bundles are requested2 ms1
 Scenario: Starting a job with Bundle Stop step.Scenario: Starting a job with Bundle Stop step2 ms1
 Scenario: Starting a job with Configuration Put step.And A new job target item1 ms1
 Scenario: Starting a job with Configuration Put step.Scenario: Starting a job with Configuration Put step2 ms1
 Scenario: Starting a job with Package Install step.Then Device status is "DISCONNECTED"5 ms1
 Scenario: Starting a job with Package Install step.Scenario: Starting a job with Package Install step7 ms1
 Scenario: Starting a job with Package Uninstall step.And Package named org.eclipse.kura.example.beacon with version 1.0.300 is received2 ms1
 Scenario: Starting a job with Package Uninstall step.Scenario: Starting a job with Package Uninstall step2 ms1
 Scenario: Starting a job with Command Execution and Bundle Start steps.And Bundles are requested2 ms1
 Scenario: Starting a job with Command Execution and Bundle Start steps.Scenario: Starting a job with Command Execution and Bundle Start steps3 ms1
 Scenario: Starting a job with Asset Write and Bundle Start steps.And Bundles are requested1 ms1
 Scenario: Starting a job with Asset Write and Bundle Start steps.Scenario: Starting a job with Asset Write and Bundle Start steps2 ms1
 Scenario: Starting a job with two Bundle Start steps.And Bundles are requested3 ms1
 Scenario: Starting a job with two Bundle Start steps.Scenario: Starting a job with two Bundle Start steps4 ms1
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.And Bundles are requested1 ms1
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.Scenario: Starting a job with Bundle Stop and Bundle Start steps2 ms1
 Scenario: Starting a job with Configuration Put and Bundle Start steps.And Bundles are requested1 ms1
 Scenario: Starting a job with Configuration Put and Bundle Start steps.Scenario: Starting a job with Configuration Put and Bundle Start steps2 ms1
 Scenario: Starting a job with Package Install and Bundle Start steps.And Bundles are requested2 ms1
 Scenario: Starting a job with Package Install and Bundle Start steps.Scenario: Starting a job with Package Install and Bundle Start steps3 ms1
 Scenario: Starting a job with Package Uninstall and Bundle Start steps.And Package named org.eclipse.kura.example.beacon with version 1.0.300 is received1 ms1
 Scenario: Starting a job with Package Uninstall and Bundle Start steps.Scenario: Starting a job with Package Uninstall and Bundle Start steps2 ms1
 Scenario: Starting job with Bundle Start step and multiple devices.Then I count 20 ms1
 Scenario: Starting job with Bundle Start step and multiple devices.Scenario: Starting job with Bundle Start step and multiple devices0 ms1
 Scenario: Starting job with Bundle Stop step and multiple devices.Then I count 21 ms1
 Scenario: Starting job with Bundle Stop step and multiple devices.Scenario: Starting job with Bundle Stop step and multiple devices2 ms1
 Scenario: Starting job with Package Download/Install step and multiple devices.Then Device status is "DISCONNECTED"3 ms1
 Scenario: Starting job with Package Download/Install step and multiple devices.Scenario: Starting job with Package Download/Install step and multiple devices5 ms1
 Scenario: Starting job with Package Uninstall step and multiple device.Then I count 21 ms1
 Scenario: Starting job with Package Uninstall step and multiple device.Scenario: Starting job with Package Uninstall step and multiple device2 ms1
 Scenario: Starting job with Asset Write step and multiple devices.Then I count 21 ms1
 Scenario: Starting job with Asset Write step and multiple devices.Scenario: Starting job with Asset Write step and multiple devices2 ms1
 Scenario: Starting job with Configuration Put step and multiple devices.Then I count 22 ms1
 Scenario: Starting job with Configuration Put step and multiple devices.Scenario: Starting job with Configuration Put step and multiple devices2 ms1
 Scenario: Starting job with Command Execution step and multiple devices.Then I count 22 ms1
 Scenario: Starting job with Command Execution step and multiple devices.Scenario: Starting job with Command Execution step and multiple devices3 ms1
 Scenario: Starting job with two Bundle Start steps and multiple devices.Then I count 22 ms1
 Scenario: Starting job with two Bundle Start steps and multiple devices.Scenario: Starting job with two Bundle Start steps and multiple devices2 ms1
 Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices.Then I count 22 ms1
 Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices.Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices3 ms1
 Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices.Then Device status is "DISCONNECTED"8 ms1
 Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices.Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices8 ms1
 Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device.Then I count 21 ms1
 Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device.Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device2 ms1
 Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices.Then I count 21 ms1
 Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices.Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices2 ms1
 Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices.Then I count 21 ms1
 Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices.Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices2 ms1
 Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices.Then I count 22 ms1
 Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices.Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices3 ms1
 Scenario: Start broker for all scenarios.Given Start Broker2 ms1
 Scenario: Start broker for all scenarios.Given Start Broker2 ms1
 Scenario: Start broker for all scenarios.Given Start Broker2 ms1
 Scenario: Start broker for all scenarios.Given Start Broker1 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms1
 Scenario: Restarting job with valid Command Execution step two times.When I search for events from device "rpione3" in account "kapua-sys"1 ms1
 Scenario: Restarting job with valid Command Execution step two times.Scenario: Restarting job with valid Command Execution step two times2 ms1
 Scenario: Restarting job with invalid Command Execution step two times.When I search for events from device "rpione3" in account "kapua-sys"1 ms1
 Scenario: Restarting job with invalid Command Execution step two times.Scenario: Restarting job with invalid Command Execution step two times2 ms1
 Scenario: Restarting job with valid Bundle Start step two times.And Bundles are requested1 ms1
 Scenario: Restarting job with valid Bundle Start step two times.Scenario: Restarting job with valid Bundle Start step two times2 ms1
 Scenario: Restarting job with invalid Bundle Start step two times.And Bundles are requested3 ms1
 Scenario: Restarting job with invalid Bundle Start step two times.Scenario: Restarting job with invalid Bundle Start step two times4 ms1
 Scenario: Restarting job with valid Bundle Stop step two times.And Bundles are requested3 ms1
 Scenario: Restarting job with valid Bundle Stop step two times.Scenario: Restarting job with valid Bundle Stop step two times4 ms1
 Scenario: Restarting job with invalid Bundle Stop step two times.And Bundles are requested2 ms1
 Scenario: Restarting job with invalid Bundle Stop step two times.Scenario: Restarting job with invalid Bundle Stop step two times2 ms1
 Scenario: Restarting a job with valid Package Uninstall step two times.And I search for events from device "rpione3" in account "kapua-sys"1 ms1
 Scenario: Restarting a job with valid Package Uninstall step two times.Scenario: Restarting a job with valid Package Uninstall step two times2 ms1
 Scenario: Restarting a job with invalid Package Uninstall step two times.And I search for events from device "rpione3" in account "kapua-sys"2 ms1
 Scenario: Restarting a job with invalid Package Uninstall step two times.Scenario: Restarting a job with invalid Package Uninstall step two times2 ms1
 Scenario: Restarting job with valid Command Execution and Package Install steps two times.And Command pwd is executed2 ms1
 Scenario: Restarting job with valid Command Execution and Package Install steps two times.Scenario: Restarting job with valid Command Execution and Package Install steps two times2 ms1
 Scenario: Restarting job with invalid Command Execution and Package Install step two times.And Command pwd is executed2 ms1
 Scenario: Restarting job with invalid Command Execution and Package Install step two times.Scenario: Restarting job with invalid Command Execution and Package Install step two times3 ms1
 Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times.And Bundles are requested5 ms1
 Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times.Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times7 ms1
 Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times.And Bundles are requested0 ms1
 Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times.Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times0 ms1
 Scenario: Restarting job with valid Command Execution step and multiple devices two times.And Command pwd is executed2 ms1
 Scenario: Restarting job with valid Command Execution step and multiple devices two times.Scenario: Restarting job with valid Command Execution step and multiple devices two times2 ms1
 Scenario: Restarting job with invalid Command Execution step and multiple devices two times.And Command pwd is executed2 ms1
 Scenario: Restarting job with invalid Command Execution step and multiple devices two times.Scenario: Restarting job with invalid Command Execution step and multiple devices two times4 ms1
 Scenario: Restarting job with valid Bundle Start step and multiple devices two times.And Bundles are requested2 ms1
 Scenario: Restarting job with valid Bundle Start step and multiple devices two times.Scenario: Restarting job with valid Bundle Start step and multiple devices two times3 ms1
 Scenario: Restarting job with invalid Bundle Start step and multiple devices two times.And Bundles are requested2 ms1
 Scenario: Restarting job with invalid Bundle Start step and multiple devices two times.Scenario: Restarting job with invalid Bundle Start step and multiple devices two times3 ms1
 Scenario: Restarting job with valid Bundle Stop step and multiple devices two times.And Bundles are requested1 ms1
 Scenario: Restarting job with valid Bundle Stop step and multiple devices two times.Scenario: Restarting job with valid Bundle Stop step and multiple devices two times1 ms1
 Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times.And Bundles are requested2 ms1
 Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times.Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times2 ms1
 Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times.And The type of the last event is "DEPLOY"2 ms1
 Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times.Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times2 ms1
 Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times.And The type of the last event is "DEPLOY"3 ms1
 Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times.Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times3 ms1
 Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times.And Command pwd is executed2 ms1
 Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times.Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times3 ms1
 Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times.And Command pwd is executed2 ms1
 Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times.Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times3 ms1
 Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times.And Bundles are requested2 ms1
 Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times.Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times3 ms1
 Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times.And Bundles are requested1 ms1
 Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times.Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times2 ms1
 Scenario: Restarting a job with valid Configuration Put step two times.Then Configuration is requested1 ms1
 Scenario: Restarting a job with valid Configuration Put step two times.Scenario: Restarting a job with valid Configuration Put step two times2 ms1
 Scenario: Restarting a job with invalid Configuration Put step two times.Then Configuration is requested1 ms1
 Scenario: Restarting a job with invalid Configuration Put step two times.Scenario: Restarting a job with invalid Configuration Put step two times2 ms1
 Scenario: Restarting a job with valid Package Install step two times.When I search for events from device "rpione3" in account "kapua-sys"1 ms1
 Scenario: Restarting a job with valid Package Install step two times.Scenario: Restarting a job with valid Package Install step two times2 ms1
 Scenario: Restarting a job with invalid Package Install step two times.When I search for events from device "rpione3" in account "kapua-sys"1 ms1
 Scenario: Restarting a job with invalid Package Install step two times.Scenario: Restarting a job with invalid Package Install step two times2 ms1
 Scenario: Restarting job With valid Asset Write step two times.And Device assets are requested3 ms1
 Scenario: Restarting job With valid Asset Write step two times.Scenario: Restarting job With valid Asset Write step two times3 ms1
 Scenario: Restarting job with invalid Asset Write step two times.And Device assets are requested1 ms1
 Scenario: Restarting job with invalid Asset Write step two times.Scenario: Restarting job with invalid Asset Write step two times2 ms1
 Scenario: Restarting job with valid Configuration Put and Command Execution steps two times.Then Configuration is requested8 ms1
 Scenario: Restarting job with valid Configuration Put and Command Execution steps two times.Scenario: Restarting job with valid Configuration Put and Command Execution steps two times8 ms1
 Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times.Then Configuration is requested2 ms1
 Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times.Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times2 ms1
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times.And Device assets are requested2 ms1
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times.Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times3 ms1
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times.And Device assets are requested1 ms1
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times.Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times4 ms1
 Scenario: Restarting a job with valid Configuration Put step and multiple devices two times.Then Configuration is requested2 ms1
 Scenario: Restarting a job with valid Configuration Put step and multiple devices two times.Scenario: Restarting a job with valid Configuration Put step and multiple devices two times3 ms1
 Scenario: Restarting a job with invalid Configuration Put and multiple devices two times.Then Configuration is requested2 ms1
 Scenario: Restarting a job with invalid Configuration Put and multiple devices two times.Scenario: Restarting a job with invalid Configuration Put and multiple devices two times3 ms1
 Scenario: Restarting a job with valid Package Install step and multiple devices two times.And I restart a job2 ms1
 Scenario: Restarting a job with valid Package Install step and multiple devices two times.Scenario: Restarting a job with valid Package Install step and multiple devices two times3 ms1
 Scenario: Restarting a job with invalid Package Install step and multiple devices two times.And A new job target item2 ms1
 Scenario: Restarting a job with invalid Package Install step and multiple devices two times.Scenario: Restarting a job with invalid Package Install step and multiple devices two times3 ms1
 Scenario: Restarting job with valid Asset Write step and multiple devices two times.And Device assets are requested1 ms1
 Scenario: Restarting job with valid Asset Write step and multiple devices two times.Scenario: Restarting job with valid Asset Write step and multiple devices two times2 ms1
 Scenario: Restarting job With invalid Asset Write and multiple two times.And Device assets are requested2 ms1
 Scenario: Restarting job With invalid Asset Write and multiple two times.Scenario: Restarting job With invalid Asset Write and multiple two times3 ms1
 Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times.Then Configuration is requested1 ms1
 Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times.Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times2 ms1
 Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times.Then Configuration is requested1 ms1
 Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times.Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times2 ms1
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times.And Device assets are requested7 ms1
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times.Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times9 ms1
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times.And Device assets are requested1 ms1
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times.Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times2 ms1
 Scenario: Starting a job with valid Command Execution step.When I search for events from device "rpione3" in account "kapua-sys"1 ms1
 Scenario: Starting a job with valid Command Execution step.Scenario: Starting a job with valid Command Execution step2 ms1
 Scenario: Starting a job with invalid Command Execution step.When I search for events from device "rpione3" in account "kapua-sys"1 ms1
 Scenario: Starting a job with invalid Command Execution step.Scenario: Starting a job with invalid Command Execution step2 ms1
 Scenario: Starting a job with valid Bundle Start step.And Bundles are requested2 ms1
 Scenario: Starting a job with valid Bundle Start step.Scenario: Starting a job with valid Bundle Start step2 ms1
 Scenario: Starting a job with invalid Bundle Start step.And Bundles are requested1 ms1
 Scenario: Starting a job with invalid Bundle Start step.Scenario: Starting a job with invalid Bundle Start step2 ms1
 Scenario: Starting a job with valid Bundle Stop step.And Bundles are requested2 ms1
 Scenario: Starting a job with valid Bundle Stop step.Scenario: Starting a job with valid Bundle Stop step3 ms1
 Scenario: Starting a job with invalid Bundle Stop step.And Bundles are requested2 ms1
 Scenario: Starting a job with invalid Bundle Stop step.Scenario: Starting a job with invalid Bundle Stop step2 ms1
 Scenario: Starting a job with valid Configuration Put step.When Configuration is requested2 ms1
 Scenario: Starting a job with valid Configuration Put step.Scenario: Starting a job with valid Configuration Put step2 ms1
 Scenario: Starting a job with invalid Configuration Put step.When Configuration is requested1 ms1
 Scenario: Starting a job with invalid Configuration Put step.Scenario: Starting a job with invalid Configuration Put step2 ms1
 Scenario: Starting a job with valid Package Install step.When I search for events from device "rpione3" in account "kapua-sys"2 ms1
 Scenario: Starting a job with valid Package Install step.Scenario: Starting a job with valid Package Install step2 ms1
 Scenario: Starting a job with invalid Package Install step.When I search for events from device "rpione3" in account "kapua-sys"1 ms1
 Scenario: Starting a job with invalid Package Install step.Scenario: Starting a job with invalid Package Install step2 ms1
 Scenario: Starting a job with valid Asset Write step.When Device assets are requested1 ms1
 Scenario: Starting a job with valid Asset Write step.Scenario: Starting a job with valid Asset Write step2 ms1
 Scenario: Starting a job with invalid Asset Write step.And Device assets are requested2 ms1
 Scenario: Starting a job with invalid Asset Write step.Scenario: Starting a job with invalid Asset Write step2 ms1
 Scenario: Starting a job with valid Package Uninstall step.When I search for events from device "rpione3" in account "kapua-sys"2 ms1
 Scenario: Starting a job with valid Package Uninstall step.Scenario: Starting a job with valid Package Uninstall step3 ms1
 Scenario: Starting a job with invalid Package Uninstall step.When I search for events from device "rpione3" in account "kapua-sys"2 ms1
 Scenario: Starting a job with invalid Package Uninstall step.Scenario: Starting a job with invalid Package Uninstall step2 ms1
 Scenario: Starting job with valid Command Execution and Package Install steps.And Command "pwd" is executed1 ms1
 Scenario: Starting job with valid Command Execution and Package Install steps.Scenario: Starting job with valid Command Execution and Package Install steps2 ms1
 Scenario: Starting job with invalid Command Execution and Package Install steps.And Command "pwd" is executed2 ms1
 Scenario: Starting job with invalid Command Execution and Package Install steps.Scenario: Starting job with invalid Command Execution and Package Install steps2 ms1
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps.And Bundles are requested0 ms1
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps.Scenario: Starting a job with valid Bundle Start and Bundle Stop steps0 ms1
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps.And Bundles are requested2 ms1
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps.Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps2 ms1
 Scenario: Starting job with valid Configuration Put and Command Execution steps.And Configuration is requested1 ms1
 Scenario: Starting job with valid Configuration Put and Command Execution steps.Scenario: Starting job with valid Configuration Put and Command Execution steps2 ms1
 Scenario: Starting job with invalid Configuration Put and Command Execution steps.Then Configuration is requested2 ms1
 Scenario: Starting job with invalid Configuration Put and Command Execution steps.Scenario: Starting job with invalid Configuration Put and Command Execution steps3 ms1
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps.When Device assets are requested2 ms1
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps.Scenario: Starting a job with valid Package Uninstall and Asset Write steps3 ms1
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps.When Device assets are requested2 ms1
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps.Scenario: Starting a job with invalid Package Uninstall and Asset Write steps2 ms1
 Scenario: Starting job with valid Command Execution step and multiple devices.And Command "pwd" is executed2 ms1
 Scenario: Starting job with valid Command Execution step and multiple devices.Scenario: Starting job with valid Command Execution step and multiple devices3 ms1
 Scenario: Starting job with invalid Command Execution step and multiple devices.And Command "pwd" is executed2 ms1
 Scenario: Starting job with invalid Command Execution step and multiple devices.Scenario: Starting job with invalid Command Execution step and multiple devices2 ms1
 Scenario: Starting job with valid Bundle Start step and multiple devices.And Bundles are requested1 ms1
 Scenario: Starting job with valid Bundle Start step and multiple devices.Scenario: Starting job with valid Bundle Start step and multiple devices2 ms1
 Scenario: Starting job with invalid Bundle Start step and multiple devices.And Bundles are requested1 ms1
 Scenario: Starting job with invalid Bundle Start step and multiple devices.Scenario: Starting job with invalid Bundle Start step and multiple devices2 ms1
 Scenario: Starting a job with valid Bundle Stop step and multiple devices.And Bundles are requested2 ms1
 Scenario: Starting a job with valid Bundle Stop step and multiple devices.Scenario: Starting a job with valid Bundle Stop step and multiple devices3 ms1
 Scenario: Starting a job with invalid Bundle Stop step and multiple devices.And Bundles are requested2 ms1
 Scenario: Starting a job with invalid Bundle Stop step and multiple devices.Scenario: Starting a job with invalid Bundle Stop step and multiple devices11 ms1
 Scenario: Starting a job with valid Configuration Put step and multiple devices.Then Configuration is requested2 ms1
 Scenario: Starting a job with valid Configuration Put step and multiple devices.Scenario: Starting a job with valid Configuration Put step and multiple devices3 ms1
 Scenario: Starting a job with invalid Configuration Put step and multiple devices.Then Configuration is requested1 ms1
 Scenario: Starting a job with invalid Configuration Put step and multiple devices.Scenario: Starting a job with invalid Configuration Put step and multiple devices2 ms1
 Scenario: Starting a job with valid Asset Write step and multiple targets.And Device assets are requested2 ms1
 Scenario: Starting a job with valid Asset Write step and multiple targets.Scenario: Starting a job with valid Asset Write step and multiple targets3 ms1
 Scenario: Starting a job with invalid Asset Write step and multiple targets.And Device assets are requested1 ms1
 Scenario: Starting a job with invalid Asset Write step and multiple targets.Scenario: Starting a job with invalid Asset Write step and multiple targets2 ms1
 Scenario: Starting a job with valid Package Uninstall step and multiple targets.And I start a job2 ms1
 Scenario: Starting a job with valid Package Uninstall step and multiple targets.Scenario: Starting a job with valid Package Uninstall step and multiple targets3 ms1
 Scenario: Starting a job with invalid Package Uninstall step and multiple targets.And I start a job2 ms1
 Scenario: Starting a job with invalid Package Uninstall step and multiple targets.Scenario: Starting a job with invalid Package Uninstall step and multiple targets5 ms1
 Scenario: Starting a job with valid Package Install step and multiple devices.And I start a job2 ms1
 Scenario: Starting a job with valid Package Install step and multiple devices.Scenario: Starting a job with valid Package Install step and multiple devices11 ms1
 Scenario: Starting a job with invalid Package Install step and multiple devices.And I start a job3 ms1
 Scenario: Starting a job with invalid Package Install step and multiple devices.Scenario: Starting a job with invalid Package Install step and multiple devices4 ms1
 Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices.And Command "pwd" is executed2 ms1
 Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices.Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices3 ms1
 Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices.And Command "pwd" is executed1 ms1
 Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices.Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices2 ms1
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices.And Bundles are requested2 ms1
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices.Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices3 ms1
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices.And Bundles are requested1 ms1
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices.Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices2 ms1
 Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices.Then Configuration is requested2 ms1
 Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices.Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices2 ms1
 Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices.Then Configuration is requested1 ms1
 Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices.Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices2 ms1
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices.And Device assets are requested2 ms1
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices.Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices2 ms1
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices.And Device assets are requested1 ms1
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices.Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices2 ms1
 Scenario: Stop job with multiple Bundle Start and Package Install steps and one target.And Bundles are requested2 ms1
 Scenario: Stop job with multiple Bundle Start and Package Install steps and one target.Scenario: Stop job with multiple Bundle Start and Package Install steps and one target2 ms1
 Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target.And Bundles are requested2 ms1
 Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target.Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target2 ms1
 Scenario: Stop job with multiple Command Execution and Package Install steps and one target.And Command pwd is executed1 ms1
 Scenario: Stop job with multiple Command Execution and Package Install steps and one target.Scenario: Stop job with multiple Command Execution and Package Install steps and one target2 ms1
 Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target.And Configuration is requested1 ms1
 Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target.Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target2 ms1
 Scenario: Stop job with multiple Asset Write and Package Install steps and one target.When Device assets are requested1 ms1
 Scenario: Stop job with multiple Asset Write and Package Install steps and one target.Scenario: Stop job with multiple Asset Write and Package Install steps and one target2 ms1
 Scenario: Stop job with multiple targets and Bundle Start and Package Install steps.And Bundles are requested1 ms1
 Scenario: Stop job with multiple targets and Bundle Start and Package Install steps.Scenario: Stop job with multiple targets and Bundle Start and Package Install steps2 ms1
 Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps.And Bundles are requested1 ms1
 Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps.Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps2 ms1
 Scenario: Stop job with multiple targets and Command Execution and Package Install steps.And Command pwd is executed1 ms1
 Scenario: Stop job with multiple targets and Command Execution and Package Install steps.Scenario: Stop job with multiple targets and Command Execution and Package Install steps2 ms1
 Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps.And Configuration is requested1 ms1
 Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps.Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps2 ms1
 Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target.When Device assets are requested1 ms1
 Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target.Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target2 ms1
 Scenario: Start broker for all scenarios.Given Start Broker5 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios5 ms1
 Scenario: Executing Job When Device Connected After The Specified Start Date And Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms1
 Scenario: Executing Job When Device Connected After The Specified Start Date And Time.Scenario: Executing Job When Device Connected After The Specified Start Date And Time2 ms1
 Scenario: Executing Job When Device Connected Before The Specified Start Date And Time.When I search for events from device "rpione3" in account "kapua-sys"2 ms1
 Scenario: Executing Job When Device Connected Before The Specified Start Date And Time.Scenario: Executing Job When Device Connected Before The Specified Start Date And Time3 ms1
 Scenario: Executing Job When Device Connected Before End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"2 ms1
 Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time2 ms1
 Scenario: Executing Job When Device Connected After End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"3 ms1
 Scenario: Executing Job When Device Connected After End Date And Time.Scenario: Executing Job When Device Connected After End Date And Time4 ms1
 Scenario: Executing Job And Then Restarting Device.When I search for events from device "rpione3" in account "kapua-sys"1 ms1
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device2 ms1
 Scenario: Executing Job Without Steps.When I search for events from device "rpione3" in account "kapua-sys"2 ms1
 Scenario: Executing Job Without Steps.Scenario: Executing Job Without Steps2 ms1
 Scenario: Start broker for all scenarios.Given Start Broker1 ms1
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms1

All Tests

PackageDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
(root)9.3 sec452+4523672+36727108+710811232+11232
org.eclipse.kapua78 ms0033
org.eclipse.kapua.broker.core.plugin3.3 sec0015+1515+15
org.eclipse.kapua.client.gateway55 ms0043+4343+43
org.eclipse.kapua.client.gateway.kura0.17 sec0014+1414+14
org.eclipse.kapua.client.gateway.spi.util2.7 sec0015+1515+15
org.eclipse.kapua.client.gateway.util2 ms003+33+3
org.eclipse.kapua.commons.about0.32 sec0011
org.eclipse.kapua.commons.configuration57 ms0011
org.eclipse.kapua.commons.configuration.metatype13 ms001919
org.eclipse.kapua.commons.liquibase0.7 sec0044
org.eclipse.kapua.commons.metric4 ms0022
org.eclipse.kapua.commons.model0.13 sec0088
org.eclipse.kapua.commons.model.id4 ms0011
org.eclipse.kapua.commons.security2.6 sec0033
org.eclipse.kapua.commons.setting0 ms0044
org.eclipse.kapua.commons.util38 ms003838
org.eclipse.kapua.commons.util.xml0.23 sec0099
org.eclipse.kapua.integration.service.datastoreJunit0 ms05+505+5
org.eclipse.kapua.kura.simulator.main.simulation5.3 sec0013+1313+13
org.eclipse.kapua.locator.internal0.16 sec021012
org.eclipse.kapua.message.internal0.33 sec022628
org.eclipse.kapua.message.internal.device.data0 ms0033
org.eclipse.kapua.message.internal.device.lifecycle53 ms002121
org.eclipse.kapua.message.internal.xml0.9 sec001111
org.eclipse.kapua.service.datastore.test.junit0.18 sec004+44+4
org.eclipse.kapua.service.datastore.test.junit.client0.29 sec007+77+7
org.eclipse.kapua.service.datastore.test.junit.clientTransport80 ms03+319+1922+22
org.eclipse.kapua.service.device.management.commons.message.notification7 ms002+22+2