Test Result

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

All Failed Tests

Test NameDurationAge
 Scenario: Starting a job with Package Install step.Then Device status is "DISCONNECTED"3 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 Broker3 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms3
 Scenario: Find correct number of messages by corresponding metric.Then I prepare a number of messages with the following details and remember the list as "TestMessages"2 ms3
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric2 ms3
 Scenario: Finding correct number of messages by corresponding two metrics.Then I prepare a number of messages with the following details and remember the list as "TestMessages"2 ms3
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics2 ms3
 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 ms3
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics2 ms3
 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 ms3
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters1 ms3
 Scenario: Start broker for all scenarios.Given Start Broker2 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms3
 Scenario: Start broker for all scenarios.Given Start Broker2 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms3
 Scenario: Start broker for all scenarios.Given Start Broker1 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms3
 Scenario: Find correct number of messages by corresponding metric.Then I prepare a number of messages with the following details and remember the list as "TestMessages"2 ms3
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric3 ms3
 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 ms3
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics2 ms3
 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 ms3
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics2 ms3
 Scenario: Finding messages with incorrect metric parameters.Then I prepare a number of messages with the following details and remember the list as "TestMessages"2 ms3
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters2 ms3
 Scenario: Start broker for all scenarios.Given Start Broker1 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms3
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Given Mqtt Device is started5 ms3
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed7 ms3
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started7 ms3
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY7 ms3
 Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started3 ms3
 Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY4 ms3
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started6 ms3
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account7 ms3
 Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Given Mqtt Device is started2 ms3
 Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Scenario: DM5 Data manage publish to CTRL_ACC is not allowed7 ms3
 Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started4 ms3
 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 allowed6 ms3
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Given Mqtt Device is started4 ms3
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed6 ms3
 Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started3 ms3
 Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI4 ms3
 Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Given Mqtt Device is started3 ms3
 Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC4 ms3
 Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started5 ms3
 Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI6 ms3
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started5 ms3
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed7 ms3
 Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started6 ms3
 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 allowed8 ms3
 Scenario: Start broker for all scenarios.Given Start Broker12 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios12 ms3
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Given Mqtt Device is started4 ms3
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic7 ms3
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Given Mqtt Device is started5 ms3
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY6 ms3
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started4 ms3
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY5 ms3
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started6 ms3
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY8 ms3
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started6 ms3
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account8 ms3
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.Given Mqtt Device is started2 ms3
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.Scenario: B5 Broker publish to CTRL_ACC is not allowed4 ms3
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started7 ms3
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed9 ms3
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Given Mqtt Device is started7 ms3
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed13 ms3
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started9 ms3
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI9 ms3
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started3 ms3
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed5 ms3
 Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.Given Mqtt Device is started3 ms3
 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 allowed4 ms3
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Given Mqtt Device is started2 ms3
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed4 ms3
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started7 ms3
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI9 ms3
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started4 ms3
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed6 ms3
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started4 ms3
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed5 ms3
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Given Mqtt Device is started5 ms3
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY6 ms3
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started2 ms3
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY3 ms3
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started5 ms3
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY6 ms3
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started2 ms3
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account5 ms3
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Given Mqtt Device is started4 ms3
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Scenario: D5 Device subscribe - publish - admin on CTRL_ACC6 ms3
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started3 ms3
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI5 ms3
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started2 ms3
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed6 ms3
 Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.Given Mqtt Device is started6 ms3
 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 allowed6 ms3
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Given Mqtt Device is started4 ms3
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed6 ms3
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started7 ms3
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI7 ms3
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started3 ms3
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms3
 Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started6 ms3
 Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed8 ms3
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Given Mqtt Device is started1 ms3
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY3 ms3
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started5 ms3
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY8 ms3
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started3 ms3
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY4 ms3
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started4 ms3
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account6 ms3
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Given Mqtt Device is started6 ms3
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Scenario: DV5 Data view publish to CTRL_ACC is not allowed7 ms3
 Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started3 ms3
 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 ms3
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Given Mqtt Device is started9 ms3
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed9 ms3
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started3 ms3
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI4 ms3
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started4 ms3
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed5 ms3
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Given Mqtt Device is started2 ms3
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed4 ms3
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Given Mqtt Device is started3 ms3
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed4 ms3
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Given Mqtt Device is started4 ms3
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed5 ms3
 Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed.Given Mqtt Device is started3 ms3
 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 allowed5 ms3
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started5 ms3
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed7 ms3
 Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started4 ms3
 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 allowed6 ms3
 Scenario: Start broker for all scenarios.Given Start Broker2 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms3
 Scenario: Send BIRTH message and then DC message.And I login as user with name "kapua-sys" and password "kapua-password"6 ms3
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message8 ms3
 Scenario: Start broker for all scenarios.Given Start Broker1 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms3
 Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Then Device is connected with "localhost" server ip2 ms3
 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 ms3
 Scenario: Start broker for all scenarios.Given Start Broker1 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms3
 Scenario: Send BIRTH message and then DC message while broker ip is set by System.Then Device is connected with "localhost" server ip4 ms3
 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 System5 ms3
 Scenario: Start broker for all scenarios.Given Start Broker1 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms3
 Scenario: Start broker for all scenarios.Given Start Broker2 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms3
 Scenario: Stealing link scenario.Scenario: Stealing link scenario8 ms3
 Scenario: Start broker for all scenarios.Given Start Broker1 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms3
 Scenario: Connect to the system and publish some data.Then Device sim-1 for account kapua-sys is registered after 5 seconds4 ms3
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data5 ms3
 Scenario: Start broker for all scenarios.Given Start Broker2 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms3
 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 seconds5 ms3
 Scenario: Starting and stopping the simulator should create a device entry and properly set its status.Scenario: Starting and stopping the simulator should create a device entry and properly set its status5 ms3
 Scenario: Installing a package.Then Device sim-1 for account kapua-sys is registered after 5 seconds0 ms3
 Scenario: Installing a package.Scenario: Installing a package0 ms3
 Scenario: Start broker for all scenarios.Given Start Broker1 ms3
 Scenario: Start broker for all scenarios.Given Start Broker1 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms3
 Scenario: Restarting job with Command Execution step.Scenario: Restarting job with Command Execution step3 ms3
 Scenario: Restarting job with Asset Write step.Scenario: Restarting job with Asset Write step3 ms3
 Scenario: Restarting job with Configuration Put step.Scenario: Restarting job with Configuration Put step2 ms3
 Scenario: Restarting job with Bundle Start step.Scenario: Restarting job with Bundle Start step3 ms3
 Scenario: Restarting job with Bundle Stop step.Scenario: Restarting job with Bundle Stop step2 ms3
 Scenario: Restarting job with Package Install step.Scenario: Restarting job with Package Install step2 ms3
 Scenario: Restarting job with Package Uninstall step.Scenario: Restarting job with Package Uninstall step2 ms3
 Scenario: Restarting job with two Bundle Start steps.Scenario: Restarting job with two Bundle Start steps2 ms3
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.Scenario: Restarting job with Bundle Stop and Bundle Start steps2 ms3
 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 ms3
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices3 ms3
 Scenario: Restarting a job with Package Uninstall and Bundle Start steps.Scenario: Restarting a job with Package Uninstall and Bundle Start steps4 ms3
 Scenario: Restarting a job with Command Execution and Bundle Start steps.Scenario: Restarting a job with Command Execution and Bundle Start steps2 ms3
 Scenario: Restarting a job with Asset Write and Bundle Start steps.Scenario: Restarting a job with Asset Write and Bundle Start steps2 ms3
 Scenario: Restarting a job with Configuration Put and Bundle Start steps.Scenario: Restarting a job with Configuration Put and Bundle Start steps2 ms3
 Scenario: Restarting job with Bundle Start step and multiple devices.Then I count 21 ms3
 Scenario: Restarting job with Bundle Start step and multiple devices.Scenario: Restarting job with Bundle Start step and multiple devices2 ms3
 Scenario: Restarting job with Bundle Stop step and multiple devices.Then I count 22 ms3
 Scenario: Restarting job with Bundle Stop step and multiple devices.Scenario: Restarting job with Bundle Stop step and multiple devices2 ms3
 Scenario: Restarting job with Package Download/Install step and multiple devices.Then I count 22 ms3
 Scenario: Restarting job with Package Download/Install step and multiple devices.Scenario: Restarting job with Package Download/Install step and multiple devices2 ms3
 Scenario: Restarting job with Package Uninstall step and multiple device.Then I count 22 ms3
 Scenario: Restarting job with Package Uninstall step and multiple device.Scenario: Restarting job with Package Uninstall step and multiple device3 ms3
 Scenario: Restarting job with Asset Write step and multiple devices.Then I count 21 ms3
 Scenario: Restarting job with Asset Write step and multiple devices.Scenario: Restarting job with Asset Write step and multiple devices2 ms3
 Scenario: Restarting job with Configuration Put step and multiple devices.Then I count 20 ms3
 Scenario: Restarting job with Configuration Put step and multiple devices.Scenario: Restarting job with Configuration Put step and multiple devices0 ms3
 Scenario: Restarting job with Command Execution step and multiple devices.Then I count 21 ms3
 Scenario: Restarting job with Command Execution step and multiple devices.Scenario: Restarting job with Command Execution step and multiple devices2 ms3
 Scenario: Restarting job with two Bundle Start steps and multiple devices.Then I count 21 ms3
 Scenario: Restarting job with two Bundle Start steps and multiple devices.Scenario: Restarting job with two Bundle Start steps and multiple devices2 ms3
 Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices.Then I count 22 ms3
 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 devices3 ms3
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.Then I count 22 ms3
 Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device.Then I count 21 ms3
 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 ms3
 Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices.Then I count 22 ms3
 Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices.Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices3 ms3
 Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices.Then I count 22 ms3
 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 devices3 ms3
 Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices.Then I count 22 ms3
 Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices.Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices2 ms3
 Scenario: Starting a job with Command Execution step.Scenario: Starting a job with Command Execution step3 ms3
 Scenario: Starting a job with Asset Write step.Scenario: Starting a job with Asset Write step3 ms3
 Scenario: Starting a job with Bundle Start step.Scenario: Starting a job with Bundle Start step2 ms3
 Scenario: Starting a job with Bundle Stop step.Scenario: Starting a job with Bundle Stop step2 ms3
 Scenario: Starting a job with Configuration Put step.Scenario: Starting a job with Configuration Put step3 ms3
 Scenario: Starting a job with Package Install step.Scenario: Starting a job with Package Install step5 ms3
 Scenario: Starting a job with Package Uninstall step.And Package named org.eclipse.kura.example.beacon with version 1.0.300 is received1 ms3
 Scenario: Starting a job with Package Uninstall step.Scenario: Starting a job with Package Uninstall step2 ms3
 Scenario: Starting a job with Command Execution and Bundle Start steps.Scenario: Starting a job with Command Execution and Bundle Start steps3 ms3
 Scenario: Starting a job with Asset Write and Bundle Start steps.Scenario: Starting a job with Asset Write and Bundle Start steps3 ms3
 Scenario: Starting a job with two Bundle Start steps.Scenario: Starting a job with two Bundle Start steps2 ms3
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.Scenario: Starting a job with Bundle Stop and Bundle Start steps3 ms3
 Scenario: Starting a job with Configuration Put and Bundle Start steps.Scenario: Starting a job with Configuration Put and Bundle Start steps3 ms3
 Scenario: Starting a job with Package Install and Bundle Start steps.Scenario: Starting a job with Package Install and Bundle Start steps2 ms3
 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 received2 ms3
 Scenario: Starting a job with Package Uninstall and Bundle Start steps.Scenario: Starting a job with Package Uninstall and Bundle Start steps2 ms3
 Scenario: Starting job with Bundle Start step and multiple devices.Then I count 22 ms3
 Scenario: Starting job with Bundle Start step and multiple devices.Scenario: Starting job with Bundle Start step and multiple devices2 ms3
 Scenario: Starting job with Bundle Stop step and multiple devices.Then I count 22 ms3
 Scenario: Starting job with Bundle Stop step and multiple devices.Scenario: Starting job with Bundle Stop step and multiple devices2 ms3
 Scenario: Starting job with Package Download/Install step and multiple devices.Scenario: Starting job with Package Download/Install step and multiple devices5 ms3
 Scenario: Starting job with Package Uninstall step and multiple device.Then I count 21 ms3
 Scenario: Starting job with Package Uninstall step and multiple device.Scenario: Starting job with Package Uninstall step and multiple device2 ms3
 Scenario: Starting job with Asset Write step and multiple devices.Then I count 22 ms3
 Scenario: Starting job with Asset Write step and multiple devices.Scenario: Starting job with Asset Write step and multiple devices3 ms3
 Scenario: Starting job with Configuration Put step and multiple devices.Then I count 22 ms3
 Scenario: Starting job with Configuration Put step and multiple devices.Scenario: Starting job with Configuration Put step and multiple devices2 ms3
 Scenario: Starting job with Command Execution step and multiple devices.Then I count 21 ms3
 Scenario: Starting job with Command Execution step and multiple devices.Scenario: Starting job with Command Execution step and multiple devices1 ms3
 Scenario: Starting job with two Bundle Start steps and multiple devices.Then I count 22 ms3
 Scenario: Starting job with two Bundle Start steps and multiple devices.Scenario: Starting job with two Bundle Start steps and multiple devices3 ms3
 Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices.Then I count 21 ms3
 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 ms3
 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 ms3
 Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device.Then I count 23 ms3
 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 ms3
 Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices.Then I count 22 ms3
 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 ms3
 Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices.Then I count 22 ms3
 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 devices3 ms3
 Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices.Then I count 22 ms3
 Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices.Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices3 ms3
 Scenario: Start broker for all scenarios.Given Start Broker1 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms3
 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 Time3 ms3
 Scenario: Executing Job When Device Connected Before The Specified Start Date And Time.Scenario: Executing Job When Device Connected Before The Specified Start Date And Time3 ms3
 Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time3 ms3
 Scenario: Executing Job When Device Connected After End Date And Time.Scenario: Executing Job When Device Connected After End Date And Time3 ms3
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device3 ms3
 Scenario: Executing Job Without Steps.Scenario: Executing Job Without Steps3 ms3
 Scenario: Start broker for all scenarios.Given Start Broker0 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0 ms3
 Scenario: Stealing link scenario.And Client named "client-2" is not connected6 ms622
 Scenario: Restarting job with Command Execution step.And A new job target item2 ms622
 Scenario: Restarting job with Asset Write step.And A new job target item2 ms622
 Scenario: Restarting job with Configuration Put step.And A new job target item1 ms622
 Scenario: Restarting job with Bundle Start step.And A new job target item2 ms622
 Scenario: Restarting job with Bundle Stop step.And A new job target item1 ms622
 Scenario: Restarting job with Package Install step.And A new job target item2 ms622
 Scenario: Restarting job with Package Uninstall step.And A new job target item1 ms622
 Scenario: Restarting job with two Bundle Start steps.And A new job target item1 ms622
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.And A new job target item1 ms622
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.And A new job target item2 ms622
 Scenario: Restarting a job with Package Uninstall and Bundle Start steps.And A new job target item3 ms622
 Scenario: Restarting a job with Command Execution and Bundle Start steps.And A new job target item1 ms622
 Scenario: Restarting a job with Asset Write and Bundle Start steps.And A new job target item1 ms622
 Scenario: Restarting a job with Configuration Put and Bundle Start steps.And A new job target item1 ms622
 Scenario: Starting a job with Command Execution step.And A new job target item2 ms622
 Scenario: Starting a job with Asset Write step.And A new job target item2 ms622
 Scenario: Starting a job with Bundle Start step.And Bundles are requested1 ms622
 Scenario: Starting a job with Bundle Stop step.And Bundles are requested2 ms622
 Scenario: Starting a job with Configuration Put step.And A new job target item2 ms622
 Scenario: Starting a job with Command Execution and Bundle Start steps.And Bundles are requested2 ms622
 Scenario: Starting a job with Asset Write and Bundle Start steps.And Bundles are requested2 ms622
 Scenario: Starting a job with two Bundle Start steps.And Bundles are requested1 ms622
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.And Bundles are requested2 ms622
 Scenario: Starting a job with Configuration Put and Bundle Start steps.And Bundles are requested2 ms622
 Scenario: Starting a job with Package Install and Bundle Start steps.And Bundles are requested1 ms622
 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"2 ms622
 Scenario: Executing Job When Device Connected Before The Specified Start Date And Time.When I search for events from device "rpione3" in account "kapua-sys"2 ms622
 Scenario: Executing Job When Device Connected Before End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"2 ms622
 Scenario: Executing Job When Device Connected After End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"2 ms622
 Scenario: Executing Job And Then Restarting Device.When I search for events from device "rpione3" in account "kapua-sys"1 ms622
 Scenario: Executing Job Without Steps.When I search for events from device "rpione3" in account "kapua-sys"2 ms622

