Test Result

296 failures (-234) , 1,695 skipped (-3607)
8,643 tests (-7930)
Took 55 min.

All Failed Tests

Test NameDurationAge
 Scenario: Starting a job with Package Install step.Then Device status is "DISCONNECTED"2 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 and Bundle Start steps and multiple devices.Then Device status is "DISCONNECTED"3 ms1
 Scenario: Start broker for all scenarios.Given Start Broker1 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 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 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 Broker0 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0 ms5
 Scenario: Start broker for all scenarios.Given Start Broker0 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"1 ms5
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics2 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 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 scenarios1 ms5
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Given Mqtt Device is started6 ms5
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed7 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_REPLY4 ms5
 Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started2 ms5
 Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY4 ms5
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started5 ms5
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account7 ms5
 Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Given Mqtt Device is started5 ms5
 Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Scenario: DM5 Data manage publish to CTRL_ACC is not allowed7 ms5
 Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started3 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 allowed5 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 started9 ms5
 Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI9 ms5
 Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Given Mqtt Device is started6 ms5
 Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC8 ms5
 Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started4 ms5
 Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI6 ms5
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started6 ms5
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed7 ms5
 Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started5 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 allowed5 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 started5 ms5
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic7 ms5
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Given Mqtt Device is started11 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 started4 ms5
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY5 ms5
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started0 ms5
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY0 ms5
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started13 ms5
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account13 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 allowed6 ms5
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Given Mqtt Device is started8 ms5
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed10 ms5
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started3 ms5
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI5 ms5
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started5 ms5
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed6 ms5
 Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.Given Mqtt Device is started4 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 allowed6 ms5
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Given Mqtt Device is started6 ms5
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed7 ms5
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started3 ms5
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI5 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 started2 ms5
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms5
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Given Mqtt Device is started3 ms5
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY4 ms5
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started2 ms5
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY4 ms5
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started5 ms5
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY6 ms5
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started0 ms5
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account1 ms5
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Given Mqtt Device is started4 ms5
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Scenario: D5 Device subscribe - publish - admin on CTRL_ACC6 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_CLI5 ms5
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started5 ms5
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed6 ms5
 Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.Given Mqtt Device is started7 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 allowed8 ms5
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Given Mqtt Device is started5 ms5
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed7 ms5
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started4 ms5
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI5 ms5
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started0 ms5
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed0 ms5
 Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started3 ms5
 Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed12 ms5
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Given Mqtt Device is started4 ms5
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY8 ms5
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started6 ms5
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY7 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_REPLY4 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 started2 ms5
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Scenario: DV5 Data view publish to CTRL_ACC is not allowed6 ms5
 Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started3 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 allowed4 ms5
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started5 ms5
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI6 ms5
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started6 ms5
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed8 ms5
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Given Mqtt Device is started5 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 allowed7 ms5
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Given Mqtt Device is started4 ms5
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed6 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 allowed5 ms5
 Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed.Given Mqtt Device is started2 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 allowed6 ms5
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started4 ms5
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed5 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 allowed5 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"5 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 ip2 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 file3 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: Send BIRTH message and then DC message while broker ip is set by System.Then Device is connected with "localhost" server ip2 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 System2 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: Start broker for all scenarios.Given Start Broker2 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms5
 Scenario: Stealing link scenario.Scenario: Stealing link scenario6 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: Connect to the system and publish some data.Then Device sim-1 for account kapua-sys is registered after 5 seconds13 ms5
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data13 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: 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 seconds1 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 status2 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 scenarios2 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 step3 ms5
 Scenario: Restarting job with Configuration Put step.Scenario: Restarting job with Configuration Put step5 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 steps2 ms5
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.Scenario: Restarting job with Bundle Stop and Bundle Start steps2 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 devices0 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 21 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 devices2 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 21 ms5
 Scenario: Restarting job with Package Uninstall step and multiple device.Scenario: Restarting job with Package Uninstall step and multiple device2 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 21 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 25 ms5
 Scenario: Restarting job with two Bundle Start steps and multiple devices.Scenario: Restarting job with two Bundle Start steps and multiple devices5 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 20 ms5
 Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device.Then I count 211 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 device11 ms5
 Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices.Then I count 23 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 devices5 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 step2 ms5
 Scenario: Starting a job with Bundle Start step.Scenario: Starting a job with Bundle Start step2 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 step3 ms5
 Scenario: Starting a job with Package Uninstall step.And Package named org.eclipse.kura.example.beacon with version 1.0.300 is received1 ms5
 Scenario: Starting a job with Package Uninstall step.Scenario: Starting a job with Package Uninstall step2 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 steps3 ms5
 Scenario: Starting a job with two Bundle Start steps.Scenario: Starting a job with two Bundle Start steps3 ms5
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.Scenario: Starting a job with Bundle Stop and Bundle Start steps3 ms5
 Scenario: Starting a job with Configuration Put and Bundle Start steps.Scenario: Starting a job with Configuration Put and Bundle Start steps1 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 20 ms5
 Scenario: Starting job with Bundle Stop step and multiple devices.Scenario: Starting job with Bundle Stop step and multiple devices0 ms5
 Scenario: Starting job with Package Download/Install step and multiple devices.Scenario: Starting job with Package Download/Install step and multiple devices4 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 20 ms5
 Scenario: Starting job with Asset Write step and multiple devices.Scenario: Starting job with Asset Write step and multiple devices0 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 devices2 ms5
 Scenario: Starting job with two Bundle Start steps and multiple devices.Then I count 22 ms5
 Scenario: Starting job with two Bundle Start steps and multiple devices.Scenario: Starting job with two Bundle Start steps and multiple devices3 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 devices5 ms5
 Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device.Then I count 22 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 device3 ms5
 Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices.Then I count 22 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 devices3 ms5
 Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices.Then I count 21 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 devices1 ms5
 Scenario: Start broker for all scenarios.Given Start Broker0 ms5
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms5
 Scenario: Executing Job When Device Connected After End Date And Time.Scenario: Executing Job When Device Connected After End Date And Time1 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: 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 ms6
 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 ms8
 Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time4 ms8
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device2 ms8
 Scenario: Stealing link scenario.And Client named "client-2" is not connected4 ms604
 Scenario: Restarting job with Command Execution step.And A new job target item1 ms604
 Scenario: Restarting job with Asset Write step.And A new job target item2 ms604
 Scenario: Restarting job with Configuration Put step.And A new job target item1 ms604
 Scenario: Restarting job with Bundle Start step.And A new job target item1 ms604
 Scenario: Restarting job with Bundle Stop step.And A new job target item1 ms604
 Scenario: Restarting job with Package Install step.And A new job target item1 ms604
 Scenario: Restarting job with Package Uninstall step.And A new job target item1 ms604
 Scenario: Restarting job with two Bundle Start steps.And A new job target item1 ms604
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.And A new job target item2 ms604
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.And A new job target item2 ms604
 Scenario: Restarting a job with Package Uninstall and Bundle Start steps.And A new job target item1 ms604
 Scenario: Restarting a job with Command Execution and Bundle Start steps.And A new job target item1 ms604
 Scenario: Restarting a job with Asset Write and Bundle Start steps.And A new job target item1 ms604
 Scenario: Restarting a job with Configuration Put and Bundle Start steps.And A new job target item1 ms604
 Scenario: Starting a job with Command Execution step.And A new job target item1 ms604
 Scenario: Starting a job with Asset Write step.And A new job target item1 ms604
 Scenario: Starting a job with Bundle Start step.And Bundles are requested1 ms604
 Scenario: Starting a job with Bundle Stop step.And Bundles are requested1 ms604
 Scenario: Starting a job with Configuration Put step.And A new job target item1 ms604
 Scenario: Starting a job with Command Execution and Bundle Start steps.And Bundles are requested2 ms604
 Scenario: Starting a job with Asset Write and Bundle Start steps.And Bundles are requested3 ms604
 Scenario: Starting a job with two Bundle Start steps.And Bundles are requested2 ms604
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.And Bundles are requested2 ms604
 Scenario: Starting a job with Configuration Put and Bundle Start steps.And Bundles are requested1 ms604
 Scenario: Starting a job with Package Install and Bundle Start steps.And Bundles are requested1 ms604
 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 ms604
 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 ms604
 Scenario: Executing Job When Device Connected Before End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms604
 Scenario: Executing Job When Device Connected After End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms604
 Scenario: Executing Job And Then Restarting Device.When I search for events from device "rpione3" in account "kapua-sys"1 ms604
 Scenario: Executing Job Without Steps.When I search for events from device "rpione3" in account "kapua-sys"1 ms604

