Test Result : (root)

530 failures (±0) , 5,289 skipped (±0)
16,599 tests (±0)
Took 14 sec.

All Failed Tests

Test NameDurationAge
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Given Mqtt Device is started3 ms11
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic6 ms11
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Given Mqtt Device is started4 ms11
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY9 ms11
 Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.Given Mqtt Device is started3 ms11
 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 allowed5 ms11
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Given Mqtt Device is started4 ms11
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed6 ms11
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started4 ms11
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI5 ms11
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started4 ms11
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms11
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started5 ms11
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed7 ms11
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started2 ms11
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY4 ms11
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started4 ms11
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY6 ms11
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started3 ms11
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account5 ms11
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.Given Mqtt Device is started6 ms11
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.Scenario: B5 Broker publish to CTRL_ACC is not allowed8 ms11
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started3 ms11
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed5 ms11
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Given Mqtt Device is started7 ms11
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed9 ms11
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started6 ms11
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI8 ms11
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started7 ms11
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed9 ms11
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data14 ms11
 Scenario: Connect to the system and publish some data.Then Device sim-1 for account kapua-sys is registered after 5 seconds4 ms11
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Given Mqtt Device is started4 ms11
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY6 ms11
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started6 ms11
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI8 ms11
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started5 ms11
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed6 ms11
 Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started6 ms11
 Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed8 ms11
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started9 ms11
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY11 ms11
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started7 ms11
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY9 ms11
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started2 ms11
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account4 ms11
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Given Mqtt Device is started6 ms11
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Scenario: D5 Device subscribe - publish - admin on CTRL_ACC8 ms11
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started3 ms11
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI4 ms11
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started2 ms11
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed4 ms11
 Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.Given Mqtt Device is started2 ms11
 Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed4 ms11
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Given Mqtt Device is started5 ms11
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed7 ms11
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Given Mqtt Device is started7 ms11
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed8 ms11
 Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started3 ms11
 Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI4 ms11
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started4 ms11
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms11
 Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started5 ms11
 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 allowed7 ms11
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started19 ms11
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY20 ms11
 Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started4 ms11
 Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY5 ms11
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started6 ms11
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account8 ms11
 Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Given Mqtt Device is started3 ms11
 Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Scenario: DM5 Data manage publish to CTRL_ACC is not allowed4 ms11
 Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started3 ms11
 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 allowed4 ms11
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Given Mqtt Device is started4 ms11
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed9 ms11
 Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started4 ms11
 Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI6 ms11
 Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Given Mqtt Device is started3 ms11
 Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC5 ms11
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Given Mqtt Device is started3 ms11
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY4 ms11
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Given Mqtt Device is started2 ms11
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed7 ms11
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Given Mqtt Device is started5 ms11
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed6 ms11
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Given Mqtt Device is started3 ms11
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed4 ms11
 Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed.Given Mqtt Device is started2 ms11
 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 allowed4 ms11
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started5 ms11
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed7 ms11
 Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started14 ms11
 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 allowed14 ms11
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started8 ms11
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY9 ms11
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started3 ms11
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY4 ms11
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started2 ms11
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account4 ms11
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Given Mqtt Device is started3 ms11
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Scenario: DV5 Data view publish to CTRL_ACC is not allowed5 ms11
 Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started4 ms11
 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 allowed6 ms11
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Given Mqtt Device is started2 ms11
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed4 ms11
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started6 ms11
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI12 ms11
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started3 ms11
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed4 ms11
 Scenario: Execute possible docker steps to show its usage.Given List images by name "kapua/kapua-broker:1.3.0-SNAPSHOT"3 ms8
 Scenario: Execute possible docker steps to show its usage.Scenario: Execute possible docker steps to show its usage4 ms8
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device22 ms11
 Scenario: Executing Job And Then Restarting Device.When I search for events from device "rpione3" in account "kapua-sys"2 ms630
 Scenario: Executing Job When Device Connected After End Date And Time.Scenario: Executing Job When Device Connected After End Date And Time5 ms11
 Scenario: Executing Job When Device Connected After End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"4 ms630
 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 Time5 ms11
 Scenario: Executing Job When Device Connected After The Specified Start Date And Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms630
 Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time2 ms11
 Scenario: Executing Job When Device Connected Before End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"2 ms630
 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 ms11
 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 ms630
 Scenario: Executing Job Without Steps.Scenario: Executing Job Without Steps2 ms11
 Scenario: Executing Job Without Steps.When I search for events from device "rpione3" in account "kapua-sys"2 ms630
 Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode.And The connection status is "CONNECTED"2 ms630
 Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode.Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode4 ms8
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode.And The connection status is "CONNECTED"2 ms630
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode.Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode3 ms8
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices.Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices5 ms8
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices.Then I find 1 connection3 ms630
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric2 ms11
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric2 ms11
 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 ms11
 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 ms11
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics2 ms11
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics2 ms11
 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 ms11
 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 ms11
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics2 ms11
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics3 ms11
 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 ms11
 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 ms11
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters5 ms11
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters2 ms11
 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 ms11
 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 ms11
 Scenario: Installing a package.Scenario: Installing a package0 ms11
 Scenario: Installing a package.Then Device sim-1 for account kapua-sys is registered after 5 seconds0 ms11
 Scenario: List Endpoints Created From Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22221 ms8
 Scenario: List Endpoints Created From Sub-Account.Scenario: List Endpoints Created From Sub-Account3 ms8
 Scenario: List Endpoints From "kapua-sys" Account.Scenario: List Endpoints From "kapua-sys" Account2 ms8
 Scenario: List Endpoints From "kapua-sys" Account.Then I find 3 endpoints1 ms630
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22221 ms8
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.Scenario: List Endpoints From Sub-Account Of Another Sub-Account2 ms8
 Scenario: List Endpoints From Sub-account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms8
 Scenario: List Endpoints From Sub-account.Scenario: List Endpoints From Sub-account3 ms8
 Scenario: New connection with reserved ID.And The connection status is "CONNECTED"2 ms630
 Scenario: New connection with reserved ID.Scenario: New connection with reserved ID4 ms8
 Scenario: Restarting a job with Asset Write and Bundle Start steps.And A new job target item1 ms630
 Scenario: Restarting a job with Asset Write and Bundle Start steps.Scenario: Restarting a job with Asset Write and Bundle Start steps2 ms11
 Scenario: Restarting a job with Command Execution and Bundle Start steps.And A new job target item2 ms630
 Scenario: Restarting a job with Command Execution and Bundle Start steps.Scenario: Restarting a job with Command Execution and Bundle Start steps2 ms11
 Scenario: Restarting a job with Configuration Put and Bundle Start steps.And A new job target item1 ms630
 Scenario: Restarting a job with Configuration Put and Bundle Start steps.Scenario: Restarting a job with Configuration Put and Bundle Start steps2 ms11
 Scenario: Restarting a job with Package Uninstall and Bundle Start steps.And A new job target item2 ms630
 Scenario: Restarting a job with Package Uninstall and Bundle Start steps.Scenario: Restarting a job with Package Uninstall and Bundle Start steps3 ms11
 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 ms8
 Scenario: Restarting a job with invalid Configuration Put and multiple devices two times.Then Configuration is requested2 ms630
 Scenario: Restarting a job with invalid Configuration Put step two times.Scenario: Restarting a job with invalid Configuration Put step two times2 ms8
 Scenario: Restarting a job with invalid Configuration Put step two times.Then Configuration is requested2 ms630
 Scenario: Restarting a job with invalid Package Install step and multiple devices two times.And A new job target item2 ms8
 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 times3 ms8
 Scenario: Restarting a job with invalid Package Install step two times.Scenario: Restarting a job with invalid Package Install step two times2 ms8
 Scenario: Restarting a job with invalid Package Install step two times.When I search for events from device "rpione3" in account "kapua-sys"2 ms630
 Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times.And The type of the last event is "DEPLOY"1 ms630
 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 ms8
 Scenario: Restarting a job with invalid Package Uninstall step two times.And I search for events from device "rpione3" in account "kapua-sys"2 ms630
 Scenario: Restarting a job with invalid Package Uninstall step two times.Scenario: Restarting a job with invalid Package Uninstall step two times3 ms8
 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 times5 ms8
 Scenario: Restarting a job with valid Configuration Put step and multiple devices two times.Then Configuration is requested3 ms630
 Scenario: Restarting a job with valid Configuration Put step two times.Scenario: Restarting a job with valid Configuration Put step two times2 ms8
 Scenario: Restarting a job with valid Configuration Put step two times.Then Configuration is requested2 ms630
 Scenario: Restarting a job with valid Package Install step and multiple devices two times.And I restart a job2 ms630
 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 times3 ms8
 Scenario: Restarting a job with valid Package Install step two times.Scenario: Restarting a job with valid Package Install step two times2 ms8
 Scenario: Restarting a job with valid Package Install step two times.When I search for events from device "rpione3" in account "kapua-sys"1 ms630
 Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times.And The type of the last event is "DEPLOY"2 ms630
 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 times6 ms8
 Scenario: Restarting a job with valid Package Uninstall step two times.And I search for events from device "rpione3" in account "kapua-sys"2 ms630
 Scenario: Restarting a job with valid Package Uninstall step two times.Scenario: Restarting a job with valid Package Uninstall step two times2 ms8
 Scenario: Restarting job With invalid Asset Write and multiple two times.And Device assets are requested2 ms630
 Scenario: Restarting job With invalid Asset Write and multiple two times.Scenario: Restarting job With invalid Asset Write and multiple two times2 ms8
 Scenario: Restarting job With valid Asset Write step two times.And Device assets are requested1 ms630
 Scenario: Restarting job With valid Asset Write step two times.Scenario: Restarting job With valid Asset Write step two times2 ms8
 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 ms11
 Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices.Then I count 22 ms11
 Scenario: Restarting job with Asset Write step.And A new job target item2 ms630
 Scenario: Restarting job with Asset Write step.Scenario: Restarting job with Asset Write step2 ms11
 Scenario: Restarting job with Asset Write step and multiple devices.Scenario: Restarting job with Asset Write step and multiple devices2 ms11
 Scenario: Restarting job with Asset Write step and multiple devices.Then I count 21 ms11
 Scenario: Restarting job with Bundle Start step.And A new job target item2 ms630
 Scenario: Restarting job with Bundle Start step.Scenario: Restarting job with Bundle Start step2 ms11
 Scenario: Restarting job with Bundle Start step and multiple devices.Scenario: Restarting job with Bundle Start step and multiple devices4 ms11
 Scenario: Restarting job with Bundle Start step and multiple devices.Then I count 23 ms11
 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 ms11
 Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices.Then I count 23 ms11
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.And A new job target item2 ms630
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.Scenario: Restarting job with Bundle Stop and Bundle Start steps3 ms11
 Scenario: Restarting job with Bundle Stop step.And A new job target item1 ms630
 Scenario: Restarting job with Bundle Stop step.Scenario: Restarting job with Bundle Stop step2 ms11
 Scenario: Restarting job with Bundle Stop step and multiple devices.Scenario: Restarting job with Bundle Stop step and multiple devices2 ms11
 Scenario: Restarting job with Bundle Stop step and multiple devices.Then I count 21 ms11
 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 ms11
 Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices.Then I count 21 ms11
 Scenario: Restarting job with Command Execution step.And A new job target item2 ms630
 Scenario: Restarting job with Command Execution step.Scenario: Restarting job with Command Execution step3 ms11
 Scenario: Restarting job with Command Execution step and multiple devices.Scenario: Restarting job with Command Execution step and multiple devices3 ms11
 Scenario: Restarting job with Command Execution step and multiple devices.Then I count 23 ms11
 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 ms11
 Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices.Then I count 22 ms11
 Scenario: Restarting job with Configuration Put step.And A new job target item1 ms630
 Scenario: Restarting job with Configuration Put step.Scenario: Restarting job with Configuration Put step2 ms11
 Scenario: Restarting job with Configuration Put step and multiple devices.Scenario: Restarting job with Configuration Put step and multiple devices0 ms11
 Scenario: Restarting job with Configuration Put step and multiple devices.Then I count 20 ms11
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.And A new job target item2 ms630
 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 devices41 ms11
 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 ms11
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.Then I count 239 ms11
 Scenario: Restarting job with Package Download/Install step and multiple devices.Scenario: Restarting job with Package Download/Install step and multiple devices2 ms11
 Scenario: Restarting job with Package Download/Install step and multiple devices.Then I count 22 ms11
 Scenario: Restarting job with Package Install step.And A new job target item1 ms630
 Scenario: Restarting job with Package Install step.Scenario: Restarting job with Package Install step2 ms11
 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 ms11
 Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device.Then I count 21 ms11
 Scenario: Restarting job with Package Uninstall step.And A new job target item2 ms630
 Scenario: Restarting job with Package Uninstall step.Scenario: Restarting job with Package Uninstall step3 ms11
 Scenario: Restarting job with Package Uninstall step and multiple device.Scenario: Restarting job with Package Uninstall step and multiple device3 ms11
 Scenario: Restarting job with Package Uninstall step and multiple device.Then I count 22 ms11
 Scenario: Restarting job with invalid Asset Write step two times.And Device assets are requested2 ms630
 Scenario: Restarting job with invalid Asset Write step two times.Scenario: Restarting job with invalid Asset Write step two times3 ms8
 Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times.And Bundles are requested1 ms8
 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 times2 ms8
 Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times.And Bundles are requested1 ms8
 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 ms8
 Scenario: Restarting job with invalid Bundle Start step and multiple devices two times.And Bundles are requested1 ms8
 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 ms8
 Scenario: Restarting job with invalid Bundle Start step two times.And Bundles are requested2 ms8
 Scenario: Restarting job with invalid Bundle Start step two times.Scenario: Restarting job with invalid Bundle Start step two times2 ms8
 Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times.And Bundles are requested2 ms8
 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 ms8
 Scenario: Restarting job with invalid Bundle Stop step two times.And Bundles are requested2 ms8
 Scenario: Restarting job with invalid Bundle Stop step two times.Scenario: Restarting job with invalid Bundle Stop step two times2 ms8
 Scenario: Restarting job with invalid Command Execution and Package Install step two times.And Command pwd is executed1 ms8
 Scenario: Restarting job with invalid Command Execution and Package Install step two times.Scenario: Restarting job with invalid Command Execution and Package Install step two times2 ms8
 Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times.And Command pwd is executed2 ms8
 Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times.Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times2 ms8
 Scenario: Restarting job with invalid Command Execution step and multiple devices two times.And Command pwd is executed2 ms8
 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 ms8
 Scenario: Restarting job with invalid Command Execution step two times.Scenario: Restarting job with invalid Command Execution step two times5 ms8
 Scenario: Restarting job with invalid Command Execution step two times.When I search for events from device "rpione3" in account "kapua-sys"5 ms630
 Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times.Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times2 ms8
 Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times.Then Configuration is requested1 ms630
 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 times2 ms8
 Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times.Then Configuration is requested1 ms630
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times.And Device assets are requested0 ms630
 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 times0 ms8
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times.And Device assets are requested2 ms630
 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 ms8
 Scenario: Restarting job with two Bundle Start steps.And A new job target item2 ms630
 Scenario: Restarting job with two Bundle Start steps.Scenario: Restarting job with two Bundle Start steps2 ms11
 Scenario: Restarting job with two Bundle Start steps and multiple devices.Scenario: Restarting job with two Bundle Start steps and multiple devices2 ms11
 Scenario: Restarting job with two Bundle Start steps and multiple devices.Then I count 21 ms11
 Scenario: Restarting job with valid Asset Write step and multiple devices two times.And Device assets are requested3 ms630
 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 times4 ms8
 Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times.And Bundles are requested1 ms8
 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 ms8
 Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times.And Bundles are requested4 ms8
 Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times.Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times4 ms8
 Scenario: Restarting job with valid Bundle Start step and multiple devices two times.And Bundles are requested3 ms8
 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 times5 ms8
 Scenario: Restarting job with valid Bundle Start step two times.And Bundles are requested2 ms8
 Scenario: Restarting job with valid Bundle Start step two times.Scenario: Restarting job with valid Bundle Start step two times2 ms8
 Scenario: Restarting job with valid Bundle Stop step and multiple devices two times.And Bundles are requested2 ms8
 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 ms8
 Scenario: Restarting job with valid Bundle Stop step two times.And Bundles are requested1 ms8
 Scenario: Restarting job with valid Bundle Stop step two times.Scenario: Restarting job with valid Bundle Stop step two times2 ms8
 Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times.And Command pwd is executed1 ms8
 Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times.Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times2 ms8
 Scenario: Restarting job with valid Command Execution and Package Install steps two times.And Command pwd is executed2 ms8
 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 times3 ms8
 Scenario: Restarting job with valid Command Execution step and multiple devices two times.And Command pwd is executed1 ms8
 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 ms8
 Scenario: Restarting job with valid Command Execution step two times.Scenario: Restarting job with valid Command Execution step two times5 ms8
 Scenario: Restarting job with valid Command Execution step two times.When I search for events from device "rpione3" in account "kapua-sys"5 ms630
 Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times.Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times3 ms8
 Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times.Then Configuration is requested2 ms630
 Scenario: Restarting job with valid Configuration Put and Command Execution steps two times.Scenario: Restarting job with valid Configuration Put and Command Execution steps two times2 ms8
 Scenario: Restarting job with valid Configuration Put and Command Execution steps two times.Then Configuration is requested1 ms630
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times.And Device assets are requested2 ms630
 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 ms8
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times.And Device assets are requested3 ms630
 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 times5 ms8
 Scenario: Send BIRTH message and then DC message.And I login as user with name "kapua-sys" and password "kapua-password"5 ms11
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message6 ms11
 Scenario: Send BIRTH message and then DC message while broker ip is set by System.Scenario: Send BIRTH message and then DC message while broker ip is set by System2 ms11
 Scenario: Send BIRTH message and then DC message while broker ip is set by System.Then Device is connected with "localhost" server ip1 ms11
 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 file0 ms11
 Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Then Device is connected with "localhost" server ip0 ms11
 Scenario: Start broker for all scenarios.Given Start Broker1 ms8
 Scenario: Start broker for all scenarios.Given Start Broker11 ms11
 Scenario: Start broker for all scenarios.Given Start Broker2 ms11
 Scenario: Start broker for all scenarios.Given Start Broker1 ms11
 Scenario: Start broker for all scenarios.Given Start Broker1 ms11
 Scenario: Start broker for all scenarios.Given Start Broker1 ms11
 Scenario: Start broker for all scenarios.Given Start Broker2 ms11
 Scenario: Start broker for all scenarios.Given Start Broker2 ms8
 Scenario: Start broker for all scenarios.Given Start Broker1 ms11
 Scenario: Start broker for all scenarios.Given Start Broker1 ms8
 Scenario: Start broker for all scenarios.Given Start Broker2 ms11
 Scenario: Start broker for all scenarios.Given Start Broker1 ms11
 Scenario: Start broker for all scenarios.Given Start Broker1 ms8
 Scenario: Start broker for all scenarios.Given Start Broker1 ms11
 Scenario: Start broker for all scenarios.Given Start Broker1 ms11
 Scenario: Start broker for all scenarios.Given Start Broker2 ms11
 Scenario: Start broker for all scenarios.Given Start Broker1 ms11
 Scenario: Start broker for all scenarios.Given Start Broker1 ms11
 Scenario: Start broker for all scenarios.Given Start Broker2 ms8
 Scenario: Start broker for all scenarios.Given Start Broker1 ms11
 Scenario: Start broker for all scenarios.Given Start Broker1 ms11
 Scenario: Start broker for all scenarios.Given Start Broker1 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms8
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios11 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms8
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms8
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms8
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms11
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms8
 Scenario: Starting a job with Asset Write and Bundle Start steps.And Bundles are requested1 ms630
 Scenario: Starting a job with Asset Write and Bundle Start steps.Scenario: Starting a job with Asset Write and Bundle Start steps2 ms11
 Scenario: Starting a job with Asset Write step.And A new job target item1 ms630
 Scenario: Starting a job with Asset Write step.Scenario: Starting a job with Asset Write step2 ms11
 Scenario: Starting a job with Bundle Start step.And Bundles are requested1 ms630
 Scenario: Starting a job with Bundle Start step.Scenario: Starting a job with Bundle Start step2 ms11
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.And Bundles are requested6 ms630
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.Scenario: Starting a job with Bundle Stop and Bundle Start steps6 ms11
 Scenario: Starting a job with Bundle Stop step.And Bundles are requested1 ms630
 Scenario: Starting a job with Bundle Stop step.Scenario: Starting a job with Bundle Stop step1 ms11
 Scenario: Starting a job with Command Execution and Bundle Start steps.And Bundles are requested1 ms630
 Scenario: Starting a job with Command Execution and Bundle Start steps.Scenario: Starting a job with Command Execution and Bundle Start steps1 ms11
 Scenario: Starting a job with Command Execution step.And A new job target item1 ms630
 Scenario: Starting a job with Command Execution step.Scenario: Starting a job with Command Execution step2 ms11
 Scenario: Starting a job with Configuration Put and Bundle Start steps.And Bundles are requested1 ms630
 Scenario: Starting a job with Configuration Put and Bundle Start steps.Scenario: Starting a job with Configuration Put and Bundle Start steps2 ms11
 Scenario: Starting a job with Configuration Put step.And A new job target item2 ms630
 Scenario: Starting a job with Configuration Put step.Scenario: Starting a job with Configuration Put step3 ms11
 Scenario: Starting a job with Package Install and Bundle Start steps.And Bundles are requested1 ms630
 Scenario: Starting a job with Package Install and Bundle Start steps.Scenario: Starting a job with Package Install and Bundle Start steps2 ms11
 Scenario: Starting a job with Package Install step.Scenario: Starting a job with Package Install step0 ms11
 Scenario: Starting a job with Package Install step.Then Device status is "DISCONNECTED"0 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 ms11
 Scenario: Starting a job with Package Uninstall and Bundle Start steps.Scenario: Starting a job with Package Uninstall and Bundle Start steps26 ms11
 Scenario: Starting a job with Package Uninstall step.And Package named org.eclipse.kura.example.beacon with version 1.0.300 is received1 ms11
 Scenario: Starting a job with Package Uninstall step.Scenario: Starting a job with Package Uninstall step2 ms11
 Scenario: Starting a job with invalid Asset Write step.And Device assets are requested2 ms630
 Scenario: Starting a job with invalid Asset Write step.Scenario: Starting a job with invalid Asset Write step2 ms8
 Scenario: Starting a job with invalid Asset Write step and multiple targets.And Device assets are requested1 ms630
 Scenario: Starting a job with invalid Asset Write step and multiple targets.Scenario: Starting a job with invalid Asset Write step and multiple targets2 ms8
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps.And Bundles are requested2 ms8
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps.Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps2 ms8
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices.And Bundles are requested2 ms8
 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 ms8
 Scenario: Starting a job with invalid Bundle Start step.And Bundles are requested1 ms8
 Scenario: Starting a job with invalid Bundle Start step.Scenario: Starting a job with invalid Bundle Start step2 ms8
 Scenario: Starting a job with invalid Bundle Stop step.And Bundles are requested1 ms8
 Scenario: Starting a job with invalid Bundle Stop step.Scenario: Starting a job with invalid Bundle Stop step2 ms8
 Scenario: Starting a job with invalid Bundle Stop step and multiple devices.And Bundles are requested2 ms8
 Scenario: Starting a job with invalid Bundle Stop step and multiple devices.Scenario: Starting a job with invalid Bundle Stop step and multiple devices2 ms8
 Scenario: Starting a job with invalid Command Execution step.Scenario: Starting a job with invalid Command Execution step2 ms8
 Scenario: Starting a job with invalid Command Execution step.When I search for events from device "rpione3" in account "kapua-sys"1 ms630
 Scenario: Starting a job with invalid Configuration Put step.Scenario: Starting a job with invalid Configuration Put step2 ms8
 Scenario: Starting a job with invalid Configuration Put step.When Configuration is requested2 ms8
 Scenario: Starting a job with invalid Configuration Put step and multiple devices.Scenario: Starting a job with invalid Configuration Put step and multiple devices2 ms8
 Scenario: Starting a job with invalid Configuration Put step and multiple devices.Then Configuration is requested1 ms630
 Scenario: Starting a job with invalid Package Install step.Scenario: Starting a job with invalid Package Install step2 ms8
 Scenario: Starting a job with invalid Package Install step.When I search for events from device "rpione3" in account "kapua-sys"1 ms630
 Scenario: Starting a job with invalid Package Install step and multiple devices.And I start a job2 ms630
 Scenario: Starting a job with invalid Package Install step and multiple devices.Scenario: Starting a job with invalid Package Install step and multiple devices3 ms8
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps.Scenario: Starting a job with invalid Package Uninstall and Asset Write steps2 ms8
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps.When Device assets are requested2 ms630
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices.And Device assets are requested2 ms630
 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 devices3 ms8
 Scenario: Starting a job with invalid Package Uninstall step.Scenario: Starting a job with invalid Package Uninstall step2 ms8
 Scenario: Starting a job with invalid Package Uninstall step.When I search for events from device "rpione3" in account "kapua-sys"1 ms630
 Scenario: Starting a job with invalid Package Uninstall step and multiple targets.And I start a job2 ms630
 Scenario: Starting a job with invalid Package Uninstall step and multiple targets.Scenario: Starting a job with invalid Package Uninstall step and multiple targets3 ms8
 Scenario: Starting a job with two Bundle Start steps.And Bundles are requested1 ms630
 Scenario: Starting a job with two Bundle Start steps.Scenario: Starting a job with two Bundle Start steps2 ms11
 Scenario: Starting a job with valid Asset Write step.Scenario: Starting a job with valid Asset Write step2 ms8
 Scenario: Starting a job with valid Asset Write step.When Device assets are requested1 ms630
 Scenario: Starting a job with valid Asset Write step and multiple targets.And Device assets are requested2 ms630
 Scenario: Starting a job with valid Asset Write step and multiple targets.Scenario: Starting a job with valid Asset Write step and multiple targets3 ms8
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps.And Bundles are requested1 ms8
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps.Scenario: Starting a job with valid Bundle Start and Bundle Stop steps2 ms8
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices.And Bundles are requested1 ms8
 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 devices2 ms8
 Scenario: Starting a job with valid Bundle Start step.And Bundles are requested1 ms8
 Scenario: Starting a job with valid Bundle Start step.Scenario: Starting a job with valid Bundle Start step2 ms8
 Scenario: Starting a job with valid Bundle Stop step.And Bundles are requested1 ms8
 Scenario: Starting a job with valid Bundle Stop step.Scenario: Starting a job with valid Bundle Stop step2 ms8
 Scenario: Starting a job with valid Bundle Stop step and multiple devices.And Bundles are requested1 ms8
 Scenario: Starting a job with valid Bundle Stop step and multiple devices.Scenario: Starting a job with valid Bundle Stop step and multiple devices2 ms8
 Scenario: Starting a job with valid Command Execution step.Scenario: Starting a job with valid Command Execution step2 ms8
 Scenario: Starting a job with valid Command Execution step.When I search for events from device "rpione3" in account "kapua-sys"1 ms630
 Scenario: Starting a job with valid Configuration Put step.Scenario: Starting a job with valid Configuration Put step3 ms8
 Scenario: Starting a job with valid Configuration Put step.When Configuration is requested2 ms8
 Scenario: Starting a job with valid Configuration Put step and multiple devices.Scenario: Starting a job with valid Configuration Put step and multiple devices2 ms8
 Scenario: Starting a job with valid Configuration Put step and multiple devices.Then Configuration is requested1 ms630
 Scenario: Starting a job with valid Package Install step.Scenario: Starting a job with valid Package Install step2 ms8
 Scenario: Starting a job with valid Package Install step.When I search for events from device "rpione3" in account "kapua-sys"1 ms630
 Scenario: Starting a job with valid Package Install step and multiple devices.And I start a job2 ms630
 Scenario: Starting a job with valid Package Install step and multiple devices.Scenario: Starting a job with valid Package Install step and multiple devices3 ms8
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps.Scenario: Starting a job with valid Package Uninstall and Asset Write steps2 ms8
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps.When Device assets are requested1 ms630
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices.And Device assets are requested2 ms630
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices.Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices2 ms8
 Scenario: Starting a job with valid Package Uninstall step.Scenario: Starting a job with valid Package Uninstall step2 ms8
 Scenario: Starting a job with valid Package Uninstall step.When I search for events from device "rpione3" in account "kapua-sys"1 ms630
 Scenario: Starting a job with valid Package Uninstall step and multiple targets.And I start a job2 ms630
 Scenario: Starting a job with valid Package Uninstall step and multiple targets.Scenario: Starting a job with valid Package Uninstall step and multiple targets4 ms8
 Scenario: Starting and stopping the simulator should create a device entry and properly set its status.Scenario: Starting and stopping the simulator should create a device entry and properly set its status2 ms11
 Scenario: Starting and stopping the simulator should create a device entry and properly set its status.Then Device sim-1 for account kapua-sys is registered after 5 seconds1 ms11
 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 devices0 ms11
 Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices.Then I count 20 ms11
 Scenario: Starting job with Asset Write step and multiple devices.Scenario: Starting job with Asset Write step and multiple devices2 ms11
 Scenario: Starting job with Asset Write step and multiple devices.Then I count 22 ms11
 Scenario: Starting job with Bundle Start step and multiple devices.Scenario: Starting job with Bundle Start step and multiple devices2 ms11
 Scenario: Starting job with Bundle Start step and multiple devices.Then I count 22 ms11
 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 devices1 ms11
 Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices.Then I count 20 ms11
 Scenario: Starting job with Bundle Stop step and multiple devices.Scenario: Starting job with Bundle Stop step and multiple devices2 ms11
 Scenario: Starting job with Bundle Stop step and multiple devices.Then I count 22 ms11
 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 ms11
 Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices.Then I count 22 ms11
 Scenario: Starting job with Command Execution step and multiple devices.Scenario: Starting job with Command Execution step and multiple devices2 ms11
 Scenario: Starting job with Command Execution step and multiple devices.Then I count 21 ms11
 Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices.Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices2 ms11
 Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices.Then I count 21 ms11
 Scenario: Starting job with Configuration Put step and multiple devices.Scenario: Starting job with Configuration Put step and multiple devices2 ms11
 Scenario: Starting job with Configuration Put step and multiple devices.Then I count 22 ms11
 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 devices4 ms11
 Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices.Then Device status is "DISCONNECTED"2 ms1
 Scenario: Starting job with Package Download/Install step and multiple devices.Scenario: Starting job with Package Download/Install step and multiple devices4 ms11
 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 device2 ms11
 Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device.Then I count 21 ms11
 Scenario: Starting job with Package Uninstall step and multiple device.Scenario: Starting job with Package Uninstall step and multiple device2 ms11
 Scenario: Starting job with Package Uninstall step and multiple device.Then I count 21 ms11
 Scenario: Starting job with invalid Bundle Start step and multiple devices.And Bundles are requested2 ms8
 Scenario: Starting job with invalid Bundle Start step and multiple devices.Scenario: Starting job with invalid Bundle Start step and multiple devices2 ms8
 Scenario: Starting job with invalid Command Execution and Package Install steps.And Command "pwd" is executed2 ms8
 Scenario: Starting job with invalid Command Execution and Package Install steps.Scenario: Starting job with invalid Command Execution and Package Install steps2 ms8
 Scenario: Starting job with invalid Command Execution step and multiple devices.And Command "pwd" is executed1 ms8
 Scenario: Starting job with invalid Command Execution step and multiple devices.Scenario: Starting job with invalid Command Execution step and multiple devices2 ms8
 Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices.And Command "pwd" is executed2 ms8
 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 devices4 ms8
 Scenario: Starting job with invalid Configuration Put and Command Execution steps.Scenario: Starting job with invalid Configuration Put and Command Execution steps2 ms8
 Scenario: Starting job with invalid Configuration Put and Command Execution steps.Then Configuration is requested1 ms630
 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 ms8
 Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices.Then Configuration is requested2 ms630
 Scenario: Starting job with two Bundle Start steps and multiple devices.Scenario: Starting job with two Bundle Start steps and multiple devices2 ms11
 Scenario: Starting job with two Bundle Start steps and multiple devices.Then I count 22 ms11
 Scenario: Starting job with valid Bundle Start step and multiple devices.And Bundles are requested2 ms8
 Scenario: Starting job with valid Bundle Start step and multiple devices.Scenario: Starting job with valid Bundle Start step and multiple devices2 ms8
 Scenario: Starting job with valid Command Execution and Package Install steps.And Command "pwd" is executed2 ms8
 Scenario: Starting job with valid Command Execution and Package Install steps.Scenario: Starting job with valid Command Execution and Package Install steps3 ms8
 Scenario: Starting job with valid Command Execution step and multiple devices.And Command "pwd" is executed2 ms8
 Scenario: Starting job with valid Command Execution step and multiple devices.Scenario: Starting job with valid Command Execution step and multiple devices3 ms8
 Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices.And Command "pwd" is executed2 ms8
 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 ms8
 Scenario: Starting job with valid Configuration Put and Command Execution steps.And Configuration is requested0 ms630
 Scenario: Starting job with valid Configuration Put and Command Execution steps.Scenario: Starting job with valid Configuration Put and Command Execution steps0 ms8
 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 devices2 ms8
 Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices.Then Configuration is requested1 ms630
 Scenario: Stealing link scenario.And Client named "client-2" is not connected5 ms630
 Scenario: Stealing link scenario.Scenario: Stealing link scenario5 ms11
 Scenario: Stop job with multiple Asset Write and Package Install steps and one target.Scenario: Stop job with multiple Asset Write and Package Install steps and one target3 ms8
 Scenario: Stop job with multiple Asset Write and Package Install steps and one target.When Device assets are requested2 ms630
 Scenario: Stop job with multiple Bundle Start and Package Install steps and one target.And Bundles are requested2 ms8
 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 target3 ms8
 Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target.And Bundles are requested2 ms8
 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 target3 ms8
 Scenario: Stop job with multiple Command Execution and Package Install steps and one target.And Command pwd is executed1 ms8
 Scenario: Stop job with multiple Command Execution and Package Install steps and one target.Scenario: Stop job with multiple Command Execution and Package Install steps and one target2 ms8
 Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target.And Configuration is requested1 ms630
 Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target.Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target2 ms8
 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 target3 ms8
 Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target.When Device assets are requested2 ms630
 Scenario: Stop job with multiple targets and Bundle Start and Package Install steps.And Bundles are requested1 ms8
 Scenario: Stop job with multiple targets and Bundle Start and Package Install steps.Scenario: Stop job with multiple targets and Bundle Start and Package Install steps2 ms8
 Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps.And Bundles are requested2 ms8
 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 steps3 ms8
 Scenario: Stop job with multiple targets and Command Execution and Package Install steps.And Command pwd is executed1 ms8
 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 steps2 ms8
 Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps.And Configuration is requested2 ms630
 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 steps3 ms8
 Scenario: Test LOOSE user coupling on single connection.And The connection status is "CONNECTED"3 ms630
 Scenario: Test LOOSE user coupling on single connection.Scenario: Test LOOSE user coupling on single connection4 ms8
 Scenario: Test LOOSE user coupling with 3 connections.And The connection status is "CONNECTED"2 ms630
 Scenario: Test LOOSE user coupling with 3 connections.Scenario: Test LOOSE user coupling with 3 connections5 ms8
 Scenario: Test STRICT user coupling on single connection.And The connection status is "CONNECTED"2 ms630
 Scenario: Test STRICT user coupling on single connection.Scenario: Test STRICT user coupling on single connection3 ms8
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.And The connection status is "CONNECTED"2 ms630
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.Scenario: Test STRICT user coupling with 3 connections and a reserved user4 ms8
 Scenario: Test STRICT user coupling with user change allowed on single connection.And The connection status is "CONNECTED"2 ms630
 Scenario: Test STRICT user coupling with user change allowed on single connection.Scenario: Test STRICT user coupling with user change allowed on single connection4 ms8

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope24 ms0044
Scenario: A newly created account must have some metadata6 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic9 ms2608
Scenario: Access info service sanity checks4 ms0044
Scenario: Access service comparison sanity checks5 ms0033
Scenario: Account based ClientInfo data check34 ms002424
Scenario: Account exactly on its expiration date23 ms001414
Scenario: Account name must not be mutable4 ms0066
Scenario: Account past its expiration date12 ms001414
Scenario: Account wide metrics check23 ms002828
Scenario: Account with future expiration date8 ms001313
Scenario: Account with no expiration date13 ms001313
Scenario: Add Access Info domain permissions to new user40 ms002626
Scenario: Add Account permissions to the role in child account20 ms002828
Scenario: Add Credential domain permissions to new user18 ms001818
Scenario: Add Datastore domain permissions to new user0.1 sec001919
Scenario: Add Device Connection domain permissions to kapua-sys user16 ms001111
Scenario: Add Device Connection domain permissions to new user14 ms002323
Scenario: Add Device Event domain permissions to new user29 ms001616
Scenario: Add Device domain permissions to new user13 ms001717
Scenario: Add Domain domain permissions to kapua-sys user19 ms001717
Scenario: Add Domain domain permissions to new user28 ms003232
Scenario: Add Endpoint Permission To The User12 ms003030
Scenario: Add Endpoint_info permissions to the role in child account12 ms003030
Scenario: Add Group domain permissions to new user18 ms001717
Scenario: Add Group permissions to the role in child account17 ms002626
Scenario: Add Job domain permissions to new user29 ms001919
Scenario: Add Role domain permissions to new user25 ms001717
Scenario: Add Role permissions to the role in child account22 ms002626
Scenario: Add Scheduler Permissions With Job Permissions17 ms003131
Scenario: Add Scheduler Permissions Without Job Permissions15 ms002121
Scenario: Add Scheduler permissions to the role in child account11 ms003636
Scenario: Add Tag domain permissions to new user21 ms001515
Scenario: Add Tag permissions to the role in child account17 ms002626
Scenario: Add User domain permissions to new user14 ms002020
Scenario: Add account permissions to the role14 ms001919
Scenario: Add admin role to the user24 ms004444
Scenario: Add and delete Account permissions from the "admin" role15 ms001414
Scenario: Add and delete Device permissions from the "admin" role21 ms001414
Scenario: Add and delete Endpoint_info permissions from the "admin" role9 ms001414
Scenario: Add and delete Group permissions from the "admin" role16 ms001414
Scenario: Add and delete Job permissions from the "admin" role11 ms001414
Scenario: Add and delete Role permissions from the "admin" role14 ms001414
Scenario: Add and delete User permissions from the "admin" role12 ms001515
Scenario: Add datastore permissions to the role13 ms002727
Scenario: Add deleted role again10 ms001010
Scenario: Add device event permissions to the role11 ms003232
Scenario: Add device permissions to the role13 ms001919
Scenario: Add device permissions to the role in child account17 ms002626
Scenario: Add domain, user and access_info permissions to the role16 ms002323
Scenario: Add endpoint_info permissions to the role12 ms003131
Scenario: Add group permissions to the role11 ms001818
Scenario: Add job permissions to the role12 ms001919
Scenario: Add job permissions to the role in child account23 ms002626
Scenario: Add role permissions to the role28 ms001919
Scenario: Add same permission twice to the same role11 ms001414
Scenario: Add same role to user twice13 ms001313
Scenario: Add scheduler permissions to the role31 ms003131
Scenario: Add tag permissions to the role26 ms001818
Scenario: Add user permissions to the role14 ms001919
Scenario: Add user permissions to the role in child account36 ms002626
Scenario: Adding "Cron Job" Schedule With All Valid Parameters11 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value6 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format16 ms001111
Scenario: Adding "Cron Job" Schedule With End Date Only4 ms001010
Scenario: Adding "Cron Job" Schedule With End Time before Start time11 ms001212
Scenario: Adding "Cron Job" Schedule With Non-Unique End Date Parameter12 ms001616
Scenario: Adding "Cron Job" Schedule With Non-Unique Start Date Parameter10 ms001515
Scenario: Adding "Cron Job" Schedule With Start Date Only11 ms001111
Scenario: Adding "Cron Job" Schedule With the same Start and End time3 ms001212
Scenario: Adding "Cron Job" Schedule Without The Start Date Parameter6 ms001010
Scenario: Adding "Device Connect" Schedule With All Valid Parameters13 ms0088
Scenario: Adding "Device Connect" Schedule With End Date Only7 ms001010
Scenario: Adding "Device Connect" Schedule With End Time before Start time8 ms001111
Scenario: Adding "Device Connect" Schedule With Max Length Name9 ms0088
Scenario: Adding "Device Connect" Schedule With Min Length Name12 ms0088
Scenario: Adding "Device Connect" Schedule With Name Only7 ms0099
Scenario: Adding "Device Connect" Schedule With Non-Unique End Date Parameter7 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Name6 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Start Date Parameter9 ms001111
Scenario: Adding "Device Connect" Schedule With Start Date Only9 ms001010
Scenario: Adding "Device Connect" Schedule With the same Start and End time6 ms001111
Scenario: Adding "Device Connect" Schedule Without Name6 ms001010
Scenario: Adding "Device Connect" Schedule Without The Start Date Parameter8 ms0099
Scenario: Adding "Empty" Tag To Device7 ms0099
Scenario: Adding "Interval Job" Schedule With All Valid Parameters7 ms001010
Scenario: Adding "Interval Job" Schedule With End Date Only13 ms001010
Scenario: Adding "Interval Job" Schedule With End Time before Start time9 ms001212
Scenario: Adding "Interval Job" Schedule With Max Length Name7 ms001010
Scenario: Adding "Interval Job" Schedule With Min Length Name9 ms001010
Scenario: Adding "Interval Job" Schedule With Name Only10 ms001010
Scenario: Adding "Interval Job" Schedule With Non-Unique End Date Parameter17 ms001616
Scenario: Adding "Interval Job" Schedule With Non-Unique Name7 ms001515
Scenario: Adding "Interval Job" Schedule With Non-Unique Start Date Parameter9 ms001515
Scenario: Adding "Interval Job" Schedule With Null Interval Number5 ms001212
Scenario: Adding "Interval Job" Schedule With Start Date Only6 ms001111
Scenario: Adding "Interval Job" Schedule With the same Start and End time14 ms001212
Scenario: Adding "Interval Job" Schedule Without Interval Number14 ms001111
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter16 ms0099
Scenario: Adding "Interval Job" Schedule Without a Name8 ms001111
Scenario: Adding "admin" role to a user in a child account17 ms001414
Scenario: Adding "admin" role to multiple users11 ms001818
Scenario: Adding "admin" role twice10 ms001313
Scenario: Adding Account:Delete permission to user in same scope23 ms002525
Scenario: Adding Account:Delete permission to user in sub-account scope18 ms003030
Scenario: Adding Account:Read and Account:Delete permissions to user in same scope18 ms002121
Scenario: Adding Account:Read and Account:Write permissions to user in same scope18 ms001919
Scenario: Adding Account:Read permission to user in same scope11 ms002323
Scenario: Adding Account:Read permission to user in sub-account scope15 ms002929
Scenario: Adding Account:Write and Account:Delete permission to user in same scope18 ms002323
Scenario: Adding Account:Write permission to user in same scope16 ms002525
Scenario: Adding Account:Write permission to user in sub-account scope21 ms003131
Scenario: Adding Multiple Permissions To User19 ms002020
Scenario: Adding One Permission To User21 ms001111
Scenario: Adding Permissions To Child User31 ms001818
Scenario: Adding Permissions To Parallel User32 ms0018