All Tests

PackageDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
(root)8.7 sec296-2341683-36066259-41588238-7998
org.eclipse.kapua0.12 sec0033
org.eclipse.kapua.broker.core.plugin2.8 sec001515
org.eclipse.kapua.client.gateway62 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.16 sec0011
org.eclipse.kapua.commons.configuration62 ms001717
org.eclipse.kapua.commons.configuration.metatype5 ms00134+115134+115
org.eclipse.kapua.commons.liquibase7.9 sec0044
org.eclipse.kapua.commons.metric0 ms0022
org.eclipse.kapua.commons.model0.15 sec0088
org.eclipse.kapua.commons.model.id0 ms0011
org.eclipse.kapua.commons.security2.8 sec0033
org.eclipse.kapua.commons.setting0 ms0044
org.eclipse.kapua.commons.util3 sec00130+38130+38
org.eclipse.kapua.commons.util.xml0.2 sec0099
org.eclipse.kapua.integration.service.datastoreJunit0 ms0505
org.eclipse.kapua.kura.simulator.main.simulation5.4 sec001313
org.eclipse.kapua.locator.internal0.21 sec021012
org.eclipse.kapua.message.internal0.26 sec022628
org.eclipse.kapua.message.internal.device.data2 ms0033
org.eclipse.kapua.message.internal.device.lifecycle0 ms001717
org.eclipse.kapua.message.internal.xml1.2 sec001111
org.eclipse.kapua.service.datastore.test.junit0.2 sec0044
org.eclipse.kapua.service.datastore.test.junit.client0.25 sec0077
org.eclipse.kapua.service.datastore.test.junit.clientTransport72 ms031922
org.eclipse.kapua.service.device.management.commons.message.notification6 ms0022