Test Result

530 failures (±0) , 5,302 skipped (±0)
16,552 tests (±0)
Took 1 hr 22 min.

All Failed Tests

Test NameDurationAge
 Scenario: Starting a job with Package Install step.Then Device status is "DISCONNECTED"0 ms1
 Scenario: Starting job with Package Download/Install step and multiple devices.Then Device status is "DISCONNECTED"2 ms1
 Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices.Then Device status is "DISCONNECTED"1 ms1
 Scenario: Execute possible docker steps to show its usage.Given List images by name "kapua/kapua-broker:1.2.0-SNAPSHOT"2 ms2
 Scenario: Execute possible docker steps to show its usage.Scenario: Execute possible docker steps to show its usage4 ms2
 Scenario: Start broker for all scenarios.Given Start Broker1 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms2
 Scenario: Test LOOSE user coupling on single connection.Scenario: Test LOOSE user coupling on single connection4 ms2
 Scenario: New connection with reserved ID.Scenario: New connection with reserved ID0 ms2
 Scenario: Test STRICT user coupling on single connection.Scenario: Test STRICT user coupling on single connection3 ms2
 Scenario: Test STRICT user coupling with user change allowed on single connection.Scenario: Test STRICT user coupling with user change allowed on single connection0 ms2
 Scenario: Test LOOSE user coupling with 3 connections.Scenario: Test LOOSE user coupling with 3 connections4 ms2
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.Scenario: Test STRICT user coupling with 3 connections and a reserved user3 ms2
 Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode.Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode4 ms2
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode.Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode4 ms2
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices.Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices4 ms2
 Scenario: List Endpoints From "kapua-sys" Account.Scenario: List Endpoints From "kapua-sys" Account2 ms2
 Scenario: List Endpoints From Sub-account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms2
 Scenario: List Endpoints From Sub-account.Scenario: List Endpoints From Sub-account4 ms2
 Scenario: List Endpoints Created From Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22224 ms2
 Scenario: List Endpoints Created From Sub-Account.Scenario: List Endpoints Created From Sub-Account5 ms2
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22221 ms2
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.Scenario: List Endpoints From Sub-Account Of Another Sub-Account2 ms2
 Scenario: Start broker for all scenarios.Given Start Broker1 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms5
 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"1 ms5
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric2 ms5
 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 ms5
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics1 ms5
 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 ms5
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics1 ms5
 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 ms5
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters1 ms5
 Scenario: Start broker for all scenarios.Given Start Broker2 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms5
 Scenario: Start broker for all scenarios.Given Start Broker1 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms5
 Scenario: Start broker for all scenarios.Given Start Broker2 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms5
 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"1 ms5
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric2 ms5
 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"3 ms5
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics3 ms5
 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"2 ms5
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics2 ms5
 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 ms5
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters2 ms5
 Scenario: Start broker for all scenarios.Given Start Broker1 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms5
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Given Mqtt Device is started12 ms5
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed12 ms5
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started3 ms5
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY5 ms5
 Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started3 ms5
 Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY7 ms5
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started4 ms5
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account5 ms5
 Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Given Mqtt Device is started4 ms5
 Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Scenario: DM5 Data manage publish to CTRL_ACC is not allowed5 ms5
 Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started7 ms5
 Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed.Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed9 ms5
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Given Mqtt Device is started4 ms5
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed6 ms5
 Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started3 ms5
 Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI6 ms5
 Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Given Mqtt Device is started3 ms5
 Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC5 ms5
 Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started2 ms5
 Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI4 ms5
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started4 ms5
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms5
 Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started2 ms5
 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 allowed4 ms5
 Scenario: Start broker for all scenarios.Given Start Broker13 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios13 ms5
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Given Mqtt Device is started6 ms5
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic8 ms5
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Given Mqtt Device is started12 ms5
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY12 ms5
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started5 ms5
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY7 ms5
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started7 ms5
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY9 ms5
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started6 ms5
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account6 ms5
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.Given Mqtt Device is started3 ms5
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.Scenario: B5 Broker publish to CTRL_ACC is not allowed5 ms5
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started4 ms5
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed5 ms5
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Given Mqtt Device is started5 ms5
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed5 ms5
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started5 ms5
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI8 ms5
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started4 ms5
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed5 ms5
 Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.Given Mqtt Device is started8 ms5
 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 allowed8 ms5
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Given Mqtt Device is started7 ms5
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed8 ms5
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started6 ms5
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI8 ms5
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started3 ms5
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms5
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started3 ms5
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed16 ms5
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Given Mqtt Device is started6 ms5
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY8 ms5
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started6 ms5
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY8 ms5
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started6 ms5
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY7 ms5
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started4 ms5
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account5 ms5
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Given Mqtt Device is started2 ms5
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Scenario: D5 Device subscribe - publish - admin on CTRL_ACC4 ms5
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started3 ms5
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI8 ms5
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started2 ms5
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed7 ms5
 Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.Given Mqtt Device is started3 ms5
 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 ms5
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Given Mqtt Device is started4 ms5
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed6 ms5
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started3 ms5
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI6 ms5
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started6 ms5
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed7 ms5
 Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started2 ms5
 Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed5 ms5
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Given Mqtt Device is started3 ms5
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY4 ms5
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started2 ms5
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY4 ms5
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started3 ms5
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY5 ms5
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started5 ms5
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account6 ms5
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Given Mqtt Device is started6 ms5
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Scenario: DV5 Data view publish to CTRL_ACC is not allowed7 ms5
 Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started2 ms5
 Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed.Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed4 ms5
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Given Mqtt Device is started3 ms5
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed5 ms5
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started6 ms5
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI8 ms5
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started2 ms5
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed4 ms5
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Given Mqtt Device is started4 ms5
 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 allowed6 ms5
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Given Mqtt Device is started2 ms5
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed3 ms5
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Given Mqtt Device is started3 ms5
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed4 ms5
 Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed.Given Mqtt Device is started6 ms5
 Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed.Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed7 ms5
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started9 ms5
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed9 ms5
 Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started3 ms5
 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 allowed4 ms5
 Scenario: Start broker for all scenarios.Given Start Broker1 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms5
 Scenario: Send BIRTH message and then DC message.And I login as user with name "kapua-sys" and password "kapua-password"4 ms5
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message6 ms5
 Scenario: Start broker for all scenarios.Given Start Broker1 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms5
 Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Then Device is connected with "localhost" server ip1 ms5
 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 file2 ms5
 Scenario: Start broker for all scenarios.Given Start Broker1 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms5
 Scenario: Send BIRTH message and then DC message while broker ip is set by System.Then Device is connected with "localhost" server ip5 ms5
 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 System7 ms5
 Scenario: Start broker for all scenarios.Given Start Broker1 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms5
 Scenario: Start broker for all scenarios.Given Start Broker3 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms5
 Scenario: Stealing link scenario.Scenario: Stealing link scenario8 ms5
 Scenario: Start broker for all scenarios.Given Start Broker5 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios6 ms5
 Scenario: Connect to the system and publish some data.Then Device sim-1 for account kapua-sys is registered after 5 seconds6 ms5
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data7 ms5
 Scenario: Start broker for all scenarios.Given Start Broker1 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms5
 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 ms5
 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 status4 ms5
 Scenario: Installing a package.Then Device sim-1 for account kapua-sys is registered after 5 seconds1 ms5
 Scenario: Installing a package.Scenario: Installing a package1 ms5
 Scenario: Start broker for all scenarios.Given Start Broker1 ms5
 Scenario: Start broker for all scenarios.Given Start Broker1 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms5
 Scenario: Restarting job with Command Execution step.Scenario: Restarting job with Command Execution step2 ms5
 Scenario: Restarting job with Asset Write step.Scenario: Restarting job with Asset Write step2 ms5
 Scenario: Restarting job with Configuration Put step.Scenario: Restarting job with Configuration Put step2 ms5
 Scenario: Restarting job with Bundle Start step.Scenario: Restarting job with Bundle Start step2 ms5
 Scenario: Restarting job with Bundle Stop step.Scenario: Restarting job with Bundle Stop step2 ms5
 Scenario: Restarting job with Package Install step.Scenario: Restarting job with Package Install step1 ms5
 Scenario: Restarting job with Package Uninstall step.Scenario: Restarting job with Package Uninstall step2 ms5
 Scenario: Restarting job with two Bundle Start steps.Scenario: Restarting job with two Bundle Start steps3 ms5
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.Scenario: Restarting job with Bundle Stop and Bundle Start steps3 ms5
 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 devices2 ms5
 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 devices2 ms5
 Scenario: Restarting a job with Package Uninstall and Bundle Start steps.Scenario: Restarting a job with Package Uninstall and Bundle Start steps2 ms5
 Scenario: Restarting a job with Command Execution and Bundle Start steps.Scenario: Restarting a job with Command Execution and Bundle Start steps2 ms5
 Scenario: Restarting a job with Asset Write and Bundle Start steps.Scenario: Restarting a job with Asset Write and Bundle Start steps2 ms5
 Scenario: Restarting a job with Configuration Put and Bundle Start steps.Scenario: Restarting a job with Configuration Put and Bundle Start steps2 ms5
 Scenario: Restarting job with Bundle Start step and multiple devices.Then I count 22 ms5
 Scenario: Restarting job with Bundle Start step and multiple devices.Scenario: Restarting job with Bundle Start step and multiple devices2 ms5
 Scenario: Restarting job with Bundle Stop step and multiple devices.Then I count 22 ms5
 Scenario: Restarting job with Bundle Stop step and multiple devices.Scenario: Restarting job with Bundle Stop step and multiple devices4 ms5
 Scenario: Restarting job with Package Download/Install step and multiple devices.Then I count 21 ms5
 Scenario: Restarting job with Package Download/Install step and multiple devices.Scenario: Restarting job with Package Download/Install step and multiple devices2 ms5
 Scenario: Restarting job with Package Uninstall step and multiple device.Then I count 22 ms5
 Scenario: Restarting job with Package Uninstall step and multiple device.Scenario: Restarting job with Package Uninstall step and multiple device3 ms5
 Scenario: Restarting job with Asset Write step and multiple devices.Then I count 21 ms5
 Scenario: Restarting job with Asset Write step and multiple devices.Scenario: Restarting job with Asset Write step and multiple devices2 ms5
 Scenario: Restarting job with Configuration Put step and multiple devices.Then I count 21 ms5
 Scenario: Restarting job with Configuration Put step and multiple devices.Scenario: Restarting job with Configuration Put step and multiple devices2 ms5
 Scenario: Restarting job with Command Execution step and multiple devices.Then I count 22 ms5
 Scenario: Restarting job with Command Execution step and multiple devices.Scenario: Restarting job with Command Execution step and multiple devices2 ms5
 Scenario: Restarting job with two Bundle Start steps and multiple devices.Then I count 22 ms5
 Scenario: Restarting job with two Bundle Start steps and multiple devices.Scenario: Restarting job with two Bundle Start steps and multiple devices2 ms5
 Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices.Then I count 21 ms5
 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 ms5
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.Then I count 21 ms5
 Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device.Then I count 22 ms5
 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 device2 ms5
 Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices.Then I count 22 ms5
 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 devices2 ms5
 Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices.Then I count 21 ms5
 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 ms5
 Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices.Then I count 22 ms5
 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 devices3 ms5
 Scenario: Starting a job with Command Execution step.Scenario: Starting a job with Command Execution step2 ms5
 Scenario: Starting a job with Asset Write step.Scenario: Starting a job with Asset Write step1 ms5
 Scenario: Starting a job with Bundle Start step.Scenario: Starting a job with Bundle Start step3 ms5
 Scenario: Starting a job with Bundle Stop step.Scenario: Starting a job with Bundle Stop step2 ms5
 Scenario: Starting a job with Configuration Put step.Scenario: Starting a job with Configuration Put step2 ms5
 Scenario: Starting a job with Package Install step.Scenario: Starting a job with Package Install step0 ms5
 Scenario: Starting a job with Package Uninstall step.And Package named org.eclipse.kura.example.beacon with version 1.0.300 is received27 ms5
 Scenario: Starting a job with Package Uninstall step.Scenario: Starting a job with Package Uninstall step28 ms5
 Scenario: Starting a job with Command Execution and Bundle Start steps.Scenario: Starting a job with Command Execution and Bundle Start steps3 ms5
 Scenario: Starting a job with Asset Write and Bundle Start steps.Scenario: Starting a job with Asset Write and Bundle Start steps2 ms5
 Scenario: Starting a job with two Bundle Start steps.Scenario: Starting a job with two Bundle Start steps2 ms5
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.Scenario: Starting a job with Bundle Stop and Bundle Start steps2 ms5
 Scenario: Starting a job with Configuration Put and Bundle Start steps.Scenario: Starting a job with Configuration Put and Bundle Start steps3 ms5
 Scenario: Starting a job with Package Install and Bundle Start steps.Scenario: Starting a job with Package Install and Bundle Start steps2 ms5
 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 ms5
 Scenario: Starting a job with Package Uninstall and Bundle Start steps.Scenario: Starting a job with Package Uninstall and Bundle Start steps2 ms5
 Scenario: Starting job with Bundle Start step and multiple devices.Then I count 21 ms5
 Scenario: Starting job with Bundle Start step and multiple devices.Scenario: Starting job with Bundle Start step and multiple devices2 ms5
 Scenario: Starting job with Bundle Stop step and multiple devices.Then I count 22 ms5
 Scenario: Starting job with Bundle Stop step and multiple devices.Scenario: Starting job with Bundle Stop step and multiple devices2 ms5
 Scenario: Starting job with Package Download/Install step and multiple devices.Scenario: Starting job with Package Download/Install step and multiple devices3 ms5
 Scenario: Starting job with Package Uninstall step and multiple device.Then I count 21 ms5
 Scenario: Starting job with Package Uninstall step and multiple device.Scenario: Starting job with Package Uninstall step and multiple device2 ms5
 Scenario: Starting job with Asset Write step and multiple devices.Then I count 21 ms5
 Scenario: Starting job with Asset Write step and multiple devices.Scenario: Starting job with Asset Write step and multiple devices1 ms5
 Scenario: Starting job with Configuration Put step and multiple devices.Then I count 21 ms5
 Scenario: Starting job with Configuration Put step and multiple devices.Scenario: Starting job with Configuration Put step and multiple devices2 ms5
 Scenario: Starting job with Command Execution step and multiple devices.Then I count 21 ms5
 Scenario: Starting job with Command Execution step and multiple devices.Scenario: Starting job with Command Execution step and multiple devices5 ms5
 Scenario: Starting job with two Bundle Start steps and multiple devices.Then I count 20 ms5
 Scenario: Starting job with two Bundle Start steps and multiple devices.Scenario: Starting job with two Bundle Start steps and multiple devices0 ms5
 Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices.Then I count 21 ms5
 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 devices2 ms5
 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 devices2 ms5
 Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device.Then I count 21 ms5
 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 device1 ms5
 Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices.Then I count 21 ms5
 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 ms5
 Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices.Then I count 22 ms5
 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 ms5
 Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices.Then I count 21 ms5
 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 devices2 ms5
 Scenario: Start broker for all scenarios.Given Start Broker1 ms5
 Scenario: Start broker for all scenarios.Given Start Broker2 ms5
 Scenario: Start broker for all scenarios.Given Start Broker1 ms5
 Scenario: Start broker for all scenarios.Given Start Broker1 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms5
 Scenario: Restarting job with valid Command Execution step two times.Scenario: Restarting job with valid Command Execution step two times2 ms5
 Scenario: Restarting job with invalid Command Execution step two times.Scenario: Restarting job with invalid Command Execution step two times2 ms5
 Scenario: Restarting job with valid Bundle Start step two times.And Bundles are requested3 ms5
 Scenario: Restarting job with valid Bundle Start step two times.Scenario: Restarting job with valid Bundle Start step two times3 ms5
 Scenario: Restarting job with invalid Bundle Start step two times.And Bundles are requested2 ms5
 Scenario: Restarting job with invalid Bundle Start step two times.Scenario: Restarting job with invalid Bundle Start step two times3 ms5
 Scenario: Restarting job with valid Bundle Stop step two times.And Bundles are requested1 ms5
 Scenario: Restarting job with valid Bundle Stop step two times.Scenario: Restarting job with valid Bundle Stop step two times2 ms5
 Scenario: Restarting job with invalid Bundle Stop step two times.And Bundles are requested2 ms5
 Scenario: Restarting job with invalid Bundle Stop step two times.Scenario: Restarting job with invalid Bundle Stop step two times3 ms5
 Scenario: Restarting a job with valid Package Uninstall step two times.Scenario: Restarting a job with valid Package Uninstall step two times2 ms5
 Scenario: Restarting a job with invalid Package Uninstall step two times.Scenario: Restarting a job with invalid Package Uninstall step two times2 ms5
 Scenario: Restarting job with valid Command Execution and Package Install steps two times.And Command pwd is executed1 ms5
 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 ms5
 Scenario: Restarting job with invalid Command Execution and Package Install step two times.And Command pwd is executed2 ms5
 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 times2 ms5
 Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times.And Bundles are requested1 ms5
 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 times2 ms5
 Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times.And Bundles are requested1 ms5
 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 times2 ms5
 Scenario: Restarting job with valid Command Execution step and multiple devices two times.And Command pwd is executed2 ms5
 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 ms5
 Scenario: Restarting job with invalid Command Execution step and multiple devices two times.And Command pwd is executed1 ms5
 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 times2 ms5
 Scenario: Restarting job with valid Bundle Start step and multiple devices two times.And Bundles are requested1 ms5
 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 times2 ms5
 Scenario: Restarting job with invalid Bundle Start step and multiple devices two times.And Bundles are requested2 ms5
 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 times2 ms5
 Scenario: Restarting job with valid Bundle Stop step and multiple devices two times.And Bundles are requested2 ms5
 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 times3 ms5
 Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times.And Bundles are requested3 ms5
 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 times3 ms5
 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 ms5
 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 ms5
 Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times.And Command pwd is executed2 ms5
 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 times2 ms5
 Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times.And Command pwd is executed2 ms5
 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 times2 ms5
 Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times.And Bundles are requested4 ms5
 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 times4 ms5
 Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times.And Bundles are requested2 ms5
 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 times3 ms5
 Scenario: Restarting a job with valid Configuration Put step two times.Scenario: Restarting a job with valid Configuration Put step two times2 ms5
 Scenario: Restarting a job with invalid Configuration Put step two times.Scenario: Restarting a job with invalid Configuration Put step two times2 ms5
 Scenario: Restarting a job with valid Package Install step two times.Scenario: Restarting a job with valid Package Install step two times2 ms5
 Scenario: Restarting a job with invalid Package Install step two times.Scenario: Restarting a job with invalid Package Install step two times2 ms5
 Scenario: Restarting job With valid Asset Write step two times.Scenario: Restarting job With valid Asset Write step two times2 ms5
 Scenario: Restarting job with invalid Asset Write step two times.Scenario: Restarting job with invalid Asset Write step two times4 ms5
 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 times2 ms5
 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 ms5
 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 times2 ms5
 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 times1 ms5
 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 ms5
 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 times2 ms5
 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 times9 ms5
 Scenario: Restarting a job with invalid Package Install step and multiple devices two times.And A new job target item0 ms5
 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 times0 ms5
 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 times1 ms5
 Scenario: Restarting job With invalid Asset Write and multiple two times.Scenario: Restarting job With invalid Asset Write and multiple two times2 ms5
 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 times3 ms5
 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 times4 ms5
 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 times2 ms5
 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 ms5
 Scenario: Starting a job with valid Command Execution step.Scenario: Starting a job with valid Command Execution step2 ms5
 Scenario: Starting a job with invalid Command Execution step.Scenario: Starting a job with invalid Command Execution step2 ms5
 Scenario: Starting a job with valid Bundle Start step.And Bundles are requested2 ms5
 Scenario: Starting a job with valid Bundle Start step.Scenario: Starting a job with valid Bundle Start step2 ms5
 Scenario: Starting a job with invalid Bundle Start step.And Bundles are requested3 ms5
 Scenario: Starting a job with invalid Bundle Start step.Scenario: Starting a job with invalid Bundle Start step4 ms5
 Scenario: Starting a job with valid Bundle Stop step.And Bundles are requested1 ms5
 Scenario: Starting a job with valid Bundle Stop step.Scenario: Starting a job with valid Bundle Stop step2 ms5
 Scenario: Starting a job with invalid Bundle Stop step.And Bundles are requested2 ms5
 Scenario: Starting a job with invalid Bundle Stop step.Scenario: Starting a job with invalid Bundle Stop step2 ms5
 Scenario: Starting a job with valid Configuration Put step.When Configuration is requested2 ms5
 Scenario: Starting a job with valid Configuration Put step.Scenario: Starting a job with valid Configuration Put step3 ms5
 Scenario: Starting a job with invalid Configuration Put step.When Configuration is requested1 ms5
 Scenario: Starting a job with invalid Configuration Put step.Scenario: Starting a job with invalid Configuration Put step2 ms5
 Scenario: Starting a job with valid Package Install step.Scenario: Starting a job with valid Package Install step2 ms5
 Scenario: Starting a job with invalid Package Install step.Scenario: Starting a job with invalid Package Install step3 ms5
 Scenario: Starting a job with valid Asset Write step.Scenario: Starting a job with valid Asset Write step2 ms5
 Scenario: Starting a job with invalid Asset Write step.Scenario: Starting a job with invalid Asset Write step2 ms5
 Scenario: Starting a job with valid Package Uninstall step.Scenario: Starting a job with valid Package Uninstall step2 ms5
 Scenario: Starting a job with invalid Package Uninstall step.Scenario: Starting a job with invalid Package Uninstall step2 ms5
 Scenario: Starting job with valid Command Execution and Package Install steps.And Command "pwd" is executed2 ms5
 Scenario: Starting job with valid Command Execution and Package Install steps.Scenario: Starting job with valid Command Execution and Package Install steps2 ms5
 Scenario: Starting job with invalid Command Execution and Package Install steps.And Command "pwd" is executed1 ms5
 Scenario: Starting job with invalid Command Execution and Package Install steps.Scenario: Starting job with invalid Command Execution and Package Install steps2 ms5
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps.And Bundles are requested1 ms5
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps.Scenario: Starting a job with valid Bundle Start and Bundle Stop steps2 ms5
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps.And Bundles are requested2 ms5
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps.Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps2 ms5
 Scenario: Starting job with valid Configuration Put and Command Execution steps.Scenario: Starting job with valid Configuration Put and Command Execution steps2 ms5
 Scenario: Starting job with invalid Configuration Put and Command Execution steps.Scenario: Starting job with invalid Configuration Put and Command Execution steps2 ms5
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps.Scenario: Starting a job with valid Package Uninstall and Asset Write steps2 ms5
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps.Scenario: Starting a job with invalid Package Uninstall and Asset Write steps4 ms5
 Scenario: Starting job with valid Command Execution step and multiple devices.And Command "pwd" is executed2 ms5
 Scenario: Starting job with valid Command Execution step and multiple devices.Scenario: Starting job with valid Command Execution step and multiple devices3 ms5
 Scenario: Starting job with invalid Command Execution step and multiple devices.And Command "pwd" is executed1 ms5
 Scenario: Starting job with invalid Command Execution step and multiple devices.Scenario: Starting job with invalid Command Execution step and multiple devices2 ms5
 Scenario: Starting job with valid Bundle Start step and multiple devices.And Bundles are requested1 ms5
 Scenario: Starting job with valid Bundle Start step and multiple devices.Scenario: Starting job with valid Bundle Start step and multiple devices2 ms5
 Scenario: Starting job with invalid Bundle Start step and multiple devices.And Bundles are requested1 ms5
 Scenario: Starting job with invalid Bundle Start step and multiple devices.Scenario: Starting job with invalid Bundle Start step and multiple devices2 ms5
 Scenario: Starting a job with valid Bundle Stop step and multiple devices.And Bundles are requested2 ms5
 Scenario: Starting a job with valid Bundle Stop step and multiple devices.Scenario: Starting a job with valid Bundle Stop step and multiple devices2 ms5
 Scenario: Starting a job with invalid Bundle Stop step and multiple devices.And Bundles are requested2 ms5
 Scenario: Starting a job with invalid Bundle Stop step and multiple devices.Scenario: Starting a job with invalid Bundle Stop step and multiple devices2 ms5
 Scenario: Starting a job with valid Configuration Put step and multiple devices.Scenario: Starting a job with valid Configuration Put step and multiple devices3 ms5
 Scenario: Starting a job with invalid Configuration Put step and multiple devices.Scenario: Starting a job with invalid Configuration Put step and multiple devices2 ms5
 Scenario: Starting a job with valid Asset Write step and multiple targets.Scenario: Starting a job with valid Asset Write step and multiple targets2 ms5
 Scenario: Starting a job with invalid Asset Write step and multiple targets.Scenario: Starting a job with invalid Asset Write step and multiple targets3 ms5
 Scenario: Starting a job with valid Package Uninstall step and multiple targets.Scenario: Starting a job with valid Package Uninstall step and multiple targets11 ms5
 Scenario: Starting a job with invalid Package Uninstall step and multiple targets.Scenario: Starting a job with invalid Package Uninstall step and multiple targets8 ms5
 Scenario: Starting a job with valid Package Install step and multiple devices.Scenario: Starting a job with valid Package Install step and multiple devices6 ms5
 Scenario: Starting a job with invalid Package Install step and multiple devices.Scenario: Starting a job with invalid Package Install step and multiple devices3 ms5
 Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices.And Command "pwd" is executed1 ms5
 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 devices2 ms5
 Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices.And Command "pwd" is executed3 ms5
 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 devices3 ms5
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices.And Bundles are requested0 ms5
 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 devices0 ms5
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices.And Bundles are requested2 ms5
 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 devices3 ms5
 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 devices3 ms5
 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 ms5
 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 ms5
 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 ms5
 Scenario: Stop job with multiple Bundle Start and Package Install steps and one target.And Bundles are requested1 ms5
 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 ms5
 Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target.And Bundles are requested2 ms5
 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 ms5
 Scenario: Stop job with multiple Command Execution and Package Install steps and one target.And Command pwd is executed1 ms5
 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 ms5
 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 ms5
 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 target3 ms5
 Scenario: Stop job with multiple targets and Bundle Start and Package Install steps.And Bundles are requested1 ms5
 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 ms5
 Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps.And Bundles are requested2 ms5
 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 ms5
 Scenario: Stop job with multiple targets and Command Execution and Package Install steps.And Command pwd is executed2 ms5
 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 steps3 ms5
 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 ms5
 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 ms5
 Scenario: Start broker for all scenarios.Given Start Broker1 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms5
 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 ms5
 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 Time2 ms5
 Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time3 ms5
 Scenario: Executing Job When Device Connected After End Date And Time.Scenario: Executing Job When Device Connected After End Date And Time4 ms5
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device3 ms5
 Scenario: Executing Job Without Steps.Scenario: Executing Job Without Steps2 ms5
 Scenario: Start broker for all scenarios.Given Start Broker2 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms5
 Scenario: Test LOOSE user coupling on single connection.And The connection status is "CONNECTED"2 ms591
 Scenario: New connection with reserved ID.And The connection status is "CONNECTED"0 ms591
 Scenario: Test STRICT user coupling on single connection.And The connection status is "CONNECTED"1 ms591
 Scenario: Test STRICT user coupling with user change allowed on single connection.And The connection status is "CONNECTED"0 ms591
 Scenario: Test LOOSE user coupling with 3 connections.And The connection status is "CONNECTED"2 ms591
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.And The connection status is "CONNECTED"2 ms591
 Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode.And The connection status is "CONNECTED"2 ms591
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode.And The connection status is "CONNECTED"2 ms591
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices.Then I find 1 connection2 ms591
 Scenario: Stealing link scenario.And Client named "client-2" is not connected7 ms591
 Scenario: List Endpoints From "kapua-sys" Account.Then I find 3 endpoints1 ms591
 Scenario: Restarting job with Command Execution step.And A new job target item1 ms591
 Scenario: Restarting job with Asset Write step.And A new job target item1 ms591
 Scenario: Restarting job with Configuration Put step.And A new job target item1 ms591
 Scenario: Restarting job with Bundle Start step.And A new job target item2 ms591
 Scenario: Restarting job with Bundle Stop step.And A new job target item2 ms591
 Scenario: Restarting job with Package Install step.And A new job target item1 ms591
 Scenario: Restarting job with Package Uninstall step.And A new job target item1 ms591
 Scenario: Restarting job with two Bundle Start steps.And A new job target item3 ms591
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.And A new job target item2 ms591
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.And A new job target item2 ms591
 Scenario: Restarting a job with Package Uninstall and Bundle Start steps.And A new job target item1 ms591
 Scenario: Restarting a job with Command Execution and Bundle Start steps.And A new job target item1 ms591
 Scenario: Restarting a job with Asset Write and Bundle Start steps.And A new job target item1 ms591
 Scenario: Restarting a job with Configuration Put and Bundle Start steps.And A new job target item1 ms591
 Scenario: Starting a job with Command Execution step.And A new job target item1 ms591
 Scenario: Starting a job with Asset Write step.And A new job target item1 ms591
 Scenario: Starting a job with Bundle Start step.And Bundles are requested2 ms591
 Scenario: Starting a job with Bundle Stop step.And Bundles are requested2 ms591
 Scenario: Starting a job with Configuration Put step.And A new job target item1 ms591
 Scenario: Starting a job with Command Execution and Bundle Start steps.And Bundles are requested1 ms591
 Scenario: Starting a job with Asset Write and Bundle Start steps.And Bundles are requested1 ms591
 Scenario: Starting a job with two Bundle Start steps.And Bundles are requested1 ms591
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.And Bundles are requested1 ms591
 Scenario: Starting a job with Configuration Put and Bundle Start steps.And Bundles are requested2 ms591
 Scenario: Starting a job with Package Install and Bundle Start steps.And Bundles are requested1 ms591
 Scenario: Restarting job with valid Command Execution step two times.When I search for events from device "rpione3" in account "kapua-sys"1 ms591
 Scenario: Restarting job with invalid Command Execution step two times.When I search for events from device "rpione3" in account "kapua-sys"1 ms591
 Scenario: Restarting a job with valid Package Uninstall step two times.And I search for events from device "rpione3" in account "kapua-sys"1 ms591
 Scenario: Restarting a job with invalid Package Uninstall step two times.And I search for events from device "rpione3" in account "kapua-sys"1 ms591
 Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times.And The type of the last event is "DEPLOY"1 ms591
 Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times.And The type of the last event is "DEPLOY"2 ms591
 Scenario: Restarting a job with valid Configuration Put step two times.Then Configuration is requested1 ms591
 Scenario: Restarting a job with invalid Configuration Put step two times.Then Configuration is requested1 ms591
 Scenario: Restarting a job with valid Package Install step two times.When I search for events from device "rpione3" in account "kapua-sys"1 ms591
 Scenario: Restarting a job with invalid Package Install step two times.When I search for events from device "rpione3" in account "kapua-sys"1 ms591
 Scenario: Restarting job With valid Asset Write step two times.And Device assets are requested1 ms591
 Scenario: Restarting job with invalid Asset Write step two times.And Device assets are requested3 ms591
 Scenario: Restarting job with valid Configuration Put and Command Execution steps two times.Then Configuration is requested2 ms591
 Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times.Then Configuration is requested2 ms591
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times.And Device assets are requested1 ms591
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times.And Device assets are requested1 ms591
 Scenario: Restarting a job with valid Configuration Put step and multiple devices two times.Then Configuration is requested2 ms591
 Scenario: Restarting a job with invalid Configuration Put and multiple devices two times.Then Configuration is requested1 ms591
 Scenario: Restarting a job with valid Package Install step and multiple devices two times.And I restart a job7 ms591
 Scenario: Restarting job with valid Asset Write step and multiple devices two times.And Device assets are requested0 ms591
 Scenario: Restarting job With invalid Asset Write and multiple two times.And Device assets are requested2 ms591
 Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times.Then Configuration is requested2 ms591
 Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times.Then Configuration is requested2 ms591
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times.And Device assets are requested2 ms591
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times.And Device assets are requested1 ms591
 Scenario: Starting a job with valid Command Execution step.When I search for events from device "rpione3" in account "kapua-sys"1 ms591
 Scenario: Starting a job with invalid Command Execution step.When I search for events from device "rpione3" in account "kapua-sys"2 ms591
 Scenario: Starting a job with valid Package Install step.When I search for events from device "rpione3" in account "kapua-sys"2 ms591
 Scenario: Starting a job with invalid Package Install step.When I search for events from device "rpione3" in account "kapua-sys"2 ms591
 Scenario: Starting a job with valid Asset Write step.When Device assets are requested1 ms591
 Scenario: Starting a job with invalid Asset Write step.And Device assets are requested1 ms591
 Scenario: Starting a job with valid Package Uninstall step.When I search for events from device "rpione3" in account "kapua-sys"1 ms591
 Scenario: Starting a job with invalid Package Uninstall step.When I search for events from device "rpione3" in account "kapua-sys"2 ms591
 Scenario: Starting job with valid Configuration Put and Command Execution steps.And Configuration is requested1 ms591
 Scenario: Starting job with invalid Configuration Put and Command Execution steps.Then Configuration is requested1 ms591
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps.When Device assets are requested2 ms591
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps.When Device assets are requested3 ms591
 Scenario: Starting a job with valid Configuration Put step and multiple devices.Then Configuration is requested3 ms591
 Scenario: Starting a job with invalid Configuration Put step and multiple devices.Then Configuration is requested1 ms591
 Scenario: Starting a job with valid Asset Write step and multiple targets.And Device assets are requested2 ms591
 Scenario: Starting a job with invalid Asset Write step and multiple targets.And Device assets are requested2 ms591
 Scenario: Starting a job with valid Package Uninstall step and multiple targets.And I start a job2 ms591
 Scenario: Starting a job with invalid Package Uninstall step and multiple targets.And I start a job6 ms591
 Scenario: Starting a job with valid Package Install step and multiple devices.And I start a job4 ms591
 Scenario: Starting a job with invalid Package Install step and multiple devices.And I start a job2 ms591
 Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices.Then Configuration is requested2 ms591
 Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices.Then Configuration is requested1 ms591
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices.And Device assets are requested2 ms591
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices.And Device assets are requested1 ms591
 Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target.And Configuration is requested1 ms591
 Scenario: Stop job with multiple Asset Write and Package Install steps and one target.When Device assets are requested2 ms591
 Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps.And Configuration is requested1 ms591
 Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target.When Device assets are requested2 ms591
 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 ms591
 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"1 ms591
 Scenario: Executing Job When Device Connected Before End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"2 ms591
 Scenario: Executing Job When Device Connected After End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"2 ms591
 Scenario: Executing Job And Then Restarting Device.When I search for events from device "rpione3" in account "kapua-sys"2 ms591
 Scenario: Executing Job Without Steps.When I search for events from device "rpione3" in account "kapua-sys"2 ms591

