Test Result : (root)

500 failures (-30) , 3,983 skipped (-1306)
11,963 tests (-4273)
Took 11 sec.

All Failed Tests

Test NameDurationAge
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Given Mqtt Device is started2 ms4
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic4 ms4
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Given Mqtt Device is started10 ms4
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY13 ms4
 Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.Given Mqtt Device is started5 ms4
 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 allowed7 ms4
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Given Mqtt Device is started2 ms4
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed4 ms4
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started3 ms4
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI5 ms4
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started7 ms4
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed8 ms4
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started2 ms4
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms4
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started2 ms4
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY4 ms4
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started7 ms4
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY9 ms4
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started5 ms4
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account9 ms4
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.Given Mqtt Device is started3 ms4
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.Scenario: B5 Broker publish to CTRL_ACC is not allowed5 ms4
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started2 ms4
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed5 ms4
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Given Mqtt Device is started4 ms4
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed6 ms4
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started4 ms4
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI6 ms4
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started2 ms4
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed4 ms4
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data6 ms4
 Scenario: Connect to the system and publish some data.Then Device sim-1 for account kapua-sys is registered after 5 seconds4 ms4
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Given Mqtt Device is started3 ms4
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY4 ms4
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started5 ms4
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI7 ms4
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started4 ms4
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms4
 Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started5 ms4
 Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed7 ms4
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started3 ms4
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY5 ms4
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started1 ms4
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY3 ms4
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started3 ms4
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account5 ms4
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Given Mqtt Device is started2 ms4
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Scenario: D5 Device subscribe - publish - admin on CTRL_ACC4 ms4
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started3 ms4
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI5 ms4
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started21 ms4
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed21 ms4
 Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.Given Mqtt Device is started4 ms4
 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 ms4
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Given Mqtt Device is started5 ms4
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed6 ms4
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Given Mqtt Device is started2 ms4
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed8 ms4
 Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started3 ms4
 Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI6 ms4
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started2 ms4
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed7 ms4
 Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started4 ms4
 Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed5 ms4
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started0 ms4
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY1 ms4
 Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started2 ms4
 Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY4 ms4
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started3 ms4
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account4 ms4
 Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Given Mqtt Device is started2 ms4
 Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Scenario: DM5 Data manage publish to CTRL_ACC is not allowed6 ms4
 Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started5 ms4
 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 ms4
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Given Mqtt Device is started5 ms4
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed6 ms4
 Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started5 ms4
 Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI7 ms4
 Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Given Mqtt Device is started3 ms4
 Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC5 ms4
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Given Mqtt Device is started3 ms4
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY4 ms4
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Given Mqtt Device is started3 ms4
 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 ms4
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Given Mqtt Device is started2 ms4
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed4 ms4
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Given Mqtt Device is started2 ms4
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed4 ms4
 Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed.Given Mqtt Device is started1 ms4
 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 allowed3 ms4
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started3 ms4
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms4
 Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started0 ms4
 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 allowed1 ms4
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started3 ms4
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY4 ms4
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started3 ms4
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY4 ms4
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started3 ms4
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account5 ms4
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Given Mqtt Device is started2 ms4
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Scenario: DV5 Data view publish to CTRL_ACC is not allowed3 ms4
 Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started4 ms4
 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 allowed7 ms4
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Given Mqtt Device is started3 ms4
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed4 ms4
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started3 ms4
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI4 ms4
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started3 ms4
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed5 ms4
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device5 ms4
 Scenario: Executing Job And Then Restarting Device.When I search for events from device "rpione3" in account "kapua-sys"3 ms617
 Scenario: Executing Job When Device Connected After End Date And Time.Scenario: Executing Job When Device Connected After End Date And Time2 ms4
 Scenario: Executing Job When Device Connected After End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms617
 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 ms4
 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 ms617
 Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time3 ms4
 Scenario: Executing Job When Device Connected Before End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"3 ms617
 Scenario: Executing Job When Device Connected Before The Specified Start Date And Time.Scenario: Executing Job When Device Connected Before The Specified Start Date And Time2 ms4
 Scenario: Executing Job When Device Connected Before The Specified Start Date And Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms617
 Scenario: Executing Job Without Steps.Scenario: Executing Job Without Steps3 ms4
 Scenario: Executing Job Without Steps.When I search for events from device "rpione3" in account "kapua-sys"2 ms617
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric2 ms4
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric3 ms4
 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"3 ms4
 Scenario: Find correct number of messages by corresponding metric.Then I prepare a number of messages with the following details and remember the list as "TestMessages"1 ms4
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics5 ms4
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics3 ms4
 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 ms4
 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"5 ms4
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics3 ms4
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics3 ms4
 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 ms4
 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 ms4
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters2 ms4
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters1 ms4
 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 ms4
 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 ms4
 Scenario: Installing a package.Scenario: Installing a package0 ms4
 Scenario: Installing a package.Then Device sim-1 for account kapua-sys is registered after 5 seconds0 ms4
 Scenario: Restarting a job with Asset Write and Bundle Start steps.And A new job target item1 ms617
 Scenario: Restarting a job with Asset Write and Bundle Start steps.Scenario: Restarting a job with Asset Write and Bundle Start steps2 ms4
 Scenario: Restarting a job with Command Execution and Bundle Start steps.And A new job target item1 ms617
 Scenario: Restarting a job with Command Execution and Bundle Start steps.Scenario: Restarting a job with Command Execution and Bundle Start steps2 ms4
 Scenario: Restarting a job with Configuration Put and Bundle Start steps.And A new job target item1 ms617
 Scenario: Restarting a job with Configuration Put and Bundle Start steps.Scenario: Restarting a job with Configuration Put and Bundle Start steps2 ms4
 Scenario: Restarting a job with Package Uninstall and Bundle Start steps.And A new job target item17 ms617
 Scenario: Restarting a job with Package Uninstall and Bundle Start steps.Scenario: Restarting a job with Package Uninstall and Bundle Start steps17 ms4
 Scenario: Restarting a job with invalid Configuration Put and multiple devices two times.Scenario: Restarting a job with invalid Configuration Put and multiple devices two times3 ms4
 Scenario: Restarting a job with invalid Configuration Put and multiple devices two times.Then Configuration is requested1 ms617
 Scenario: Restarting a job with invalid Configuration Put step two times.Scenario: Restarting a job with invalid Configuration Put step two times3 ms4
 Scenario: Restarting a job with invalid Configuration Put step two times.Then Configuration is requested2 ms617
 Scenario: Restarting a job with invalid Package Install step and multiple devices two times.And A new job target item1 ms4
 Scenario: Restarting a job with invalid Package Install step and multiple devices two times.Scenario: Restarting a job with invalid Package Install step and multiple devices two times2 ms4
 Scenario: Restarting a job with invalid Package Install step two times.Scenario: Restarting a job with invalid Package Install step two times3 ms4
 Scenario: Restarting a job with invalid Package Install step two times.When I search for events from device "rpione3" in account "kapua-sys"2 ms617
 Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times.And The type of the last event is "DEPLOY"1 ms617
 Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times.Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times2 ms4
 Scenario: Restarting a job with invalid Package Uninstall step two times.And I search for events from device "rpione3" in account "kapua-sys"1 ms617
 Scenario: Restarting a job with invalid Package Uninstall step two times.Scenario: Restarting a job with invalid Package Uninstall step two times2 ms4
 Scenario: Restarting a job with valid Configuration Put step and multiple devices two times.Scenario: Restarting a job with valid Configuration Put step and multiple devices two times4 ms4
 Scenario: Restarting a job with valid Configuration Put step and multiple devices two times.Then Configuration is requested2 ms617
 Scenario: Restarting a job with valid Configuration Put step two times.Scenario: Restarting a job with valid Configuration Put step two times2 ms4
 Scenario: Restarting a job with valid Configuration Put step two times.Then Configuration is requested2 ms617
 Scenario: Restarting a job with valid Package Install step and multiple devices two times.And I restart a job2 ms617
 Scenario: Restarting a job with valid Package Install step and multiple devices two times.Scenario: Restarting a job with valid Package Install step and multiple devices two times4 ms4
 Scenario: Restarting a job with valid Package Install step two times.Scenario: Restarting a job with valid Package Install step two times2 ms4
 Scenario: Restarting a job with valid Package Install step two times.When I search for events from device "rpione3" in account "kapua-sys"2 ms617
 Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times.And The type of the last event is "DEPLOY"1 ms617
 Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times.Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times2 ms4
 Scenario: Restarting a job with valid Package Uninstall step two times.And I search for events from device "rpione3" in account "kapua-sys"1 ms617
 Scenario: Restarting a job with valid Package Uninstall step two times.Scenario: Restarting a job with valid Package Uninstall step two times2 ms4
 Scenario: Restarting job With invalid Asset Write and multiple two times.And Device assets are requested1 ms617
 Scenario: Restarting job With invalid Asset Write and multiple two times.Scenario: Restarting job With invalid Asset Write and multiple two times1 ms4
 Scenario: Restarting job With valid Asset Write step two times.And Device assets are requested1 ms617
 Scenario: Restarting job With valid Asset Write step two times.Scenario: Restarting job With valid Asset Write step two times2 ms4
 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 ms4
 Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices.Then I count 22 ms4
 Scenario: Restarting job with Asset Write step.And A new job target item1 ms617
 Scenario: Restarting job with Asset Write step.Scenario: Restarting job with Asset Write step2 ms4
 Scenario: Restarting job with Asset Write step and multiple devices.Scenario: Restarting job with Asset Write step and multiple devices3 ms4
 Scenario: Restarting job with Asset Write step and multiple devices.Then I count 22 ms4
 Scenario: Restarting job with Bundle Start step.And A new job target item1 ms617
 Scenario: Restarting job with Bundle Start step.Scenario: Restarting job with Bundle Start step5 ms4
 Scenario: Restarting job with Bundle Start step and multiple devices.Scenario: Restarting job with Bundle Start step and multiple devices2 ms4
 Scenario: Restarting job with Bundle Start step and multiple devices.Then I count 21 ms4
 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 devices0 ms4
 Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices.Then I count 20 ms4
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.And A new job target item1 ms617
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.Scenario: Restarting job with Bundle Stop and Bundle Start steps2 ms4
 Scenario: Restarting job with Bundle Stop step.And A new job target item2 ms617
 Scenario: Restarting job with Bundle Stop step.Scenario: Restarting job with Bundle Stop step2 ms4
 Scenario: Restarting job with Bundle Stop step and multiple devices.Scenario: Restarting job with Bundle Stop step and multiple devices2 ms4
 Scenario: Restarting job with Bundle Stop step and multiple devices.Then I count 22 ms4
 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 ms4
 Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices.Then I count 21 ms4
 Scenario: Restarting job with Command Execution step.And A new job target item2 ms617
 Scenario: Restarting job with Command Execution step.Scenario: Restarting job with Command Execution step3 ms4
 Scenario: Restarting job with Command Execution step and multiple devices.Scenario: Restarting job with Command Execution step and multiple devices3 ms4
 Scenario: Restarting job with Command Execution step and multiple devices.Then I count 22 ms4
 Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices.Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices2 ms4
 Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices.Then I count 22 ms4
 Scenario: Restarting job with Configuration Put step.And A new job target item4 ms617
 Scenario: Restarting job with Configuration Put step.Scenario: Restarting job with Configuration Put step4 ms4
 Scenario: Restarting job with Configuration Put step and multiple devices.Scenario: Restarting job with Configuration Put step and multiple devices2 ms4
 Scenario: Restarting job with Configuration Put step and multiple devices.Then I count 22 ms4
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.And A new job target item2 ms617
 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 ms4
 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 ms4
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.Then I count 22 ms4
 Scenario: Restarting job with Package Download/Install step and multiple devices.Scenario: Restarting job with Package Download/Install step and multiple devices3 ms4
 Scenario: Restarting job with Package Download/Install step and multiple devices.Then I count 22 ms4
 Scenario: Restarting job with Package Install step.And A new job target item3 ms617
 Scenario: Restarting job with Package Install step.Scenario: Restarting job with Package Install step4 ms4
 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 ms4
 Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device.Then I count 21 ms4
 Scenario: Restarting job with Package Uninstall step.And A new job target item2 ms617
 Scenario: Restarting job with Package Uninstall step.Scenario: Restarting job with Package Uninstall step3 ms4
 Scenario: Restarting job with Package Uninstall step and multiple device.Scenario: Restarting job with Package Uninstall step and multiple device3 ms4
 Scenario: Restarting job with Package Uninstall step and multiple device.Then I count 23 ms4
 Scenario: Restarting job with invalid Asset Write step two times.And Device assets are requested2 ms617
 Scenario: Restarting job with invalid Asset Write step two times.Scenario: Restarting job with invalid Asset Write step two times3 ms4
 Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times.And Bundles are requested2 ms4
 Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times.Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times3 ms4
 Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times.And Bundles are requested2 ms4
 Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times.Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times2 ms4
 Scenario: Restarting job with invalid Bundle Start step and multiple devices two times.And Bundles are requested2 ms4
 Scenario: Restarting job with invalid Bundle Start step and multiple devices two times.Scenario: Restarting job with invalid Bundle Start step and multiple devices two times2 ms4
 Scenario: Restarting job with invalid Bundle Start step two times.And Bundles are requested2 ms4
 Scenario: Restarting job with invalid Bundle Start step two times.Scenario: Restarting job with invalid Bundle Start step two times2 ms4
 Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times.And Bundles are requested1 ms4
 Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times.Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times2 ms4
 Scenario: Restarting job with invalid Bundle Stop step two times.And Bundles are requested1 ms4
 Scenario: Restarting job with invalid Bundle Stop step two times.Scenario: Restarting job with invalid Bundle Stop step two times2 ms4
 Scenario: Restarting job with invalid Command Execution and Package Install step two times.And Command pwd is executed3 ms4
 Scenario: Restarting job with invalid Command Execution and Package Install step two times.Scenario: Restarting job with invalid Command Execution and Package Install step two times4 ms4
 Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times.And Command pwd is executed2 ms4
 Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times.Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times3 ms4
 Scenario: Restarting job with invalid Command Execution step and multiple devices two times.And Command pwd is executed1 ms4
 Scenario: Restarting job with invalid Command Execution step and multiple devices two times.Scenario: Restarting job with invalid Command Execution step and multiple devices two times2 ms4
 Scenario: Restarting job with invalid Command Execution step two times.Scenario: Restarting job with invalid Command Execution step two times3 ms4
 Scenario: Restarting job with invalid Command Execution step two times.When I search for events from device "rpione3" in account "kapua-sys"2 ms617
 Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times.Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times3 ms4
 Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times.Then Configuration is requested2 ms617
 Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times.Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times3 ms4
 Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times.Then Configuration is requested2 ms617
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times.And Device assets are requested2 ms617
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times.Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times2 ms4
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times.And Device assets are requested2 ms617
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times.Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times3 ms4
 Scenario: Restarting job with two Bundle Start steps.And A new job target item1 ms617
 Scenario: Restarting job with two Bundle Start steps.Scenario: Restarting job with two Bundle Start steps2 ms4
 Scenario: Restarting job with two Bundle Start steps and multiple devices.Scenario: Restarting job with two Bundle Start steps and multiple devices3 ms4
 Scenario: Restarting job with two Bundle Start steps and multiple devices.Then I count 22 ms4
 Scenario: Restarting job with valid Asset Write step and multiple devices two times.And Device assets are requested1 ms617
 Scenario: Restarting job with valid Asset Write step and multiple devices two times.Scenario: Restarting job with valid Asset Write step and multiple devices two times2 ms4
 Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times.And Bundles are requested1 ms4
 Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times.Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times2 ms4
 Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times.And Bundles are requested2 ms4
 Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times.Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times3 ms4
 Scenario: Restarting job with valid Bundle Start step and multiple devices two times.And Bundles are requested2 ms4
 Scenario: Restarting job with valid Bundle Start step and multiple devices two times.Scenario: Restarting job with valid Bundle Start step and multiple devices two times3 ms4
 Scenario: Restarting job with valid Bundle Start step two times.And Bundles are requested2 ms4
 Scenario: Restarting job with valid Bundle Start step two times.Scenario: Restarting job with valid Bundle Start step two times3 ms4
 Scenario: Restarting job with valid Bundle Stop step and multiple devices two times.And Bundles are requested2 ms4
 Scenario: Restarting job with valid Bundle Stop step and multiple devices two times.Scenario: Restarting job with valid Bundle Stop step and multiple devices two times2 ms4
 Scenario: Restarting job with valid Bundle Stop step two times.And Bundles are requested1 ms4
 Scenario: Restarting job with valid Bundle Stop step two times.Scenario: Restarting job with valid Bundle Stop step two times2 ms4
 Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times.And Command pwd is executed3 ms4
 Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times.Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times3 ms4
 Scenario: Restarting job with valid Command Execution and Package Install steps two times.And Command pwd is executed2 ms4
 Scenario: Restarting job with valid Command Execution and Package Install steps two times.Scenario: Restarting job with valid Command Execution and Package Install steps two times2 ms4
 Scenario: Restarting job with valid Command Execution step and multiple devices two times.And Command pwd is executed2 ms4
 Scenario: Restarting job with valid Command Execution step and multiple devices two times.Scenario: Restarting job with valid Command Execution step and multiple devices two times2 ms4
 Scenario: Restarting job with valid Command Execution step two times.Scenario: Restarting job with valid Command Execution step two times2 ms4
 Scenario: Restarting job with valid Command Execution step two times.When I search for events from device "rpione3" in account "kapua-sys"1 ms617
 Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times.Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times4 ms4
 Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times.Then Configuration is requested3 ms617
 Scenario: Restarting job with valid Configuration Put and Command Execution steps two times.Scenario: Restarting job with valid Configuration Put and Command Execution steps two times5 ms4
 Scenario: Restarting job with valid Configuration Put and Command Execution steps two times.Then Configuration is requested3 ms617
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times.And Device assets are requested2 ms617
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times.Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times3 ms4
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times.And Device assets are requested1 ms617
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times.Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times2 ms4
 Scenario: Send BIRTH message and then DC message.And I login as user with name "kapua-sys" and password "kapua-password"4 ms4
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message6 ms4
 Scenario: Send BIRTH message and then DC message while broker ip is set by System.Scenario: Send BIRTH message and then DC message while broker ip is set by System4 ms4
 Scenario: Send BIRTH message and then DC message while broker ip is set by System.Then Device is connected with "localhost" server ip3 ms4
 Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Scenario: Send BIRTH message and then DC message while broker ip is set by config file3 ms4
 Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Then Device is connected with "localhost" server ip2 ms4
 Scenario: Start broker for all scenarios.Given Start Broker1 ms4
 Scenario: Start broker for all scenarios.Given Start Broker13 ms4
 Scenario: Start broker for all scenarios.Given Start Broker2 ms4
 Scenario: Start broker for all scenarios.Given Start Broker2 ms4
 Scenario: Start broker for all scenarios.Given Start Broker2 ms4
 Scenario: Start broker for all scenarios.Given Start Broker1 ms4
 Scenario: Start broker for all scenarios.Given Start Broker1 ms4
 Scenario: Start broker for all scenarios.Given Start Broker1 ms4
 Scenario: Start broker for all scenarios.Given Start Broker1 ms4
 Scenario: Start broker for all scenarios.Given Start Broker2 ms4
 Scenario: Start broker for all scenarios.Given Start Broker2 ms4
 Scenario: Start broker for all scenarios.Given Start Broker1 ms4
 Scenario: Start broker for all scenarios.Given Start Broker1 ms4
 Scenario: Start broker for all scenarios.Given Start Broker2 ms4
 Scenario: Start broker for all scenarios.Given Start Broker2 ms4
 Scenario: Start broker for all scenarios.Given Start Broker2 ms4
 Scenario: Start broker for all scenarios.Given Start Broker1 ms4
 Scenario: Start broker for all scenarios.Given Start Broker2 ms4
 Scenario: Start broker for all scenarios.Given Start Broker2 ms4
 Scenario: Start broker for all scenarios.Given Start Broker2 ms4
 Scenario: Start broker for all scenarios.Given Start Broker1 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios14 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms4
 Scenario: Starting a job with Asset Write and Bundle Start steps.And Bundles are requested2 ms617
 Scenario: Starting a job with Asset Write and Bundle Start steps.Scenario: Starting a job with Asset Write and Bundle Start steps2 ms4
 Scenario: Starting a job with Asset Write step.And A new job target item2 ms617
 Scenario: Starting a job with Asset Write step.Scenario: Starting a job with Asset Write step3 ms4
 Scenario: Starting a job with Bundle Start step.And Bundles are requested1 ms617
 Scenario: Starting a job with Bundle Start step.Scenario: Starting a job with Bundle Start step2 ms4
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.And Bundles are requested2 ms617
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.Scenario: Starting a job with Bundle Stop and Bundle Start steps2 ms4
 Scenario: Starting a job with Bundle Stop step.And Bundles are requested1 ms617
 Scenario: Starting a job with Bundle Stop step.Scenario: Starting a job with Bundle Stop step2 ms4
 Scenario: Starting a job with Command Execution and Bundle Start steps.And Bundles are requested0 ms617
 Scenario: Starting a job with Command Execution and Bundle Start steps.Scenario: Starting a job with Command Execution and Bundle Start steps0 ms4
 Scenario: Starting a job with Command Execution step.And A new job target item2 ms617
 Scenario: Starting a job with Command Execution step.Scenario: Starting a job with Command Execution step3 ms4
 Scenario: Starting a job with Configuration Put and Bundle Start steps.And Bundles are requested8 ms617
 Scenario: Starting a job with Configuration Put and Bundle Start steps.Scenario: Starting a job with Configuration Put and Bundle Start steps8 ms4
 Scenario: Starting a job with Configuration Put step.And A new job target item1 ms617
 Scenario: Starting a job with Configuration Put step.Scenario: Starting a job with Configuration Put step2 ms4
 Scenario: Starting a job with Package Install and Bundle Start steps.And Bundles are requested1 ms617
 Scenario: Starting a job with Package Install and Bundle Start steps.Scenario: Starting a job with Package Install and Bundle Start steps2 ms4
 Scenario: Starting a job with Package Install step.Scenario: Starting a job with Package Install step3 ms4
 Scenario: Starting a job with Package Install step.Then Device status is "DISCONNECTED"1 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 ms4
 Scenario: Starting a job with Package Uninstall and Bundle Start steps.Scenario: Starting a job with Package Uninstall and Bundle Start steps2 ms4
 Scenario: Starting a job with Package Uninstall step.And Package named org.eclipse.kura.example.beacon with version 1.0.300 is received1 ms4
 Scenario: Starting a job with Package Uninstall step.Scenario: Starting a job with Package Uninstall step2 ms4
 Scenario: Starting a job with invalid Asset Write step.And Device assets are requested1 ms617
 Scenario: Starting a job with invalid Asset Write step.Scenario: Starting a job with invalid Asset Write step2 ms4
 Scenario: Starting a job with invalid Asset Write step and multiple targets.And Device assets are requested1 ms617
 Scenario: Starting a job with invalid Asset Write step and multiple targets.Scenario: Starting a job with invalid Asset Write step and multiple targets2 ms4
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps.And Bundles are requested3 ms4
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps.Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps3 ms4
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices.And Bundles are requested1 ms4
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices.Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices2 ms4
 Scenario: Starting a job with invalid Bundle Start step.And Bundles are requested2 ms4
 Scenario: Starting a job with invalid Bundle Start step.Scenario: Starting a job with invalid Bundle Start step3 ms4
 Scenario: Starting a job with invalid Bundle Stop step.And Bundles are requested2 ms4
 Scenario: Starting a job with invalid Bundle Stop step.Scenario: Starting a job with invalid Bundle Stop step2 ms4
 Scenario: Starting a job with invalid Bundle Stop step and multiple devices.And Bundles are requested1 ms4
 Scenario: Starting a job with invalid Bundle Stop step and multiple devices.Scenario: Starting a job with invalid Bundle Stop step and multiple devices2 ms4
 Scenario: Starting a job with invalid Command Execution step.Scenario: Starting a job with invalid Command Execution step2 ms4
 Scenario: Starting a job with invalid Command Execution step.When I search for events from device "rpione3" in account "kapua-sys"1 ms617
 Scenario: Starting a job with invalid Configuration Put step.Scenario: Starting a job with invalid Configuration Put step1 ms4
 Scenario: Starting a job with invalid Configuration Put step.When Configuration is requested1 ms4
 Scenario: Starting a job with invalid Configuration Put step and multiple devices.Scenario: Starting a job with invalid Configuration Put step and multiple devices2 ms4
 Scenario: Starting a job with invalid Configuration Put step and multiple devices.Then Configuration is requested2 ms617
 Scenario: Starting a job with invalid Package Install step.Scenario: Starting a job with invalid Package Install step2 ms4
 Scenario: Starting a job with invalid Package Install step.When I search for events from device "rpione3" in account "kapua-sys"1 ms617
 Scenario: Starting a job with invalid Package Install step and multiple devices.And I start a job1 ms617
 Scenario: Starting a job with invalid Package Install step and multiple devices.Scenario: Starting a job with invalid Package Install step and multiple devices5 ms4
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps.Scenario: Starting a job with invalid Package Uninstall and Asset Write steps6 ms4
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps.When Device assets are requested5 ms617
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices.And Device assets are requested3 ms617
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices.Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices4 ms4
 Scenario: Starting a job with invalid Package Uninstall step.Scenario: Starting a job with invalid Package Uninstall step2 ms4
 Scenario: Starting a job with invalid Package Uninstall step.When I search for events from device "rpione3" in account "kapua-sys"2 ms617
 Scenario: Starting a job with invalid Package Uninstall step and multiple targets.And I start a job1 ms617
 Scenario: Starting a job with invalid Package Uninstall step and multiple targets.Scenario: Starting a job with invalid Package Uninstall step and multiple targets2 ms4
 Scenario: Starting a job with two Bundle Start steps.And Bundles are requested2 ms617
 Scenario: Starting a job with two Bundle Start steps.Scenario: Starting a job with two Bundle Start steps2 ms4
 Scenario: Starting a job with valid Asset Write step.Scenario: Starting a job with valid Asset Write step2 ms4
 Scenario: Starting a job with valid Asset Write step.When Device assets are requested2 ms617
 Scenario: Starting a job with valid Asset Write step and multiple targets.And Device assets are requested2 ms617
 Scenario: Starting a job with valid Asset Write step and multiple targets.Scenario: Starting a job with valid Asset Write step and multiple targets3 ms4
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps.And Bundles are requested2 ms4
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps.Scenario: Starting a job with valid Bundle Start and Bundle Stop steps3 ms4
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices.And Bundles are requested3 ms4
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices.Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices3 ms4
 Scenario: Starting a job with valid Bundle Start step.And Bundles are requested2 ms4
 Scenario: Starting a job with valid Bundle Start step.Scenario: Starting a job with valid Bundle Start step5 ms4
 Scenario: Starting a job with valid Bundle Stop step.And Bundles are requested1 ms4
 Scenario: Starting a job with valid Bundle Stop step.Scenario: Starting a job with valid Bundle Stop step2 ms4
 Scenario: Starting a job with valid Bundle Stop step and multiple devices.And Bundles are requested2 ms4
 Scenario: Starting a job with valid Bundle Stop step and multiple devices.Scenario: Starting a job with valid Bundle Stop step and multiple devices3 ms4
 Scenario: Starting a job with valid Command Execution step.Scenario: Starting a job with valid Command Execution step3 ms4
 Scenario: Starting a job with valid Command Execution step.When I search for events from device "rpione3" in account "kapua-sys"2 ms617
 Scenario: Starting a job with valid Configuration Put step.Scenario: Starting a job with valid Configuration Put step2 ms4
 Scenario: Starting a job with valid Configuration Put step.When Configuration is requested1 ms4
 Scenario: Starting a job with valid Configuration Put step and multiple devices.Scenario: Starting a job with valid Configuration Put step and multiple devices2 ms4
 Scenario: Starting a job with valid Configuration Put step and multiple devices.Then Configuration is requested2 ms617
 Scenario: Starting a job with valid Package Install step.Scenario: Starting a job with valid Package Install step2 ms4
 Scenario: Starting a job with valid Package Install step.When I search for events from device "rpione3" in account "kapua-sys"2 ms617
 Scenario: Starting a job with valid Package Install step and multiple devices.And I start a job3 ms617
 Scenario: Starting a job with valid Package Install step and multiple devices.Scenario: Starting a job with valid Package Install step and multiple devices4 ms4
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps.Scenario: Starting a job with valid Package Uninstall and Asset Write steps14 ms4
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps.When Device assets are requested1 ms617
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices.And Device assets are requested2 ms617
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices.Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices3 ms4
 Scenario: Starting a job with valid Package Uninstall step.Scenario: Starting a job with valid Package Uninstall step2 ms4
 Scenario: Starting a job with valid Package Uninstall step.When I search for events from device "rpione3" in account "kapua-sys"1 ms617
 Scenario: Starting a job with valid Package Uninstall step and multiple targets.And I start a job5 ms617
 Scenario: Starting a job with valid Package Uninstall step and multiple targets.Scenario: Starting a job with valid Package Uninstall step and multiple targets6 ms4
 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 ms4
 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 ms4
 Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices.Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices3 ms4
 Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices.Then I count 22 ms4
 Scenario: Starting job with Asset Write step and multiple devices.Scenario: Starting job with Asset Write step and multiple devices2 ms4
 Scenario: Starting job with Asset Write step and multiple devices.Then I count 22 ms4
 Scenario: Starting job with Bundle Start step and multiple devices.Scenario: Starting job with Bundle Start step and multiple devices2 ms4
 Scenario: Starting job with Bundle Start step and multiple devices.Then I count 21 ms4
 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 devices0 ms4
 Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices.Then I count 20 ms4
 Scenario: Starting job with Bundle Stop step and multiple devices.Scenario: Starting job with Bundle Stop step and multiple devices0 ms4
 Scenario: Starting job with Bundle Stop step and multiple devices.Then I count 20 ms4
 Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices.Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices2 ms4
 Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices.Then I count 21 ms4
 Scenario: Starting job with Command Execution step and multiple devices.Scenario: Starting job with Command Execution step and multiple devices2 ms4
 Scenario: Starting job with Command Execution step and multiple devices.Then I count 21 ms4
 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 ms4
 Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices.Then I count 22 ms4
 Scenario: Starting job with Configuration Put step and multiple devices.Scenario: Starting job with Configuration Put step and multiple devices3 ms4
 Scenario: Starting job with Configuration Put step and multiple devices.Then I count 22 ms4
 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 devices6 ms4
 Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices.Then Device status is "DISCONNECTED"4 ms1
 Scenario: Starting job with Package Download/Install step and multiple devices.Scenario: Starting job with Package Download/Install step and multiple devices4 ms4
 Scenario: Starting job with Package Download/Install step and multiple devices.Then Device status is "DISCONNECTED"2 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 device8 ms4
 Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device.Then I count 28 ms4
 Scenario: Starting job with Package Uninstall step and multiple device.Scenario: Starting job with Package Uninstall step and multiple device3 ms4
 Scenario: Starting job with Package Uninstall step and multiple device.Then I count 22 ms4
 Scenario: Starting job with invalid Bundle Start step and multiple devices.And Bundles are requested2 ms4
 Scenario: Starting job with invalid Bundle Start step and multiple devices.Scenario: Starting job with invalid Bundle Start step and multiple devices3 ms4
 Scenario: Starting job with invalid Command Execution and Package Install steps.And Command "pwd" is executed2 ms4
 Scenario: Starting job with invalid Command Execution and Package Install steps.Scenario: Starting job with invalid Command Execution and Package Install steps2 ms4
 Scenario: Starting job with invalid Command Execution step and multiple devices.And Command "pwd" is executed1 ms4
 Scenario: Starting job with invalid Command Execution step and multiple devices.Scenario: Starting job with invalid Command Execution step and multiple devices2 ms4
 Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices.And Command "pwd" is executed2 ms4
 Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices.Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices2 ms4
 Scenario: Starting job with invalid Configuration Put and Command Execution steps.Scenario: Starting job with invalid Configuration Put and Command Execution steps4 ms4
 Scenario: Starting job with invalid Configuration Put and Command Execution steps.Then Configuration is requested3 ms617
 Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices.Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices2 ms4
 Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices.Then Configuration is requested2 ms617
 Scenario: Starting job with two Bundle Start steps and multiple devices.Scenario: Starting job with two Bundle Start steps and multiple devices6 ms4
 Scenario: Starting job with two Bundle Start steps and multiple devices.Then I count 24 ms4
 Scenario: Starting job with valid Bundle Start step and multiple devices.And Bundles are requested2 ms4
 Scenario: Starting job with valid Bundle Start step and multiple devices.Scenario: Starting job with valid Bundle Start step and multiple devices3 ms4
 Scenario: Starting job with valid Command Execution and Package Install steps.And Command "pwd" is executed3 ms4
 Scenario: Starting job with valid Command Execution and Package Install steps.Scenario: Starting job with valid Command Execution and Package Install steps5 ms4
 Scenario: Starting job with valid Command Execution step and multiple devices.And Command "pwd" is executed2 ms4
 Scenario: Starting job with valid Command Execution step and multiple devices.Scenario: Starting job with valid Command Execution step and multiple devices2 ms4
 Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices.And Command "pwd" is executed1 ms4
 Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices.Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices2 ms4
 Scenario: Starting job with valid Configuration Put and Command Execution steps.And Configuration is requested1 ms617
 Scenario: Starting job with valid Configuration Put and Command Execution steps.Scenario: Starting job with valid Configuration Put and Command Execution steps2 ms4
 Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices.Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices3 ms4
 Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices.Then Configuration is requested2 ms617
 Scenario: Stealing link scenario.And Client named "client-2" is not connected4 ms617
 Scenario: Stealing link scenario.Scenario: Stealing link scenario14 ms4
 Scenario: Stop job with multiple Asset Write and Package Install steps and one target.Scenario: Stop job with multiple Asset Write and Package Install steps and one target4 ms4
 Scenario: Stop job with multiple Asset Write and Package Install steps and one target.When Device assets are requested3 ms617
 Scenario: Stop job with multiple Bundle Start and Package Install steps and one target.And Bundles are requested0 ms4
 Scenario: Stop job with multiple Bundle Start and Package Install steps and one target.Scenario: Stop job with multiple Bundle Start and Package Install steps and one target0 ms4
 Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target.And Bundles are requested1 ms4
 Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target.Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target2 ms4
 Scenario: Stop job with multiple Command Execution and Package Install steps and one target.And Command pwd is executed2 ms4
 Scenario: Stop job with multiple Command Execution and Package Install steps and one target.Scenario: Stop job with multiple Command Execution and Package Install steps and one target3 ms4
 Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target.And Configuration is requested2 ms617
 Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target.Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target3 ms4
 Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target.Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target2 ms4
 Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target.When Device assets are requested1 ms617
 Scenario: Stop job with multiple targets and Bundle Start and Package Install steps.And Bundles are requested2 ms4
 Scenario: Stop job with multiple targets and Bundle Start and Package Install steps.Scenario: Stop job with multiple targets and Bundle Start and Package Install steps3 ms4
 Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps.And Bundles are requested1 ms4
 Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps.Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps2 ms4
 Scenario: Stop job with multiple targets and Command Execution and Package Install steps.And Command pwd is executed2 ms4
 Scenario: Stop job with multiple targets and Command Execution and Package Install steps.Scenario: Stop job with multiple targets and Command Execution and Package Install steps3 ms4
 Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps.And Configuration is requested1 ms617
 Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps.Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps2 ms4

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 topic6 ms2608
Scenario: Account based ClientInfo data check21 ms002424
Scenario: Account name must not be mutable3 ms0066
Scenario: Account wide metrics check26 ms002828
Scenario: Add Access Info domain permissions to new user22 ms002626
Scenario: Add Account permissions to the role in child account15 ms002828
Scenario: Add Credential domain permissions to new user15 ms001818
Scenario: Add Datastore domain permissions to new user98 ms001919
Scenario: Add Device Connection domain permissions to kapua-sys user12 ms001111
Scenario: Add Device Connection domain permissions to new user11 ms002323
Scenario: Add Device Event domain permissions to new user25 ms001616
Scenario: Add Device domain permissions to new user14 ms001717
Scenario: Add Domain domain permissions to kapua-sys user11 ms001717
Scenario: Add Domain domain permissions to new user20 ms003232
Scenario: Add Endpoint Permission To The User18 ms003030
Scenario: Add Endpoint_info permissions to the role in child account13 ms003030
Scenario: Add Group domain permissions to new user13 ms001717
Scenario: Add Group permissions to the role in child account21 ms002626
Scenario: Add Job domain permissions to new user15 ms001919
Scenario: Add Role domain permissions to new user14 ms001717
Scenario: Add Role permissions to the role in child account19 ms002626
Scenario: Add Scheduler Permissions With Job Permissions12 ms003131
Scenario: Add Scheduler Permissions Without Job Permissions15 ms002121
Scenario: Add Scheduler permissions to the role in child account20 ms003636
Scenario: Add Tag domain permissions to new user15 ms001515
Scenario: Add Tag permissions to the role in child account12 ms002626
Scenario: Add User domain permissions to new user12 ms002020
Scenario: Add account permissions to the role15 ms001919
Scenario: Add admin role to the user13 ms004444
Scenario: Add and delete Account permissions from the "admin" role15 ms001414
Scenario: Add and delete Device permissions from the "admin" role15 ms001414
Scenario: Add and delete Endpoint_info permissions from the "admin" role11 ms001414
Scenario: Add and delete Group permissions from the "admin" role17 ms001414
Scenario: Add and delete Job permissions from the "admin" role16 ms001414
Scenario: Add and delete Role permissions from the "admin" role20 ms001414
Scenario: Add and delete User permissions from the "admin" role19 ms001515
Scenario: Add datastore permissions to the role17 ms002727
Scenario: Add deleted role again20 ms001010
Scenario: Add device event permissions to the role24 ms003232
Scenario: Add device permissions to the role17 ms001919
Scenario: Add device permissions to the role in child account15 ms002626
Scenario: Add domain, user and access_info permissions to the role14 ms002323
Scenario: Add endpoint_info permissions to the role19 ms003131
Scenario: Add group permissions to the role17 ms001818
Scenario: Add job permissions to the role20 ms001919
Scenario: Add job permissions to the role in child account14 ms002626
Scenario: Add role permissions to the role15 ms001919
Scenario: Add same permission twice to the same role11 ms001414
Scenario: Add same role to user twice17 ms001313
Scenario: Add scheduler permissions to the role17 ms003131
Scenario: Add tag permissions to the role17 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 Parameters10 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value19 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format5 ms001111
Scenario: Adding "Cron Job" Schedule With End Date Only21 ms001010
Scenario: Adding "Cron Job" Schedule With End Time before Start time12 ms001212
Scenario: Adding "Cron Job" Schedule With Non-Unique End Date Parameter10 ms001616
Scenario: Adding "Cron Job" Schedule With Non-Unique Start Date Parameter8 ms001515
Scenario: Adding "Cron Job" Schedule With Start Date Only7 ms001111
Scenario: Adding "Cron Job" Schedule With the same Start and End time11 ms001212
Scenario: Adding "Cron Job" Schedule Without The Start Date Parameter7 ms001010
Scenario: Adding "Device Connect" Schedule With All Valid Parameters9 ms0088
Scenario: Adding "Device Connect" Schedule With End Date Only11 ms001010
Scenario: Adding "Device Connect" Schedule With End Time before Start time7 ms001111
Scenario: Adding "Device Connect" Schedule With Max Length Name9 ms0088
Scenario: Adding "Device Connect" Schedule With Min Length Name10 ms0088
Scenario: Adding "Device Connect" Schedule With Name Only24 ms0099
Scenario: Adding "Device Connect" Schedule With Non-Unique End Date Parameter6 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Name13 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Start Date Parameter7 ms001111
Scenario: Adding "Device Connect" Schedule With Start Date Only9 ms001010
Scenario: Adding "Device Connect" Schedule With the same Start and End time12 ms001111
Scenario: Adding "Device Connect" Schedule Without Name10 ms001010
Scenario: Adding "Device Connect" Schedule Without The Start Date Parameter24 ms0099
Scenario: Adding "Empty" Tag To Device14 ms0099
Scenario: Adding "Interval Job" Schedule With All Valid Parameters8 ms001010
Scenario: Adding "Interval Job" Schedule With End Date Only9 ms001010
Scenario: Adding "Interval Job" Schedule With End Time before Start time21 ms001212
Scenario: Adding "Interval Job" Schedule With Max Length Name26 ms001010
Scenario: Adding "Interval Job" Schedule With Min Length Name7 ms001010
Scenario: Adding "Interval Job" Schedule With Name Only26 ms001010
Scenario: Adding "Interval Job" Schedule With Non-Unique End Date Parameter11 ms001616
Scenario: Adding "Interval Job" Schedule With Non-Unique Name25 ms001515
Scenario: Adding "Interval Job" Schedule With Non-Unique Start Date Parameter7 ms001515
Scenario: Adding "Interval Job" Schedule With Null Interval Number11 ms001212
Scenario: Adding "Interval Job" Schedule With Start Date Only8 ms001111
Scenario: Adding "Interval Job" Schedule With the same Start and End time4 ms001212
Scenario: Adding "Interval Job" Schedule Without Interval Number22 ms001111
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter7 ms0099
Scenario: Adding "Interval Job" Schedule Without a Name9 ms001111
Scenario: Adding "admin" role to a user in a child account16 ms001414
Scenario: Adding "admin" role to multiple users15 ms001818
Scenario: Adding "admin" role twice12 ms001313
Scenario: Adding Account:Delete permission to user in same scope24 ms002525
Scenario: Adding Account:Delete permission to user in sub-account scope16 ms003030
Scenario: Adding Account:Read and Account:Delete permissions to user in same scope11 ms002121
Scenario: Adding Account:Read and Account:Write permissions to user in same scope12 ms001919
Scenario: Adding Account:Read permission to user in same scope21 ms002323
Scenario: Adding Account:Read permission to user in sub-account scope31 ms002929
Scenario: Adding Account:Write and Account:Delete permission to user in same scope9 ms002323
Scenario: Adding Account:Write permission to user in same scope14 ms002525
Scenario: Adding Account:Write permission to user in sub-account scope16 ms003131
Scenario: Adding Multiple Permissions To User47 ms002020
Scenario: Adding One Permission To User21 ms001111
Scenario: Adding Permissions To Child User15 ms001818
Scenario: Adding Permissions To Parallel User15 ms001818
Scenario: Adding Previously Deleted Permission16 ms002828
Scenario: Adding Previously Deleted Tag From Device Again8 ms001515
Scenario: Adding Regular Tag Without Description To Device12 ms001010
Scenario: Adding Tag With Long Name Without Description To Device13 ms001010
Scenario: Adding Tag With Numbers Without Description To Device15 ms001010
Scenario: Adding Tag With Short Name Without Description To Device8 ms001010
Scenario: Adding Tag With Special Symbols Without Description To Device9 ms001010
Scenario: Adding all Account permissions to user in same scope19 ms001717
Scenario: Adding all Account permissions to user in sub-account scope14 ms002424
Scenario: Adding existing roles to user16 ms001515
Scenario: Adding role from child account to user in new child account13 ms001515
Scenario: Adding role to multiple users in child account14 ms001818
Scenario: Adding same role twice to user in child account10 ms001515
Scenario: Adding the same role to user twice in child account13 ms001313
Scenario: B1 Broker publish to CTRL_ACC_REPLY23 ms2709
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed12 ms2709
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed6 ms2608
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI7 ms2709
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed15 ms2709
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed6 ms2608
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY6 ms2709
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY15 ms2709
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account13 ms2709
Scenario: B5 Broker publish to CTRL_ACC is not allowed7 ms2709
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed7 ms2709
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed10 ms2608
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI10 ms2709
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed6 ms2709
Scenario: Birth and applications event handling6 ms001212
Scenario: Birth and death message handling13 ms001212
Scenario: Birth and missing event handling12 ms001212
Scenario: Birth message handling from a new device14 ms001313
Scenario: Birth message handling from an existing device8 ms001212
Scenario: Captured date based ClientInfo data check23 ms003030
Scenario: Change role name so it is too short4 ms0066
Scenario: Change the account parent path6 ms0055
Scenario: Changing Client ID6 ms0099
Scenario: Changing Description On Tag With Long Description6 ms0077
Scenario: Changing Description On Tag With Long Name9 ms0088
Scenario: Changing Description On Tag With Numbers In Name8 ms0099
Scenario: Changing Description On Tag With Permitted Symbols13 ms0077
Scenario: Changing Description On Tag With Short Description11 ms0077
Scenario: Changing Description On Tag With Short Name9 ms0077
Scenario: Changing Device Status To Disabled16 ms0099
Scenario: Changing Device Status To Enabled12 ms0099
Scenario: Changing Tag's Description To Non-Uniqe One6 ms0088
Scenario: Changing Tag's Description To Uniqe One6 ms001010
Scenario: Changing Tag's Name To Contain Invalid Symbols In Name Without Description10 ms0088
Scenario: Changing Tag's Name To Contain Permitted Symbols In Name Without Description14 ms0088
Scenario: Changing Tag's Name To Non-Unique One6 ms0099
Scenario: Changing Tag's Name To Short One Without Description6 ms001010
Scenario: Changing Tag's Name To Unique One8 ms001010
Scenario: Changing Tag's Name To a Long One Without Description8 ms001010
Scenario: Changing Tag's Name To a Too Long One Without Description9 ms0088
Scenario: Changing Tag's Name To a Too Short One Without Description7 ms0088
Scenario: Changing description of a nonexisting role2 ms0077
Scenario: Changing job description to non-unique one5 ms0077
Scenario: Changing job description to the long one5 ms0066
Scenario: Changing job description to unique one5 ms0066
Scenario: Changing job description to very short one6 ms0077
Scenario: Changing job name to a long one without description6 ms0077
Scenario: Changing job name to a too long one without description2 ms0055
Scenario: Changing job name to a too short one without description13 ms0066
Scenario: Changing job name to contain invalid symbols in name without description6 ms0044
Scenario: Changing job name to contain permitted symbols in name without description6 ms0055
Scenario: Changing job name to non-unique one7 ms0088
Scenario: Changing job name to short one without description11 ms0077
Scenario: Changing job name to unique one6 ms0099
Scenario: Changing name of a nonexisting role6 ms0077
Scenario: Changing role description to a valid one3 ms0066
Scenario: Changing role name so it is too long4 ms0066
Scenario: Changing role name to contain special character5 ms0044
Scenario: Changing role name to null2 ms0066
Scenario: Changing role's name to a valid one3 ms0066
Scenario: Channel info queries based on datastore channel filters20 ms005050
Scenario: ChannelInfo client ID and topic data based on the client id31 ms002828
Scenario: ChannelInfo client ID based on the account id18 ms002626
Scenario: ChannelInfo last published date20 ms003030
Scenario: ChannelInfo topic data based on the account id27 ms002626
Scenario: Check account properties7 ms0044
Scenario: Check the Device Connection Domain data seetting3 ms0022
Scenario: Check the database cache coherency30 ms003030
Scenario: Check the mapping for message semantic topics21 ms003030
Scenario: Check the message store26 ms002020
Scenario: Check the sanity of the Device Connection Domain data initialization3 ms0022
Scenario: Client Id based ClientInfo data check22 ms002828