All Tests

PackageDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
(root)10 sec296-2341683-36066285-40838264-7923
org.eclipse.kapua79 ms0033
org.eclipse.kapua.broker.core.plugin3.1 sec001515
org.eclipse.kapua.client.gateway71 ms004343
org.eclipse.kapua.client.gateway.kura0.18 sec001414
org.eclipse.kapua.client.gateway.spi.util2.7 sec001515
org.eclipse.kapua.client.gateway.util2 ms0033
org.eclipse.kapua.commons.about2.1 sec0011
org.eclipse.kapua.commons.configuration57 ms001717
org.eclipse.kapua.commons.configuration.metatype8 ms001919
org.eclipse.kapua.commons.liquibase0.67 sec0044
org.eclipse.kapua.commons.metric3 ms0022
org.eclipse.kapua.commons.model0.19 sec0088
org.eclipse.kapua.commons.model.id4 ms0011
org.eclipse.kapua.commons.security3 sec0033
org.eclipse.kapua.commons.setting1 ms0044
org.eclipse.kapua.commons.util0.23 sec009090
org.eclipse.kapua.commons.util.xml0.32 sec0099
org.eclipse.kapua.integration.service.datastoreJunit0 ms0505
org.eclipse.kapua.kura.simulator.main.simulation5.7 sec001313
org.eclipse.kapua.locator.internal0.13 sec021012
org.eclipse.kapua.message.internal0.21 sec022628
org.eclipse.kapua.message.internal.device.data0 ms0033
org.eclipse.kapua.message.internal.device.lifecycle17 ms002121
org.eclipse.kapua.message.internal.xml1.2 sec001111
org.eclipse.kapua.service.datastore.test.junit0.16 sec0044
org.eclipse.kapua.service.datastore.test.junit.client0.23 sec0077
org.eclipse.kapua.service.datastore.test.junit.clientTransport0.12 sec031922
org.eclipse.kapua.service.device.management.commons.message.notification7 ms0022