All Tests

PackageDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
(root)15 sec53052891036816187
Scenario: Creating And Account Without "10 ms0066
org.eclipse.kapua84 ms0033
org.eclipse.kapua.broker.core.plugin3.4 sec001515
org.eclipse.kapua.client.gateway60 ms004343
org.eclipse.kapua.client.gateway.kura0.19 sec001414
org.eclipse.kapua.client.gateway.spi.util2.7 sec001515
org.eclipse.kapua.client.gateway.util2 ms0033
org.eclipse.kapua.commons.about0.48 sec0011
org.eclipse.kapua.commons.configuration0 ms0011
org.eclipse.kapua.commons.configuration.metatype0 ms001919
org.eclipse.kapua.commons.liquibase0.87 sec0044
org.eclipse.kapua.commons.metric1 ms0022
org.eclipse.kapua.commons.model0.19 sec0088
org.eclipse.kapua.commons.model.id3 ms0011
org.eclipse.kapua.commons.security3 sec0033
org.eclipse.kapua.commons.setting0 ms0044
org.eclipse.kapua.commons.util3 ms008585
org.eclipse.kapua.commons.util.xml19 ms0099
org.eclipse.kapua.integration.misc0 ms0101
org.eclipse.kapua.integration.service.datastoreJunit0 ms0505
org.eclipse.kapua.kura.simulator.main.simulation5.3 sec001313
org.eclipse.kapua.locator.internal0.2 sec021012
org.eclipse.kapua.message.internal0.22 sec022628
org.eclipse.kapua.message.internal.device.data0 ms0033
org.eclipse.kapua.message.internal.device.lifecycle55 ms002121
org.eclipse.kapua.message.internal.xml0.97 sec001111
org.eclipse.kapua.service.datastore.test.junit0.16 sec0044
org.eclipse.kapua.service.datastore.test.junit.client0.29 sec0077
org.eclipse.kapua.service.datastore.test.junit.clientTransport76 ms031922
org.eclipse.kapua.service.device.management.commons.message.notification7 ms0022