Test Result : (root)

296 failures (-234) , 1,683 skipped (-3606)
8,238 tests (-7998)
Took 8.7 sec.

All Failed Tests

Test NameDurationAge
 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: 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: 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: Connect to the system and publish some data.Scenario: Connect to the system and publish some data5 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device3 ms3
 Scenario: Executing Job And Then Restarting Device.When I search for events from device "rpione3" in account "kapua-sys"1 ms622
 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 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 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 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 End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time3 ms3
 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 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 The Specified Start Date And Time.When I search for events from device "rpione3" in account "kapua-sys"2 ms622
 Scenario: Executing Job Without Steps.Scenario: Executing Job Without Steps3 ms3
 Scenario: Executing Job Without Steps.When I search for events from device "rpione3" in account "kapua-sys"2 ms622
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric3 ms3
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric2 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.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 all messages by selecting all metrics.Scenario: Finding all messages by selecting all 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.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 correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics2 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.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: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters2 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.Then I prepare a number of messages with the following details and remember the list as "TestMessages"2 ms3
 Scenario: Installing a package.Scenario: Installing a package0 ms3
 Scenario: Installing a package.Then Device sim-1 for account kapua-sys is registered after 5 seconds0 ms3
 Scenario: Restarting a job with Asset Write and Bundle Start steps.And A new job target item1 ms622
 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 Command Execution and Bundle Start steps.And A new job target item1 ms622
 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 Configuration Put and Bundle Start steps.And A new job target item1 ms622
 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 a job with Package Uninstall and Bundle Start steps.And A new job target item3 ms622
 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 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 Asset Write and Bundle Start steps and multiple devices.Then I count 22 ms3
 Scenario: Restarting job with Asset Write step.And A new job target item2 ms622
 Scenario: Restarting job with Asset Write step.Scenario: Restarting job with Asset Write step3 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 Asset Write step and multiple devices.Then I count 21 ms3
 Scenario: Restarting job with Bundle Start step.And A new job target item2 ms622
 Scenario: Restarting job with Bundle Start step.Scenario: Restarting job with Bundle Start step3 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 Start step and multiple devices.Then I count 21 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 Bundle Stop and Bundle Start step and multiple devices.Then I count 22 ms3
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.And A new job target item1 ms622
 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 Bundle Stop step.And A new job target item1 ms622
 Scenario: Restarting job with Bundle Stop step.Scenario: Restarting job with Bundle Stop step2 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 Bundle Stop step 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: Restarting job with Command Execution and Bundle Start steps and multiple devices.Then I count 22 ms3
 Scenario: Restarting job with Command Execution step.And A new job target item2 ms622
 Scenario: Restarting job with Command Execution step.Scenario: Restarting job with Command Execution step3 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 Command Execution step and multiple devices.Then I count 21 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 Configuration Put and Bundle Start steps and multiple devices.Then I count 22 ms3
 Scenario: Restarting job with Configuration Put step.And A new job target item1 ms622
 Scenario: Restarting job with Configuration Put step.Scenario: Restarting job with Configuration Put step2 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 Configuration Put step and multiple devices.Then I count 20 ms3
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.And A new job target item2 ms622
 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 job with Package Download/Install and Bundle Start steps 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 Download/Install step and multiple devices.Then I count 22 ms3
 Scenario: Restarting job with Package Install step.And A new job target item2 ms622
 Scenario: Restarting job with Package Install step.Scenario: Restarting job with Package Install step2 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 Package Uninstall and Bundle start steps and multiple device.Then I count 21 ms3
 Scenario: Restarting job with Package Uninstall step.And A new job target item1 ms622
 Scenario: Restarting job with Package Uninstall step.Scenario: Restarting job with Package Uninstall step2 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 Package Uninstall step and multiple device.Then I count 22 ms3
 Scenario: Restarting job with two Bundle Start steps.And A new job target item1 ms622
 Scenario: Restarting job with two Bundle Start steps.Scenario: Restarting job with two Bundle Start steps2 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 two Bundle Start steps and multiple devices.Then I count 21 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: 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: 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 config file.Scenario: Send BIRTH message and then DC message while broker ip is set by config file2 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: 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.Given Start Broker1 ms3
 Scenario: Start broker for all scenarios.Given Start Broker1 ms3
 Scenario: Start broker for all scenarios.Given Start Broker12 ms3
 Scenario: Start broker for all scenarios.Given Start Broker1 ms3
 Scenario: Start broker for all scenarios.Given Start Broker0 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.Given Start Broker1 ms3
 Scenario: Start broker for all scenarios.Given Start Broker1 ms3
 Scenario: Start broker for all scenarios.Given Start Broker2 ms3
 Scenario: Start broker for all scenarios.Given Start Broker2 ms3
 Scenario: Start broker for all scenarios.Given Start Broker2 ms3
 Scenario: Start broker for all scenarios.Given Start Broker3 ms3
 Scenario: Start broker for all scenarios.Given Start Broker2 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.Scenario: Start broker for all scenarios2 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: 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: Start broker for all scenarios.Scenario: Start broker for all scenarios0 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 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 scenarios12 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 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: 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: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms3
 Scenario: Starting a job with Asset Write and Bundle Start steps.And Bundles are requested2 ms622
 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 Asset Write step.And A new job target item2 ms622
 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.And Bundles are requested1 ms622
 Scenario: Starting a job with Bundle Start step.Scenario: Starting a job with Bundle Start step2 ms3
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.And Bundles are requested2 ms622
 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 Bundle Stop step.And Bundles are requested2 ms622
 Scenario: Starting a job with Bundle Stop step.Scenario: Starting a job with Bundle Stop step2 ms3
 Scenario: Starting a job with Command Execution and Bundle Start steps.And Bundles are requested2 ms622
 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 Command Execution step.And A new job target item2 ms622
 Scenario: Starting a job with Command Execution step.Scenario: Starting a job with Command Execution step3 ms3
 Scenario: Starting a job with Configuration Put and Bundle Start steps.And Bundles are requested2 ms622
 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 Configuration Put step.And A new job target item2 ms622
 Scenario: Starting a job with Configuration Put step.Scenario: Starting a job with Configuration Put step3 ms3
 Scenario: Starting a job with Package Install and Bundle Start steps.And Bundles are requested1 ms622
 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 Install step.Scenario: Starting a job with Package Install step5 ms3
 Scenario: Starting a job with Package Install step.Then Device status is "DISCONNECTED"3 ms1
 Scenario: Starting a job with Package Uninstall and Bundle Start steps.And Package named org.eclipse.kura.example.beacon with version 1.0.300 is 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 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 two Bundle Start steps.And Bundles are requested1 ms622
 Scenario: Starting a job with two Bundle Start steps.Scenario: Starting a job with two Bundle Start steps2 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: 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 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 Asset Write and Bundle Start steps 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 Asset Write 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 Start step and multiple devices.Then I count 22 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 Bundle Stop and Bundle Start step and multiple devices.Then I count 21 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 Bundle Stop step 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: Starting job with Command Execution and Bundle Start steps and multiple devices.Then I count 22 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 Command Execution step and multiple devices.Then I count 21 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 Configuration Put and Bundle Start steps 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 Configuration Put step and multiple devices.Then I count 22 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 Download/Install and Bundle Start steps and multiple devices.Then Device status is "DISCONNECTED"3 ms1
 Scenario: Starting job with Package Download/Install step and multiple devices.Scenario: Starting job with Package Download/Install step and multiple devices5 ms3
 Scenario: Starting job with Package Download/Install step and multiple devices.Then Device status is "DISCONNECTED"3 ms1
 Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device.Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device3 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 step and multiple device.Scenario: Starting job with Package Uninstall step and multiple device2 ms3
 Scenario: Starting job with Package Uninstall step and multiple device.Then I count 21 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 two Bundle Start steps and multiple devices.Then I count 22 ms3
 Scenario: Stealing link scenario.And Client named "client-2" is not connected6 ms622
 Scenario: Stealing link scenario.Scenario: Stealing link scenario8 ms3

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A newly created account must have some metadata3 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic11 ms2608
Scenario: Account based ClientInfo data check22 ms002424
Scenario: Account name must not be mutable5 ms0066
Scenario: Account wide metrics check23 ms002828
Scenario: Add Access Info domain permissions to new user22 ms002626
Scenario: Add Account permissions to the role in child account10 ms002828
Scenario: Add Credential domain permissions to new user15 ms001818
Scenario: Add Datastore domain permissions to new user0.17 sec001919
Scenario: Add Device Connection domain permissions to kapua-sys user13 ms001111
Scenario: Add Device Connection domain permissions to new user19 ms002323
Scenario: Add Device Event domain permissions to new user13 ms001616
Scenario: Add Device domain permissions to new user17 ms001717
Scenario: Add Domain domain permissions to kapua-sys user13 ms001717
Scenario: Add Domain domain permissions to new user13 ms003232
Scenario: Add Endpoint Permission To The User13 ms003030
Scenario: Add Endpoint_info permissions to the role in child account15 ms003030
Scenario: Add Group domain permissions to new user13 ms001717
Scenario: Add Group permissions to the role in child account12 ms002626
Scenario: Add Job domain permissions to new user24 ms001919
Scenario: Add Role domain permissions to new user17 ms001717
Scenario: Add Role permissions to the role in child account19 ms002626
Scenario: Add Scheduler Permissions With Job Permissions14 ms003131
Scenario: Add Scheduler Permissions Without Job Permissions22 ms002121
Scenario: Add Scheduler permissions to the role in child account14 ms003636
Scenario: Add Tag domain permissions to new user15 ms001515
Scenario: Add Tag permissions to the role in child account16 ms002626
Scenario: Add User domain permissions to new user17 ms002020
Scenario: Add account permissions to the role17 ms001919
Scenario: Add admin role to the user15 ms004444
Scenario: Add and delete Account permissions from the "admin" role18 ms001414
Scenario: Add and delete Device permissions from the "admin" role12 ms001414
Scenario: Add and delete Endpoint_info permissions from the "admin" role17 ms001414
Scenario: Add and delete Group permissions from the "admin" role16 ms001414
Scenario: Add and delete Job permissions from the "admin" role17 ms001414
Scenario: Add and delete Role permissions from the "admin" role13 ms001414
Scenario: Add and delete User permissions from the "admin" role18 ms001515
Scenario: Add datastore permissions to the role13 ms002727
Scenario: Add deleted role again17 ms001010
Scenario: Add device event permissions to the role15 ms003232
Scenario: Add device permissions to the role14 ms001919
Scenario: Add device permissions to the role in child account10 ms002626
Scenario: Add domain, user and access_info permissions to the role16 ms002323
Scenario: Add endpoint_info permissions to the role16 ms003131
Scenario: Add group permissions to the role19 ms001818
Scenario: Add job permissions to the role15 ms001919
Scenario: Add job permissions to the role in child account13 ms002626
Scenario: Add role permissions to the role23 ms001919
Scenario: Add same permission twice to the same role13 ms001414
Scenario: Add same role to user twice16 ms001313
Scenario: Add scheduler permissions to the role35 ms003131
Scenario: Add tag permissions to the role15 ms001818
Scenario: Add user permissions to the role14 ms001919
Scenario: Add user permissions to the role in child account13 ms002626
Scenario: Adding "Cron Job" Schedule With All Valid Parameters8 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value8 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format7 ms001111
Scenario: Adding "Cron Job" Schedule With End Date Only7 ms001010
Scenario: Adding "Cron Job" Schedule With End Time before Start time10 ms001212
Scenario: Adding "Cron Job" Schedule With Non-Unique End Date Parameter10 ms001616
Scenario: Adding "Cron Job" Schedule With Non-Unique Start Date Parameter7 ms001515
Scenario: Adding "Cron Job" Schedule With Start Date Only11 ms001111
Scenario: Adding "Cron Job" Schedule With the same Start and End time7 ms001212
Scenario: Adding "Cron Job" Schedule Without The Start Date Parameter9 ms001010
Scenario: Adding "Device Connect" Schedule With All Valid Parameters8 ms0088
Scenario: Adding "Device Connect" Schedule With End Date Only6 ms001010
Scenario: Adding "Device Connect" Schedule With End Time before Start time7 ms001111
Scenario: Adding "Device Connect" Schedule With Max Length Name7 ms0088
Scenario: Adding "Device Connect" Schedule With Min Length Name13 ms0088
Scenario: Adding "Device Connect" Schedule With Name Only9 ms0099
Scenario: Adding "Device Connect" Schedule With Non-Unique End Date Parameter9 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Name11 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Start Date Parameter10 ms001111
Scenario: Adding "Device Connect" Schedule With Start Date Only9 ms001010
Scenario: Adding "Device Connect" Schedule With the same Start and End time8 ms001111
Scenario: Adding "Device Connect" Schedule Without Name10 ms001010
Scenario: Adding "Device Connect" Schedule Without The Start Date Parameter13 ms0099
Scenario: Adding "Interval Job" Schedule With All Valid Parameters9 ms001010
Scenario: Adding "Interval Job" Schedule With End Date Only7 ms001010
Scenario: Adding "Interval Job" Schedule With End Time before Start time6 ms001212
Scenario: Adding "Interval Job" Schedule With Max Length Name11 ms001010
Scenario: Adding "Interval Job" Schedule With Min Length Name8 ms001010
Scenario: Adding "Interval Job" Schedule With Name Only4 ms001010
Scenario: Adding "Interval Job" Schedule With Non-Unique End Date Parameter8 ms001616
Scenario: Adding "Interval Job" Schedule With Non-Unique Name11 ms001515
Scenario: Adding "Interval Job" Schedule With Non-Unique Start Date Parameter8 ms001515
Scenario: Adding "Interval Job" Schedule With Null Interval Number6 ms001212
Scenario: Adding "Interval Job" Schedule With Start Date Only6 ms001111
Scenario: Adding "Interval Job" Schedule With the same Start and End time8 ms001212
Scenario: Adding "Interval Job" Schedule Without Interval Number12 ms001111
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter10 ms0099
Scenario: Adding "Interval Job" Schedule Without a Name8 ms001111
Scenario: Adding "admin" role to a user in a child account21 ms001414
Scenario: Adding "admin" role to multiple users15 ms001818
Scenario: Adding "admin" role twice12 ms001313
Scenario: Adding Account:Delete permission to user in same scope17 ms002525
Scenario: Adding Account:Delete permission to user in sub-account scope23 ms003030
Scenario: Adding Account:Read and Account:Delete permissions to user in same scope10 ms002121
Scenario: Adding Account:Read and Account:Write permissions to user in same scope16 ms001919
Scenario: Adding Account:Read permission to user in same scope33 ms002323
Scenario: Adding Account:Read permission to user in sub-account scope16 ms002929
Scenario: Adding Account:Write and Account:Delete permission to user in same scope16 ms002323
Scenario: Adding Account:Write permission to user in same scope12 ms002525
Scenario: Adding Account:Write permission to user in sub-account scope15 ms003131
Scenario: Adding Multiple Permissions To User17 ms002020
Scenario: Adding One Permission To User18 ms001111
Scenario: Adding Permissions To Child User17 ms001818
Scenario: Adding Permissions To Parallel User23 ms001818
Scenario: Adding Previously Deleted Permission21 ms002828
Scenario: Adding all Account permissions to user in same scope15 ms001717
Scenario: Adding all Account permissions to user in sub-account scope13 ms002424
Scenario: Adding existing roles to user23 ms001515
Scenario: Adding role from child account to user in new child account15 ms001515
Scenario: Adding role to multiple users in child account12 ms001818
Scenario: Adding same role twice to user in child account11 ms001515
Scenario: Adding the same role to user twice in child account8 ms001313
Scenario: B1 Broker publish to CTRL_ACC_REPLY11 ms2709
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed7 ms2709
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed6 ms2608
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI15 ms2709
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed10 ms2709
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed9 ms2608
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY9 ms2709
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY14 ms2709
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account14 ms2709
Scenario: B5 Broker publish to CTRL_ACC is not allowed6 ms2709
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed15 ms2709
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed20 ms2608
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI18 ms2709
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed7 ms2709
Scenario: Birth and applications event handling13 ms001212
Scenario: Birth and death message handling5 ms001212
Scenario: Birth and missing event handling8 ms001212
Scenario: Birth message handling from a new device14 ms001313
Scenario: Birth message handling from an existing device29 ms001212
Scenario: Captured date based ClientInfo data check26 ms003030
Scenario: Change role name so it is too short2 ms0066
Scenario: Change the account parent path4 ms0055
Scenario: Changing Client ID7 ms0099
Scenario: Changing Device Status To Disabled5 ms0099
Scenario: Changing Device Status To Enabled5 ms0099
Scenario: Changing description of a nonexisting role3 ms0077
Scenario: Changing job description to non-unique one5 ms0077
Scenario: Changing job description to the long one7 ms0066
Scenario: Changing job description to unique one4 ms0066
Scenario: Changing job description to very short one7 ms0077
Scenario: Changing job name to a long one without description9 ms0077
Scenario: Changing job name to a too long one without description5 ms0055
Scenario: Changing job name to a too short one without description4 ms0066
Scenario: Changing job name to contain invalid symbols in name without description7 ms0044
Scenario: Changing job name to contain permitted symbols in name without description6 ms0055
Scenario: Changing job name to non-unique one5 ms0088
Scenario: Changing job name to short one without description5 ms0077
Scenario: Changing job name to unique one8 ms0099
Scenario: Changing name of a nonexisting role2 ms0077
Scenario: Changing role description to a valid one2 ms0066
Scenario: Changing role name so it is too long3 ms0066
Scenario: Changing role name to contain special character2 ms0044
Scenario: Changing role name to null2 ms0066
Scenario: Changing role's name to a valid one2 ms0066
Scenario: Channel info queries based on datastore channel filters25 ms005050
Scenario: ChannelInfo client ID and topic data based on the client id26 ms002828
Scenario: ChannelInfo client ID based on the account id22 ms002626
Scenario: ChannelInfo last published date19 ms003030
Scenario: ChannelInfo topic data based on the account id24 ms002626
Scenario: Check account properties4 ms0044
Scenario: Check the Device Connection Domain data seetting3 ms0022
Scenario: Check the database cache coherency15 ms003030
Scenario: Check the mapping for message semantic topics25 ms003030
Scenario: Check the message store26 ms002020
Scenario: Check the sanity of the Device Connection Domain data initialization5 ms0022
Scenario: Client Id based ClientInfo data check15 ms002828
Scenario: Connect to the system and publish some data9 ms215522
Scenario: Connection Service factory sanity checks3 ms0022
Scenario: Count connections in empty scope6 ms0044
Scenario: Count connections in scope5 ms0055
Scenario: Count user4 ms0066
Scenario: Counting created roles items in the DB2 ms0055
Scenario: Create a valid job entry29 ms0066
Scenario: Create index with specific prefix9 ms001212
Scenario: Create multiple users4 ms0055
Scenario: Create same user in different accounts21 ms001515
Scenario: Create scheduler with correct end date7 ms0088
Scenario: Create scheduler with empty schedule name9 ms0088
Scenario: Create scheduler with end date before start date16 ms0099
Scenario: Create scheduler with invalid Retry Interval property7 ms0099
Scenario: Create scheduler with invalid cron job trigger property7 ms0099
Scenario: Create scheduler with invalid schedule name15 ms0088
Scenario: Create scheduler with short schedule name9 ms0088
Scenario: Create scheduler with too long schedule name14 ms0088
Scenario: Create scheduler with valid Retry Interval property6 ms0077
Scenario: Create scheduler with valid cron job trigger property6 ms0077
Scenario: Create scheduler with valid schedule name31 ms0066
Scenario: Create scheduler without Cron Job Trigger property12 ms0099
Scenario: Create scheduler without Retry Interval property7 ms0099
Scenario: Create scheduler without start date10 ms0077
Scenario: Create user that already exist5 ms0077
Scenario: Create user that has more than DB allowed length7 ms0055
Scenario: Create user with short name10 ms0055
Scenario: Create user with special characters in his name7 ms0055
Scenario: Creating A Device With Disabled Status7 ms0077
Scenario: Creating A Device With Enabled Status12 ms0077
Scenario: Creating A Device With Long Display Name4 ms0077
Scenario: Creating A Device With Long Name7 ms0077
Scenario: Creating A Device With Name Containing Invalid Symbols10 ms0088
Scenario: Creating A Device With Name Containing Permitted Symbols9 ms0077
Scenario: Creating A Device With No Name11 ms0088
Scenario: Creating A Device With Non-unique Display Name8 ms0077
Scenario: Creating A Device With Non-unique Name8 ms001010
Scenario: Creating A Device With Short Display Name11 ms0077
Scenario: Creating A Device With Short Name8 ms0077
Scenario: Creating A Device With Too Long Display Name6 ms0088
Scenario: Creating A Device With Too Long Name7 ms0088
Scenario: Creating A Device With Unique Name10 ms0099
Scenario: Creating a Access Group with invalid special symbols in name6 ms0044
Scenario: Creating a Device With Permitted Symbols in its Display Name14 ms0077
Scenario: Creating a Device With Unique Display Name5 ms0088
Scenario: Creating a job with name only10 ms0066
Scenario: Creating a job with null name13 ms0055
Scenario: Creating a job without name with valid description7 ms0055
Scenario: Creating a role name with allowed symbols in its name2 ms0055
Scenario: Creating a role with 255 characters long description4 ms0055
Scenario: Creating a role with a name and description that contain digits only2 ms0055
Scenario: Creating a role with forbidden symbols in its name0 ms0044
Scenario: Creating a role with name only2 ms0055
Scenario: Creating a role with null name3 ms0055
Scenario: Creating a role with regular name and very short description" as description cannot be too short, as even one character is enough3 ms0055
Scenario: Creating a role with special characters in the description2 ms0044
Scenario: Creating a role with the name that contains digits2 ms0055
Scenario: Creating a role with too long name1 ms0055
Scenario: Creating a role with too short name3 ms0055
Scenario: Creating a role with valid name and with too long description0 ms0033
Scenario: Creating a role wtih 255 characters long name6 ms0055
Scenario: Creating a valid Access Group with numbers in name4 ms0055
Scenario: Creating a valid Access Group with only numbers in name3 ms0055
Scenario: Creating a valid Access Group with unique name17 ms0055
Scenario: Creating a valid Access Group with valid special symbols in name4 ms0055
Scenario: Creating a valid role3 ms0055
Scenario: Creating an Access Group with empty name9 ms0044
Scenario: Creating an Access Group with long name5 ms0055
Scenario: Creating an Access Group with short name6 ms0055
Scenario: Creating an Access Group with too long name4 ms0044
Scenario: Creating an Access Group with too short name5 ms0044
Scenario: Creating an Access Group without name and with description3 ms0044
Scenario: Creating index with regular user13 ms002525
Scenario: Creating job with invalid symbols in name without description3 ms0044
Scenario: Creating job with long name and valid description5 ms0066
Scenario: Creating job with long name without description13 ms0066
Scenario: Creating job with numbers in name and valid description5 ms0066
Scenario: Creating job with numbers in name without description7 ms0066
Scenario: Creating job with permitted symbols in name without description9 ms0033
Scenario: Creating job with short name and valid job description5 ms0066
Scenario: Creating job with short name without description12 ms0066
Scenario: Creating job with too long name and valid description6 ms0055
Scenario: Creating job with too long name without description7 ms0055
Scenario: Creating job with too short name and valid description5 ms0055
Scenario: Creating job with too short name without description8 ms0055
Scenario: Creating job without name and without description7 ms0055
Scenario: Creating new device and tagging it with specific Tag8 ms001414
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag13 ms001616
Scenario: Creating non-unique Access Group7 ms0055
Scenario: Creating non-unique Access Group with unique description2 ms0055
Scenario: Creating non-unique job name with valid job description7 ms0077
Scenario: Creating tag18 ms0044
Scenario: Creating two indexes with daily index8 ms001717
Scenario: Creating two indexes with hourly index10 ms001717
Scenario: Creating two indexes with weekly index8 ms001717
Scenario: Creating two roles with the same description2 ms0066
Scenario: Creating two roles with the same name2 ms0077
Scenario: Creating unique Access Group with long description3 ms0055
Scenario: Creating unique Access Group with non-unique description6 ms0066
Scenario: Creating unique Access Group with numbers in description3 ms0055
Scenario: Creating unique Access Group with only numbers in description3 ms0055
Scenario: Creating unique Access Group with short description3 ms0055
Scenario: Creating unique Access Group with special symbols in description3 ms0044
Scenario: Creating unique Access Group with unique description3 ms0055
Scenario: Creating unique job with long description5 ms0066
Scenario: Creating unique job with non-unique description6 ms001010
Scenario: Creating unique job with short description6 ms0066
Scenario: Creating user17 ms0055
Scenario: D1 Device publish to CTRL_ACC_REPLY11 ms2709
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI14 ms2709
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed7 ms2709
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed14 ms2507
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY5 ms2709
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY11 ms2709
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account7 ms2709
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC10 ms2709
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI7 ms2709
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed8 ms2709
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed12 ms2709
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed10 ms2608
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed12 ms2709
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI11 ms2709
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed12 ms2709
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed14 ms2608
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY14 ms2709
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY7 ms2709
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account13 ms2709
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed9 ms2709
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed10 ms2709
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed10 ms2608
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI7 ms2709
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC7 ms2709
Scenario: DV1 Data view publish to CTRL_ACC_REPLY4 ms2709
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed6 ms2709
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed7 ms28010
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed9 ms2709
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed7 ms2709
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed12 ms2709
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed10 ms2608
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY13 ms2709
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY7 ms2709
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account10 ms2709
Scenario: DV5 Data view publish to CTRL_ACC is not allowed13 ms2709
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed7 ms2709
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed18 ms2608
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI7 ms2709
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed9 ms2709
Scenario: Delete Kapua system user3 ms0055
Scenario: Delete a connection from the database3 ms0088
Scenario: Delete a non existing connection5 ms0077
Scenario: Delete access role from user11 ms001212
Scenario: Delete an existing account3 ms0055
Scenario: Delete items based on query results31 ms008484
Scenario: Delete items by date ranges0.26 sec00132132
Scenario: Delete items by the datastore ID23 ms006666
Scenario: Delete nonexisting account3 ms0044
Scenario: Delete permissions from role25 ms001818
Scenario: Delete scheduler5 ms0088
Scenario: Delete scheduler which doesn't exist6 ms0055
Scenario: Delete the Kapua system account6 ms0055
Scenario: Delete user15 ms0066
Scenario: Delete user that doesn't exist2 ms0055
Scenario: Deleting "Cron Schedule" Triggering10 ms001313
Scenario: Deleting "Device Schedule" Triggering9 ms001111
Scenario: Deleting "Interval Schedule" Triggering12 ms001313
Scenario: Deleting Device With Disabled Status6 ms001010
Scenario: Deleting Device With Enabled Status7 ms001010
Scenario: Deleting a Permission16 ms002121
Scenario: Deleting a non-existing Access Group4 ms0066
Scenario: Deleting a role twice1 ms0077
Scenario: Deleting admin role17 ms0077
Scenario: Deleting an existing Access Group2 ms0055
Scenario: Deleting an existing Access Group and creating it again with the same name2 ms0077
Scenario: Deleting an existing role2 ms0066
Scenario: Deleting default permissions from admin role17 ms001212
Scenario: Deleting role after adding it to user13 ms001414
Scenario: Deleting role after it has been added to user in child account11 ms001616
Scenario: Deleting tag12 ms0044
Scenario: Deleting user in account that is higher in hierarchy17 ms002323
Scenario: Deleting user in account that is lower in hierarchy17 ms002424
Scenario: Device connection update8 ms0077
Scenario: Editing Access Group description to description with numbers3 ms0055
Scenario: Editing Access Group description to description with only numbers3 ms0055
Scenario: Editing Access Group description to description with special symbols4 ms0044
Scenario: Editing Access Group description to long description2 ms0055
Scenario: Editing Access Group description to non-unique one7 ms0055
Scenario: Editing Access Group description to short description3 ms0055
Scenario: Editing Access Group description to unique one3 ms0077
Scenario: Editing Access Group name to a long one2 ms0077
Scenario: Editing Access Group name to a too long one2 ms0055
Scenario: Editing Access Group name to empty name3 ms0055
Scenario: Editing Access Group name to name that contains numbers6 ms0077
Scenario: Editing Access Group name to name that contains only numbers2 ms0077
Scenario: Editing Access Group name to name with invalid special symbols in name0 ms0055
Scenario: Editing Access Group name to name with valid special symbols3 ms0077
Scenario: Editing Access Group name to non-unique one3 ms0066
Scenario: Editing Access Group name to short one4 ms0077
Scenario: Editing Access Group name to too short one3 ms0055
Scenario: Editing Access Group name to valid one4 ms0077
Scenario: Every account must have the default configuration items4 ms0033
Scenario: Executing Job And Then Restarting Device4 ms2331045
Scenario: Executing Job When Device Connected After End Date And Time6 ms2261038
Scenario: Executing Job When Device Connected After The Specified Start Date And Time5 ms2261038
Scenario: Executing Job When Device Connected Before End Date And Time5 ms2271039
Scenario: Executing Job When Device Connected Before The Specified Start Date And Time5 ms2251037
Scenario: Executing Job Without Steps5 ms2281040
Scenario: Find a connection by its IDs13 ms0066
Scenario: Find a connection by its client ID6 ms0066
Scenario: Find account by Id4 ms0044
Scenario: Find account by Ids9 ms0044
Scenario: Find account by name4 ms0044
Scenario: Find account by random Id5 ms0033
Scenario: Find all child accounts10 ms0033
Scenario: Find by name nonexisting account4 ms0033
Scenario: Find correct number of messages by corresponding metric9 ms4381658
Scenario: Find multiple users3 ms0055
Scenario: Find user by id4 ms0055
Scenario: Find user by its email3 ms0066
Scenario: Find user by its phone number3 ms0066
Scenario: Find user by name3 ms0055
Scenario: Find user by name that doesn't exist3 ms0033
Scenario: Find user with id and scope id that doesn't exist0 ms0033
Scenario: Finding all messages by selecting all metrics7 ms4201640
Scenario: Finding correct number of messages by corresponding two metrics8 ms4321652
Scenario: Finding messages with incorrect metric parameters6 ms4521672
Scenario: Finding user by expiration date in the future4 ms0055
Scenario: Finding user by expiration date in the past4 ms0066
Scenario: Finding user by expiration date in the present3 ms0066
Scenario: Generic connection query4 ms0088
Scenario: Get metadata3 ms0033
Scenario: Handle account creation15 ms0033
Scenario: Handle duplicate account names7 ms0055
Scenario: Handle null account name6 ms0044
Scenario: Handling of 2 birth messages13 ms001212
Scenario: Handling of a disconnect message from a non existing device7 ms001010
Scenario: I try to find a non-existing connection5 ms0066
Scenario: If user credential expiration date is before today, user can not login7 ms001414
Scenario: If user credential expiration date is today, user can not login it is day inclusive14 ms001414
Scenario: If user credential expiration date is tomorrow, user can login5 ms001313
Scenario: If user credential is in state disabled, user can not login9 ms001414
Scenario: If user credential is in state enabled, user can login7 ms001313
Scenario: If user expiration date is before today, user can not login10 ms001313
Scenario: If user expiration date is today, user can not login because expiration date was reached9 ms001313
Scenario: If user expiration date is tomorrow, user can login9 ms001212
Scenario: Init Security Context for all scenarios58 ms0012-3812-38
Scenario: Installing a package0 ms27413
Scenario: Interval Job" Schedule With Too Long Name7 ms001111
Scenario: It should not be possible to change the configuration items3 ms0055
Scenario: MetricsInfo client ID and topic data based on the client id26 ms003434
Scenario: MetricsInfo last published date23 ms004848
Scenario: Modify an existing account4 ms0044
Scenario: Modify nonexisting account3 ms0066
Scenario: Modifying Sub-account of a different parent account13 ms002525
Scenario: Negative scenario when client connects twice with same client id15 ms001111
Scenario: Positive scenario without stealing link19 ms001212
Scenario: Query based on message ordering26 ms002020
Scenario: Query based on metrics ordering19 ms002020
Scenario: Query before schema search18 ms008282
Scenario: Query user5 ms0066
Scenario: Querying Other Items With All Account Permissions12 ms003939
Scenario: Regular connection22 ms0077
Scenario: Reset Security Context for all scenarios55 ms0012-3812-38
Scenario: Restarting a job with Asset Write and Bundle Start steps4 ms2151128
Scenario: Restarting a job with Command Execution and Bundle Start steps3 ms2151128
Scenario: Restarting a job with Configuration Put and Bundle Start steps3 ms2151128
Scenario: Restarting a job with Package Uninstall and Bundle Start steps8 ms2151128
Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices5 ms2161331
Scenario: Restarting job with Asset Write step5 ms2121125
Scenario: Restarting job with Asset Write step and multiple devices4 ms2131328
Scenario: Restarting job with Bundle Start step5 ms2121125
Scenario: Restarting job with Bundle Start step and multiple devices3 ms2121327
Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices5 ms2161331
Scenario: Restarting job with Bundle Stop and Bundle Start steps3 ms2161129
Scenario: Restarting job with Bundle Stop step3 ms2121125
Scenario: Restarting job with Bundle Stop step and multiple devices4 ms2121327
Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices4 ms2161331
Scenario: Restarting job with Command Execution step5 ms2121125
Scenario: Restarting job with Command Execution step and multiple devices3 ms2121327
Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices5 ms2161331
Scenario: Restarting job with Configuration Put step3 ms2121125
Scenario: Restarting job with Configuration Put step and multiple devices1 ms2121327
Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices11 ms4312459
Scenario: Restarting job with Package Download/Install step and multiple devices4 ms2121327
Scenario: Restarting job with Package Install step4 ms2121125
Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device3 ms2161331
Scenario: Restarting job with Package Uninstall step3 ms2121125
Scenario: Restarting job with Package Uninstall step and multiple device7 ms2121327
Scenario: Restarting job with two Bundle Start steps3 ms2161129
Scenario: Restarting job with two Bundle Start steps and multiple devices3 ms2161331
Scenario: Search By Client ID And Get Multiple Matches24 ms003737
Scenario: Search By Client ID And Get No Matches9 ms001010
Scenario: Search By Client ID And Get One Match6 ms0088
Scenario: Search By Client ID and Display Name11 ms001212
Scenario: Search By Client ID and Serial Number8 ms001212
Scenario: Search By Client ID and Status5 ms001212
Scenario: Search By Client ID, Display Name and Serial Number7 ms001212
Scenario: Search By Client ID, Display Name and Status6 ms001212
Scenario: Search By Client ID, Display Name, Serial Number and Status5 ms001212
Scenario: Search By Device Status And Get No Matches13 ms0088
Scenario: Search By Device's Display Name And Get One Match16 ms0088
Scenario: Search By Display Name and Serial Number7 ms001212
Scenario: Search By Display Name and Status17 ms001212
Scenario: Search By Full Client ID And Get One Match11 ms001010
Scenario: Search By Non-existing Client ID And Get No Matches6 ms0088
Scenario: Search By One Letter Of Display Name6 ms0088
Scenario: Search By One Letter Of Serial Number11 ms001212
Scenario: Search By Serial Number And Get Multiple Matches12 ms001414
Scenario: Search By Serial Number And Get No Matches4 ms001010
Scenario: Search By Serial Number And Get One Match8 ms001111
Scenario: Search By Serial Number and Status8 ms001212
Scenario: Search By Serial Number, Display Name and Status8 ms001212
Scenario: Search By Specific Serial Number8 ms001010
Scenario: Search By Status And Get Multiple Matches8 ms001010
Scenario: Search by Device Status And Get One Match6 ms001010
Scenario: Search for a non existent client ID6 ms0066
Scenario: Send BIRTH message and then DC message14 ms210315
Scenario: Send BIRTH message and then DC message while broker ip is NOT set26 ms0066
Scenario: Send BIRTH message and then DC message while broker ip is set by System9 ms2248
Scenario: Send BIRTH message and then DC message while broker ip is set by config file4 ms2248
Scenario: Set environment variables0.23 sec0049-1249-12
Scenario: Setting configuration without mandatory items must raise an error3 ms0055
Scenario: Simple positive scenario for creating daily index8 ms001414
Scenario: Simple positive scenario for creating default - weekly index10 ms001212
Scenario: Simple positive scenario for creating hourly index9 ms001414
Scenario: Start broker for all scenarios79 ms34-100034-10
Scenario: Start datastore for all scenarios1.1 sec003030
Scenario: Start event broker for all scenarios0.47 sec0040-1040-10
Scenario: Starting a job with Asset Write and Bundle Start steps5 ms227736
Scenario: Starting a job with Asset Write step5 ms2121125
Scenario: Starting a job with Bundle Start step3 ms225734
Scenario: Starting a job with Bundle Stop and Bundle Start steps5 ms230739
Scenario: Starting a job with Bundle Stop step4 ms226735
Scenario: Starting a job with Command Execution and Bundle Start steps5 ms228737
Scenario: Starting a job with Command Execution step5 ms2121125
Scenario: Starting a job with Configuration Put and Bundle Start steps5 ms228737
Scenario: Starting a job with Configuration Put step6 ms2121125
Scenario: Starting a job with Package Install and Bundle Start steps3 ms229839
Scenario: Starting a job with Package Install step7 ms2201032
Scenario: Starting a job with Package Uninstall and Bundle Start steps4 ms226836
Scenario: Starting a job with Package Uninstall step3 ms223833
Scenario: Starting a job with two Bundle Start steps3 ms230739
Scenario: Starting and stopping the simulator should create a device entry and properly set its status10 ms214420
Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices4 ms2171332
Scenario: Starting job with Asset Write step and multiple devices5 ms2131328
Scenario: Starting job with Bundle Start step and multiple devices4 ms2131328
Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices3 ms2171332
Scenario: Starting job with Bundle Stop step and multiple devices4 ms2131328
Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices5 ms2171332
Scenario: Starting job with Command Execution step and multiple devices3 ms2131328
Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices5 ms2171332
Scenario: Starting job with Configuration Put step and multiple devices4 ms2131328
Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices7 ms2261038
Scenario: Starting job with Package Download/Install step and multiple devices9 ms2221034
Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device6 ms2171332
Scenario: Starting job with Package Uninstall step and multiple device3 ms2131227
Scenario: Starting job with two Bundle Start steps and multiple devices5 ms2171332
Scenario: Stealing link scenario14 ms2141228
Scenario: Stop broker after all scenarios0.39 sec0036-1036-10
Scenario: Stop datastore after all scenarios0.29 sec003030
Scenario: Stop event broker for all scenarios0.45 sec0040-1040-10
Scenario: Test account query3 ms0044
Scenario: Test the message store with server timestamp indexing18 ms002626
Scenario: Test the message store with timestamp indexing17 ms002626
Scenario: The Client ID is case sensitive5 ms0088
Scenario: To be defined9 ms001313
Scenario: Translating "CommandRequestMessage" to "KuraRequestMessage"24 ms0044
Scenario: Translating CommandRequestMessage to null13 ms0044
Scenario: Translating empty message to empty message8 ms0044
Scenario: Translating from "AssetRequestMessage" to "AssetResponseMessage"6 ms0044
Scenario: Translating null to KuraRequestMessage6 ms0044
Scenario: Translation of kura data message with valid channel and without body and metrics into mqtt message3 ms0055
Scenario: Translation of kura data message with valid channel, body and metrics into mqtt message3 ms0055
Scenario: Translation of kura data message with valid channel, metrics and without body into mqtt message3 ms0055
Scenario: Translation of mqtt message with empty payload into kura data message3 ms0066
Scenario: Translation of mqtt message with invalid payload and invalid topic into kura response message3 ms0055
Scenario: Translation of mqtt message with invalid payload and valid topic into kura data message5 ms0066
Scenario: Translation of mqtt message with invalid payload and valid topic into kura response message5 ms0066
Scenario: Translation of mqtt message with valid payload and invalid topic into kura response message4 ms0055
Scenario: Translation of mqtt message with valid payload and valid topic into kura data message5 ms0066
Scenario: Translation of mqtt message with valid payload and valid topic into kura response message3 ms0066
Scenario: Try to add two different roles with same permissions20 ms002121
Scenario: Try to change an existing connection ID6 ms0077
Scenario: Try to find users granted to "admin" role12 ms001212
Scenario: Try to find users that have assigned specific role12 ms001212
Scenario: Try to modify the connection client ID11 ms0077
Scenario: Update schedule which doesn't exist5 ms0055
Scenario: Update scheduler end date6 ms0099
Scenario: Update scheduler name7 ms0088
Scenario: Update scheduler start date5 ms0088
Scenario: Update trigger definition8 ms0088
Scenario: Update user6 ms0077
Scenario: Update user that doesn't exist5 ms0055
Scenario: User locking itself out by using out login attempts9 ms001616
Scenario: User locking itself out with failed attempts and not waiting to unlock13 ms001717
Scenario: User locking itself out with failed attempts and waiting to unlock7 ms001717
Scenario: User login with wrong pass, but with enough time between login failures5 ms001919
Scenario: User not locking itself out by using less than max failed login attempts4 ms001717