Test Result : (root)

336 failures (+32) , 3,222 skipped (-312)
8,807 tests (-252)
Took 8.4 sec.

All Failed Tests

Test NameDurationAge
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY5 ms17
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"4 ms17
 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 ms17
 Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme/foo"3 ms17
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed6 ms17
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown5 ms17
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed8 ms17
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"6 ms17
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms17
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown3 ms17
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY5 ms17
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"4 ms17
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account3 ms17
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown1 ms17
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed8 ms17
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Then An exception was thrown6 ms17
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed4 ms17
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"3 ms17
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data3 ms17
 Scenario: Connect to the system and publish some data.Then Device sim-1 for account kapua-sys is registered after 5 seconds2 ms17
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY5 ms17
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"4 ms17
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed4 ms17
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"2 ms17
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY5 ms17
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"4 ms17
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account15 ms17
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown15 ms17
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed4 ms17
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"2 ms17
 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 allowed5 ms17
 Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme/foo"4 ms17
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed4 ms17
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown2 ms17
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed8 ms17
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"7 ms17
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms17
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"4 ms17
 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 allowed4 ms17
 Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown2 ms17
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY5 ms17
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"3 ms17
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account7 ms17
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown2 ms17
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed4 ms17
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Then An exception was thrown2 ms17
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY4 ms17
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"3 ms17
 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 allowed10 ms17
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Then Broker doesn't receive string "Hello broker" on topic "acme/foo"9 ms17
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms17
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"4 ms17
 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 allowed8 ms17
 Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown6 ms17
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY5 ms17
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"3 ms17
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account3 ms17
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown1 ms17
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed5 ms17
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Then An exception was thrown4 ms17
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed4 ms17
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"2 ms17
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric2 ms8
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric13 ms8
 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 ms8
 Scenario: Find correct number of messages by corresponding metric.Then I prepare a number of messages with the following details and remember the list as "TestMessages"2 ms8
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics1 ms8
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics2 ms8
 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 ms8
 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 ms8
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics2 ms8
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics1 ms8
 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 ms8
 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 ms8
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters2 ms8
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters3 ms8
 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 ms8
 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 ms8
 Scenario: Installing a package.Scenario: Installing a package7 ms17
 Scenario: Installing a package.Then Device sim-1 for account kapua-sys is registered after 5 seconds5 ms17
 Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The First Time.Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The First Time4 ms8
 Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The First Time.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The Second Time.And Bundles are requested2 ms10
 Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The Second Time.Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The Second Time4 ms8
 Scenario: Restarting Job With Invalid "Bundle Start", multiple devices And Step Index=0 For The First Time.Scenario: Restarting Job With Invalid "Bundle Start", multiple devices And Step Index=0 For The First Time7 ms1
 Scenario: Restarting Job With Invalid "Bundle Start", multiple devices And Step Index=0 For The First Time.Then Devices status is "CONNECTED"5 ms1
 Scenario: Restarting Job With Invalid "Bundle Start", multiple devices And Step Index=0 For The Second Time.And Bundles are requested4 ms10
 Scenario: Restarting Job With Invalid "Bundle Start", multiple devices And Step Index=0 For The Second Time.Scenario: Restarting Job With Invalid "Bundle Start", multiple devices And Step Index=0 For The Second Time5 ms1
 Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The First Time.And Bundles are requested4 ms10
 Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The First Time.Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The First Time6 ms8
 Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The Second Time.And Bundles are requested3 ms10
 Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The Second Time.Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The Second Time4 ms8
 Scenario: Restarting Job With Invalid "Bundle Stop", multiple devices And Step Index=0 For The First Time.And Bundles are requested2 ms10
 Scenario: Restarting Job With Invalid "Bundle Stop", multiple devices And Step Index=0 For The First Time.Scenario: Restarting Job With Invalid "Bundle Stop", multiple devices And Step Index=0 For The First Time4 ms1
 Scenario: Restarting Job With Invalid "Bundle Stop", multiple devices And Step Index=0 For The Second Time.And Bundles are requested3 ms10
 Scenario: Restarting Job With Invalid "Bundle Stop", multiple devices And Step Index=0 For The Second Time.Scenario: Restarting Job With Invalid "Bundle Stop", multiple devices And Step Index=0 For The Second Time5 ms1
 Scenario: Restarting Job With Invalid "Command Execution" And Step Index=0 For The First Time.Scenario: Restarting Job With Invalid "Command Execution" And Step Index=0 For The First Time2 ms8
 Scenario: Restarting Job With Invalid "Command Execution" And Step Index=0 For The First Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms542
 Scenario: Restarting Job With Invalid "Command Execution" And Step Index=0 For The Second Time.Scenario: Restarting Job With Invalid "Command Execution" And Step Index=0 For The Second Time2 ms8
 Scenario: Restarting Job With Invalid "Command Execution" And Step Index=0 For The Second Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms542
 Scenario: Restarting Job With Invalid "Command Execution", multiple devices And Step Index=0 For The First Time.And Command invalidCommand is executed2 ms1
 Scenario: Restarting Job With Invalid "Command Execution", multiple devices And Step Index=0 For The First Time.Scenario: Restarting Job With Invalid "Command Execution", multiple devices And Step Index=0 For The First Time3 ms1
 Scenario: Restarting Job With Invalid "Command Execution", multiple devices And Step Index=0 For The Second Time.And Command invalidCommand is executed2 ms1
 Scenario: Restarting Job With Invalid "Command Execution", multiple devices And Step Index=0 For The Second Time.Scenario: Restarting Job With Invalid "Command Execution", multiple devices And Step Index=0 For The Second Time2 ms1
 Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The First Time.Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The First Time4 ms8
 Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The First Time.Then Device status is "CONNECTED"2 ms542
 Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The Second Time.And Bundles are requested4 ms10
 Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The Second Time.Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The Second Time5 ms8
 Scenario: Restarting Job With Valid "Bundle Start", multiple devices And Step Index=0 For The First Time.Scenario: Restarting Job With Valid "Bundle Start", multiple devices And Step Index=0 For The First Time5 ms1
 Scenario: Restarting Job With Valid "Bundle Start", multiple devices And Step Index=0 For The First Time.Then Devices status is "CONNECTED"4 ms1
 Scenario: Restarting Job With Valid "Bundle Start", multiple devicess And Step Index=0 For The Second Time.And Bundles are requested3 ms10
 Scenario: Restarting Job With Valid "Bundle Start", multiple devicess And Step Index=0 For The Second Time.Scenario: Restarting Job With Valid "Bundle Start", multiple devicess And Step Index=0 For The Second Time4 ms1
 Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The First Time.And Bundles are requested2 ms10
 Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The First Time.Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The First Time4 ms8
 Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The Second Time.And Bundles are requested1 ms10
 Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The Second Time.Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The Second Time2 ms8
 Scenario: Restarting Job With Valid "Bundle Stop", multiple devices And Step Index=0 For The First Time.And Bundles are requested3 ms10
 Scenario: Restarting Job With Valid "Bundle Stop", multiple devices And Step Index=0 For The First Time.Scenario: Restarting Job With Valid "Bundle Stop", multiple devices And Step Index=0 For The First Time4 ms1
 Scenario: Restarting Job With Valid "Bundle Stop", multiple devices And Step Index=0 For The Second Time.And Bundles are requested3 ms10
 Scenario: Restarting Job With Valid "Bundle Stop", multiple devices And Step Index=0 For The Second Time.Scenario: Restarting Job With Valid "Bundle Stop", multiple devices And Step Index=0 For The Second Time4 ms1
 Scenario: Restarting Job With Valid "Command Execution" And Step Index=0 For The First Time.Scenario: Restarting Job With Valid "Command Execution" And Step Index=0 For The First Time2 ms8
 Scenario: Restarting Job With Valid "Command Execution" And Step Index=0 For The First Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms542
 Scenario: Restarting Job With Valid "Command Execution" And Step Index=0 For The Second Time.Scenario: Restarting Job With Valid "Command Execution" And Step Index=0 For The Second Time2 ms8
 Scenario: Restarting Job With Valid "Command Execution" And Step Index=0 For The Second Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms542
 Scenario: Restarting Job With Valid "Command Execution", multiple devices And Step Index=0 For The First Time.And Command pwd is executed1 ms1
 Scenario: Restarting Job With Valid "Command Execution", multiple devices And Step Index=0 For The First Time.Scenario: Restarting Job With Valid "Command Execution", multiple devices And Step Index=0 For The First Time2 ms1
 Scenario: Restarting Job With Valid "Command Execution", multiple devices And Step Index=0 For The Second Time.And Command pwd is executed1 ms1
 Scenario: Restarting Job With Valid "Command Execution", multiple devices And Step Index=0 For The Second Time.Scenario: Restarting Job With Valid "Command Execution", multiple devices And Step Index=0 For The Second Time2 ms1
 Scenario: Restarting a job with Asset Write and Bundle Start steps.Scenario: Restarting a job with Asset Write and Bundle Start steps4 ms3
 Scenario: Restarting a job with Asset Write and Bundle Start steps.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting a job with Command Execution and Bundle Start steps.Scenario: Restarting a job with Command Execution and Bundle Start steps4 ms3
 Scenario: Restarting a job with Command Execution and Bundle Start steps.Then Device status is "CONNECTED"2 ms542
 Scenario: Restarting a job with Configuration Put and Bundle Start steps.Scenario: Restarting a job with Configuration Put and Bundle Start steps5 ms3
 Scenario: Restarting a job with Configuration Put and Bundle Start steps.Then Device status is "CONNECTED"2 ms542
 Scenario: Restarting a job with Package Uninstall and Bundle Start steps.Scenario: Restarting a job with Package Uninstall and Bundle Start steps5 ms3
 Scenario: Restarting a job with Package Uninstall and Bundle Start steps.Then Device status is "CONNECTED"4 ms542
 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 devices4 ms2
 Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting job with Asset Write step.And A new job target item1 ms542
 Scenario: Restarting job with Asset Write step.Scenario: Restarting job with Asset Write step2 ms3
 Scenario: Restarting job with Asset Write step and multiple devices.Scenario: Restarting job with Asset Write step and multiple devices4 ms2
 Scenario: Restarting job with Asset Write step and multiple devices.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting job with Bundle Start step.Scenario: Restarting job with Bundle Start step4 ms3
 Scenario: Restarting job with Bundle Start step.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting job with Bundle Start step and multiple devices.Scenario: Restarting job with Bundle Start step and multiple devices6 ms2
 Scenario: Restarting job with Bundle Start step and multiple devices.Then Device status is "CONNECTED"3 ms542
 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 devices5 ms2
 Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.Scenario: Restarting job with Bundle Stop and Bundle Start steps3 ms3
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.Then Device status is "CONNECTED"2 ms542
 Scenario: Restarting job with Bundle Stop step.Scenario: Restarting job with Bundle Stop step3 ms3
 Scenario: Restarting job with Bundle Stop step.Then Device status is "CONNECTED"2 ms542
 Scenario: Restarting job with Bundle Stop step and multiple devices.Scenario: Restarting job with Bundle Stop step and multiple devices3 ms2
 Scenario: Restarting job with Bundle Stop step and multiple devices.Then Device status is "CONNECTED"2 ms542
 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 devices5 ms2
 Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"4 ms542
 Scenario: Restarting job with Command Execution step.And A new job target item1 ms542
 Scenario: Restarting job with Command Execution step.Scenario: Restarting job with Command Execution step2 ms3
 Scenario: Restarting job with Command Execution step and multiple devices.Scenario: Restarting job with Command Execution step and multiple devices3 ms2
 Scenario: Restarting job with Command Execution step and multiple devices.Then Device status is "CONNECTED"2 ms542
 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 devices5 ms2
 Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"4 ms542
 Scenario: Restarting job with Configuration Put step.And A new job target item2 ms542
 Scenario: Restarting job with Configuration Put step.Scenario: Restarting job with Configuration Put step2 ms3
 Scenario: Restarting job with Configuration Put step and multiple devices.Scenario: Restarting job with Configuration Put step and multiple devices3 ms2
 Scenario: Restarting job with Configuration Put step and multiple devices.Then Device status is "CONNECTED"3 ms542
 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 devices6 ms3
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices6 ms3
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"4 ms542
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"4 ms542
 Scenario: Restarting job with Package Download/Install step and multiple devices.Scenario: Restarting job with Package Download/Install step and multiple devices4 ms2
 Scenario: Restarting job with Package Download/Install step and multiple devices.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting job with Package Install step.Scenario: Restarting job with Package Install step0 ms3
 Scenario: Restarting job with Package Install step.Then Device status is "CONNECTED"0 ms542
 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 device5 ms2
 Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device.Then Device status is "CONNECTED"4 ms542
 Scenario: Restarting job with Package Uninstall step.Scenario: Restarting job with Package Uninstall step5 ms3
 Scenario: Restarting job with Package Uninstall step.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting job with Package Uninstall step and multiple device.Scenario: Restarting job with Package Uninstall step and multiple device3 ms2
 Scenario: Restarting job with Package Uninstall step and multiple device.Then Device status is "CONNECTED"2 ms542
 Scenario: Restarting job with two Bundle Start steps.Scenario: Restarting job with two Bundle Start steps3 ms3
 Scenario: Restarting job with two Bundle Start steps.Then Device status is "CONNECTED"2 ms542
 Scenario: Restarting job with two Bundle Start steps and multiple devices.Scenario: Restarting job with two Bundle Start steps and multiple devices4 ms2
 Scenario: Restarting job with two Bundle Start steps and multiple devices.Then Device status is "CONNECTED"3 ms542
 Scenario: Send BIRTH message and then DC message.And Bundles are requested2 ms17
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message3 ms17
 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 ms17
 Scenario: Send BIRTH message and then DC message while broker ip is set by System.Then Device is connected with "localhost" server ip1 ms17
 Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Scenario: Send BIRTH message and then DC message while broker ip is set by config file2 ms17
 Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Then Device is connected with "localhost" server ip1 ms17
 Scenario: Start broker for all scenarios.Given Start Broker2 ms17
 Scenario: Start broker for all scenarios.Given Start Broker0 ms15
 Scenario: Start broker for all scenarios.Given Start Broker1 ms10
 Scenario: Start broker for all scenarios.Given Start Broker2 ms17
 Scenario: Start broker for all scenarios.Given Start Broker2 ms10
 Scenario: Start broker for all scenarios.Given Start Broker1 ms10
 Scenario: Start broker for all scenarios.Given Start Broker16 ms17
 Scenario: Start broker for all scenarios.Given Start Broker2 ms17
 Scenario: Start broker for all scenarios.Given Start Broker1 ms10
 Scenario: Start broker for all scenarios.Given Start Broker1 ms17
 Scenario: Start broker for all scenarios.Given Start Broker1 ms10
 Scenario: Start broker for all scenarios.Given Start Broker2 ms17
 Scenario: Start broker for all scenarios.Given Start Broker2 ms17
 Scenario: Start broker for all scenarios.Given Start Broker1 ms17
 Scenario: Start broker for all scenarios.Given Start Broker1 ms15
 Scenario: Start broker for all scenarios.Given Start Broker4 ms17
 Scenario: Start broker for all scenarios.Given Start Broker1 ms17
 Scenario: Start broker for all scenarios.Given Start Broker1 ms15
 Scenario: Start broker for all scenarios.Given Start Broker1 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios6 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms15
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios16 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms15
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0 ms15
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms17
 Scenario: Starting a job with Asset Write and Bundle Start steps.Scenario: Starting a job with Asset Write and Bundle Start steps5 ms10
 Scenario: Starting a job with Asset Write and Bundle Start steps.Then Device status is "CONNECTED"4 ms542
 Scenario: Starting a job with Asset Write step.And A new job target item2 ms542
 Scenario: Starting a job with Asset Write step.Scenario: Starting a job with Asset Write step4 ms10
 Scenario: Starting a job with Bundle Start step.Scenario: Starting a job with Bundle Start step5 ms10
 Scenario: Starting a job with Bundle Start step.Then Device status is "CONNECTED"4 ms542
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.And Bundles are requested4 ms10
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.Scenario: Starting a job with Bundle Stop and Bundle Start steps6 ms10
 Scenario: Starting a job with Bundle Stop step.And Bundles are requested6 ms10
 Scenario: Starting a job with Bundle Stop step.Scenario: Starting a job with Bundle Stop step7 ms10
 Scenario: Starting a job with Command Execution and Bundle Start steps.Scenario: Starting a job with Command Execution and Bundle Start steps5 ms10
 Scenario: Starting a job with Command Execution and Bundle Start steps.Then Device status is "CONNECTED"4 ms542
 Scenario: Starting a job with Command Execution step.And A new job target item2 ms542
 Scenario: Starting a job with Command Execution step.Scenario: Starting a job with Command Execution step4 ms10
 Scenario: Starting a job with Configuration Put and Bundle Start steps.And Bundles are requested3 ms10
 Scenario: Starting a job with Configuration Put and Bundle Start steps.Scenario: Starting a job with Configuration Put and Bundle Start steps4 ms10
 Scenario: Starting a job with Configuration Put step.And A new job target item1 ms542
 Scenario: Starting a job with Configuration Put step.Scenario: Starting a job with Configuration Put step2 ms10
 Scenario: Starting a job with Package Install Command step.Scenario: Starting a job with Package Install Command step4 ms10
 Scenario: Starting a job with Package Install Command step.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting a job with Package Install and Bundle Start steps.Scenario: Starting a job with Package Install and Bundle Start steps7 ms10
 Scenario: Starting a job with Package Install and Bundle Start steps.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting a job with Package Uninstall Command step.Scenario: Starting a job with Package Uninstall Command step3 ms10
 Scenario: Starting a job with Package Uninstall Command step.Then Device status is "CONNECTED"2 ms542
 Scenario: Starting a job with Package Uninstall and Bundle Start steps.Scenario: Starting a job with Package Uninstall and Bundle Start steps4 ms10
 Scenario: Starting a job with Package Uninstall and Bundle Start steps.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting a job with invalid Bundle Start step.Scenario: Starting a job with invalid Bundle Start step5 ms9
 Scenario: Starting a job with invalid Bundle Start step.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps.And Bundles are requested2 ms10
 Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps.Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps3 ms9
 Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps and multiple devices.And Bundles are requested2 ms10
 Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps and multiple devices.Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps and multiple devices4 ms1
 Scenario: Starting a job with invalid Bundle Stop step.And Bundles are requested4 ms10
 Scenario: Starting a job with invalid Bundle Stop step.Scenario: Starting a job with invalid Bundle Stop step6 ms9
 Scenario: Starting a job with invalid Bundle Stop step and multiple devices.And Bundles are requested1 ms10
 Scenario: Starting a job with invalid Bundle Stop step and multiple devices.Scenario: Starting a job with invalid Bundle Stop step and multiple devices1 ms1
 Scenario: Starting a job with invalid Command Execution step.Scenario: Starting a job with invalid Command Execution step2 ms9
 Scenario: Starting a job with invalid Command Execution step.When I search for events from device "rpione3" in account "kapua-sys"1 ms542
 Scenario: Starting a job with two Bundle Start steps.Scenario: Starting a job with two Bundle Start steps5 ms10
 Scenario: Starting a job with two Bundle Start steps.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting a job with two invalid Bundle Start steps.Scenario: Starting a job with two invalid Bundle Start steps4 ms9
 Scenario: Starting a job with two invalid Bundle Start steps.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting a job with two invalid Bundle Start steps and multiple devices.Scenario: Starting a job with two invalid Bundle Start steps and multiple devices4 ms1
 Scenario: Starting a job with two invalid Bundle Start steps and multiple devices.Then Device status is "CONNECTED"2 ms542
 Scenario: Starting a job with two valid Bundle Start steps.Scenario: Starting a job with two valid Bundle Start steps3 ms9
 Scenario: Starting a job with two valid Bundle Start steps.Then Device status is "CONNECTED"2 ms542
 Scenario: Starting a job with two valid Bundle Start steps and multiple devices.Scenario: Starting a job with two valid Bundle Start steps and multiple devices3 ms1
 Scenario: Starting a job with two valid Bundle Start steps and multiple devices.Then Device status is "CONNECTED"2 ms542
 Scenario: Starting a job with valid Bundle Start step.Scenario: Starting a job with valid Bundle Start step1 ms9
 Scenario: Starting a job with valid Bundle Start step.Then Device status is "CONNECTED"1 ms542
 Scenario: Starting a job with valid Bundle Stop and Bundle Start steps.And Bundles are requested2 ms10
 Scenario: Starting a job with valid Bundle Stop and Bundle Start steps.Scenario: Starting a job with valid Bundle Stop and Bundle Start steps3 ms9
 Scenario: Starting a job with valid Bundle Stop and Bundle Start steps and multiple devices.And Bundles are requested2 ms10
 Scenario: Starting a job with valid Bundle Stop and Bundle Start steps and multiple devices.Scenario: Starting a job with valid Bundle Stop and Bundle Start steps and multiple devices3 ms1
 Scenario: Starting a job with valid Bundle Stop step.And Bundles are requested4 ms10
 Scenario: Starting a job with valid Bundle Stop step.Scenario: Starting a job with valid Bundle Stop step6 ms9
 Scenario: Starting a job with valid Bundle Stop step and multiple devices.And Bundles are requested1 ms10
 Scenario: Starting a job with valid Bundle Stop step and multiple devices.Scenario: Starting a job with valid Bundle Stop step and multiple devices3 ms1
 Scenario: Starting a job with valid Command Execution step.Scenario: Starting a job with valid Command Execution step2 ms9
 Scenario: Starting a job with valid Command Execution step.When I search for events from device "rpione3" in account "kapua-sys"1 ms542
 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 status6 ms17
 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 seconds4 ms17
 Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices.Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices2 ms7
 Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices.Then I count 21 ms8
 Scenario: Starting job with Asset Write step and multiple devices.Scenario: Starting job with Asset Write step and multiple devices2 ms7
 Scenario: Starting job with Asset Write step and multiple devices.Then I count 21 ms8
 Scenario: Starting job with Bundle Start step and multiple devices.Scenario: Starting job with Bundle Start step and multiple devices2 ms7
 Scenario: Starting job with Bundle Start step and multiple devices.Then I count 21 ms8
 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 ms7
 Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices.Then I count 21 ms8
 Scenario: Starting job with Bundle Stop step and multiple devices.Scenario: Starting job with Bundle Stop step and multiple devices2 ms7
 Scenario: Starting job with Bundle Stop step and multiple devices.Then I count 21 ms8
 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 ms7
 Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices.Then I count 21 ms8
 Scenario: Starting job with Command Execution step and multiple devices.Scenario: Starting job with Command Execution step and multiple devices0 ms7
 Scenario: Starting job with Command Execution step and multiple devices.Then I count 20 ms8
 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 ms7
 Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices.Then I count 22 ms8
 Scenario: Starting job with Configuration Put step and multiple devices.Scenario: Starting job with Configuration Put step and multiple devices2 ms7
 Scenario: Starting job with Configuration Put step and multiple devices.Then I count 21 ms8
 Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices.Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices5 ms7
 Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting job with Package Download/Install step and multiple devices.Scenario: Starting job with Package Download/Install step and multiple devices4 ms7
 Scenario: Starting job with Package Download/Install step and multiple devices.Then Device status is "CONNECTED"2 ms542
 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 ms7
 Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device.Then I count 21 ms8
 Scenario: Starting job with Package Uninstall step and multiple device.Scenario: Starting job with Package Uninstall step and multiple device2 ms7
 Scenario: Starting job with Package Uninstall step and multiple device.Then I count 21 ms8
 Scenario: Starting job with invalid Bundle Start step and multiple devices.Scenario: Starting job with invalid Bundle Start step and multiple devices4 ms1
 Scenario: Starting job with invalid Bundle Start step and multiple devices.Then Device status is "CONNECTED"2 ms542
 Scenario: Starting job with invalid Command Execution and Bundle Start steps.Scenario: Starting job with invalid Command Execution and Bundle Start steps6 ms1
 Scenario: Starting job with invalid Command Execution and Bundle Start steps.Then Device status is "CONNECTED"4 ms542
 Scenario: Starting job with invalid Command Execution step and multiple devices.Scenario: Starting job with invalid Command Execution step and multiple devices0 ms1
 Scenario: Starting job with invalid Command Execution step and multiple devices.Then Device status is "CONNECTED"0 ms542
 Scenario: Starting job with invalid Command Execution, invalid Bundle Start steps and multiple devices.Scenario: Starting job with invalid Command Execution, invalid Bundle Start steps and multiple devices16 ms1
 Scenario: Starting job with invalid Command Execution, invalid Bundle Start steps and multiple devices.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting job with two Bundle Start steps and multiple devices.Scenario: Starting job with two Bundle Start steps and multiple devices2 ms7
 Scenario: Starting job with two Bundle Start steps and multiple devices.Then I count 21 ms8
 Scenario: Starting job with valid Bundle Start step and multiple devices.Scenario: Starting job with valid Bundle Start step and multiple devices4 ms1
 Scenario: Starting job with valid Bundle Start step and multiple devices.Then Device status is "CONNECTED"2 ms542
 Scenario: Starting job with valid Command Execution and Bundle Start steps.Scenario: Starting job with valid Command Execution and Bundle Start steps5 ms1
 Scenario: Starting job with valid Command Execution and Bundle Start steps.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting job with valid Command Execution step and multiple devices.Scenario: Starting job with valid Command Execution step and multiple devices2 ms1
 Scenario: Starting job with valid Command Execution step and multiple devices.Then Device status is "CONNECTED"2 ms542
 Scenario: Starting job with valid Command Execution, valid Bundle Start steps and multiple devices.Scenario: Starting job with valid Command Execution, valid Bundle Start steps and multiple devices3 ms1
 Scenario: Starting job with valid Command Execution, valid Bundle Start steps and multiple devices.Then Device status is "CONNECTED"2 ms542
 Scenario: Stealing link scenario.And Client named "client-2" is not connected4 ms542
 Scenario: Stealing link scenario.Scenario: Stealing link scenario6 ms17

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope10 ms0044
Scenario: A newly created account must have some metadata2 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic18 ms0088
Scenario: Access info service sanity checks6 ms0044
Scenario: Access service comparison sanity checks5 ms0033
Scenario: Account based ClientInfo data check24 ms002424
Scenario: Account exactly on its expiration date12 ms001414
Scenario: Account expiration date test - Parent and child expiration set, then parent expiration date changed to before child expiration date3 ms0066
Scenario: Account expiration date test - Parent expiration set, child expiration after father expiration3 ms0066
Scenario: Account expiration date test - Parent expiration set, child expiration before father expiration3 ms0055
Scenario: Account expiration date test - Parent expiration set, child expiration null4 ms0066
Scenario: Account name must not be mutable3 ms0066
Scenario: Account past its expiration date3 ms001414
Scenario: Account wide metrics check31 ms002828
Scenario: Account with future expiration date10 ms001313
Scenario: Account with no expiration date10 ms001313
Scenario: Add Access Info domain permissions to new user14 ms002626
Scenario: Add Credential domain permissions to new user20 ms001818
Scenario: Add Datastore domain permissions to new user0.21 sec001919
Scenario: Add Device Connection domain permissions to kapua-sys user10 ms001111
Scenario: Add Device Connection domain permissions to new user8 ms002323
Scenario: Add Device Event domain permissions to new user13 ms001616
Scenario: Add Device domain permissions to new user19 ms001717
Scenario: Add Domain domain permissions to kapua-sys user12 ms001717
Scenario: Add Domain domain permissions to new user13 ms003232
Scenario: Add Group domain permissions to new user20 ms001717
Scenario: Add Job domain permissions to new user16 ms001919
Scenario: Add Role domain permissions to new user26 ms001818
Scenario: Add Tag domain permissions to new user20 ms001515
Scenario: Add User domain permissions to new user18 ms002020
Scenario: Add account permissions to the role12 ms001919
Scenario: Add datastore permissions to the role13 ms002727
Scenario: Add deleted role again22 ms001010
Scenario: Add device event permissions to the role16 ms003232
Scenario: Add device permissions to the role19 ms001919
Scenario: Add domain, user and access_info permissions to the role13 ms002323
Scenario: Add endpoint permissions to the role15 ms002626
Scenario: Add group permissions to the role19 ms001919
Scenario: Add job permissions to the role22 ms001919
Scenario: Add role permissions to the role20 ms001919
Scenario: Add same permission twice to the same role11 ms001414
Scenario: Add same role to user twice12 ms001313
Scenario: Add scheduler permissions to the role11 ms003131
Scenario: Add tag permissions to the role20 ms001919
Scenario: Add user permissions to the role21 ms001919
Scenario: Adding Multiple Permissions To User91 ms002020
Scenario: Adding One Permission To User15 ms001111
Scenario: Adding Permissions To Child User19 ms001818
Scenario: Adding Permissions To Parallel User16 ms001818
Scenario: Adding Previously Deleted Permission20 ms002828
Scenario: Adding existing roles to user17 ms001515
Scenario: B1 Broker publish to CTRL_ACC_REPLY9 ms2259
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed7 ms2259
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed11 ms2248
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI21 ms0099
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed15 ms2259
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed7 ms2248
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY9 ms2259
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY11 ms0099
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account5 ms2259
Scenario: B5 Broker publish to CTRL_ACC is not allowed11 ms0099
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed15 ms0099
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed14 ms2248
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI7 ms0099
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed7 ms2259
Scenario: Birth and applications event handling7 ms001212
Scenario: Birth and death message handling6 ms001212
Scenario: Birth and missing event handling6 ms001212
Scenario: Birth message handling from a new device20 ms001313
Scenario: Birth message handling from an existing device6 ms001212
Scenario: Both the parent and child accounts do not expire4 ms001111
Scenario: Both the parent and child accounts have the same expiration date8 ms001111
Scenario: Captured date based ClientInfo data check31 ms003030
Scenario: Change an existing step name4 ms001212
Scenario: Change the account parent path3 ms0055
Scenario: Channel info queries based on datastore channel filters36 ms005050
Scenario: ChannelInfo client ID and topic data based on the client id21 ms002828
Scenario: ChannelInfo client ID based on the account id14 ms002626
Scenario: ChannelInfo last published date24 ms003030
Scenario: ChannelInfo topic data based on the account id26 ms002626
Scenario: Check account properties4 ms0044
Scenario: Check the Device Connection Domain data seetting4 ms0022
Scenario: Check the database cache coherency17 ms003030
Scenario: Check the mapping for message semantic topics30 ms003030
Scenario: Check the message store20 ms002020
Scenario: Check the sanity of the Device Connection Domain data initialization6 ms0022
Scenario: Child account expires after parent2 ms0099
Scenario: Child account expires before parent4 ms001111
Scenario: Child account has null expiration date4 ms0099
Scenario: Client Id based ClientInfo data check24 ms002828
Scenario: Compare domain entries4 ms0033
Scenario: Connect to the system and publish some data5 ms215522
Scenario: Connection Service factory sanity checks3 ms0022
Scenario: Count access info entities in a specific scope7 ms002424
Scenario: Count access role entities by scope4 ms003939
Scenario: Count connections in empty scope10 ms0044
Scenario: Count connections in scope8 ms0055
Scenario: Count domains in a blank database6 ms0044
Scenario: Count domains in the database6 ms0077
Scenario: Count groups5 ms001414
Scenario: Count groups in a blank database10 ms0055
Scenario: Count job items3 ms0077
Scenario: Count job items in wrong - empty - scope3 ms0088
Scenario: Count role permissions in specific scopes3 ms001818
Scenario: Count roles in specific scopes7 ms001515
Scenario: Count step definition items5 ms0044
Scenario: Count step definitions in wrong (empty) scope5 ms0011
Scenario: Count steps in the database4 ms001515
Scenario: Count user4 ms0066
Scenario: Create and count several execution items for a job5 ms001212
Scenario: Create index with specific prefix11 ms001212
Scenario: Create multiple users4 ms0055
Scenario: Create regular access permissions2 ms002020
Scenario: Create some regular role permissions9 ms0099
Scenario: Create user that already exist4 ms0077
Scenario: Create user that has more than DB allowed length6 ms0055
Scenario: Create user with short name5 ms0055
Scenario: Create user with special characters in his name6 ms0055
Scenario: Create with permissions5 ms001414
Scenario: Create with permissions and a role7 ms001717
Scenario: Create with permissions and a role in the wrong scope4 ms001515
Scenario: Creating index with regular user10 ms002525
Scenario: Creating new device and tagging it with specific Tag10 ms001414
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag9 ms001616
Scenario: Creating tag31 ms0044
Scenario: Creating two indexes with daily index15 ms001717
Scenario: Creating two indexes with hourly index7 ms001717
Scenario: Creating two indexes with weekly index7 ms001717
Scenario: Creating user21 ms0055
Scenario: Creation of access role with neither acess info and role entities4 ms001212
Scenario: Creation of access role without an acess info entity4 ms001212
Scenario: D1 Device publish to CTRL_ACC_REPLY9 ms2259
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI7 ms0099
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed6 ms2259
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed9 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY9 ms2259
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY5 ms0099
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account30 ms2259
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC18 ms0099
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI6 ms0099
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed6 ms2259
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed12 ms2259
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed6 ms2248
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed15 ms2259
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI6 ms0099
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed9 ms2259
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed6 ms2248
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY7 ms2259
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY7 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account9 ms2259
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed7 ms0099
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed6 ms0099
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed6 ms2248
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI8 ms0099
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC8 ms0099
Scenario: DV1 Data view publish to CTRL_ACC_REPLY7 ms2259
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed19 ms2259
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed6 ms001010
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed7 ms0099
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed8 ms0099
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed9 ms2259
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed14 ms2248
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY7 ms2259
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY12 ms0099
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account7 ms2259
Scenario: DV5 Data view publish to CTRL_ACC is not allowed8 ms0099
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed6 ms0099
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed9 ms2248
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI11 ms0099
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed6 ms2259
Scenario: Delete Kapua system user4 ms0055
Scenario: Delete a access info entity with permissions and roles3 ms001717
Scenario: Delete a connection from the database3 ms0088
Scenario: Delete a group from the database4 ms001010
Scenario: Delete a group from the database - Unknown group ID4 ms0066
Scenario: Delete a job4 ms001111
Scenario: Delete a job execution item4 ms0099
Scenario: Delete a job execution item twice3 ms001010
Scenario: Delete a job twice4 ms001010
Scenario: Delete a non existing connection3 ms0077
Scenario: Delete a non existing permission entity8 ms001616
Scenario: Delete a non existing role entry10 ms001111
Scenario: Delete a non-existing step6 ms001313
Scenario: Delete a nonexistent domain8 ms0055
Scenario: Delete a step definition6 ms0088
Scenario: Delete a step definition twice5 ms0077
Scenario: Delete access role from user14 ms001212
Scenario: Delete an access info entity twice5 ms001111
Scenario: Delete an access info entity using the wrong scope ID5 ms001111
Scenario: Delete an existing access info entity5 ms001212
Scenario: Delete an existing access permission entity3 ms001515
Scenario: Delete an existing access role entry7 ms002222
Scenario: Delete an existing account4 ms0055
Scenario: Delete an existing role11 ms001010
Scenario: Delete an existing role twice3 ms001616
Scenario: Delete an existing step5 ms001212
Scenario: Delete items based on query results24 ms008484
Scenario: Delete items by date ranges0.34 sec00132132
Scenario: Delete items by the datastore ID22 ms006666
Scenario: Delete middle child expiration13 ms001515
Scenario: Delete nonexisting account7 ms0044
Scenario: Delete nonexisting role permission9 ms001313
Scenario: Delete parent expiration10 ms001414
Scenario: Delete permissions from role10 ms001818
Scenario: Delete role permissions9 ms001010
Scenario: Delete the Kapua system account1 ms0055
Scenario: Delete the last created domain entry13 ms0088
Scenario: Delete user5 ms0066
Scenario: Delete user that doesn't exist3 ms0055
Scenario: Deleting a Permission15 ms002121
Scenario: Deleting tag8 ms0044
Scenario: Deleting user in account that is higher in hierarchy18 ms002323
Scenario: Deleting user in account that is lower in hierarchy15 ms002424
Scenario: Device connection update9 ms0077
Scenario: Domain entry query6 ms0055
Scenario: Domain with null actions2 ms0055
Scenario: Domain with null name4 ms0055
Scenario: Domains with duplicate names3 ms0088
Scenario: Duplicate group name in root scope5 ms001010
Scenario: Duplicate role names10 ms0077
Scenario: Empty query results are supported13 ms0088
Scenario: Every account must have the default configuration items4 ms0033
Scenario: Find a connection by its IDs4 ms0066
Scenario: Find a connection by its client ID6 ms0066
Scenario: Find a group entry in the database3 ms0099
Scenario: Find account by Id6 ms0044
Scenario: Find account by Ids5 ms0044
Scenario: Find account by name4 ms0044
Scenario: Find account by random Id5 ms0033
Scenario: Find all child accounts9 ms0033
Scenario: Find an access info entity9 ms001111
Scenario: Find an access info entity by user ID5 ms001010
Scenario: Find an existing access role entity4 ms001313
Scenario: Find by name nonexisting account4 ms0033
Scenario: Find correct number of messages by corresponding metric19 ms4381658
Scenario: Find last created permission5 ms001212
Scenario: Find multiple users3 ms0055
Scenario: Find role by ID3 ms0077
Scenario: Find self account by id6 ms001111
Scenario: Find self account by id and scope id9 ms001111
Scenario: Find self account by name7 ms001111
Scenario: Find the last created domain entry3 ms0055
Scenario: Find user by id4 ms0055
Scenario: Find user by name5 ms0055
Scenario: Find user by name that doesn't exist3 ms0033
Scenario: Find user with id and scope id that doesn't exist3 ms0033
Scenario: Finding all messages by selecting all metrics19 ms4201640
Scenario: Finding correct number of messages by corresponding two metrics5 ms4321652
Scenario: Finding messages with incorrect metric parameters14 ms4521672
Scenario: Generic connection query4 ms0088
Scenario: Get metadata4 ms0033
Scenario: Group with a null name2 ms0077
Scenario: Handle account creation19 ms0033
Scenario: Handle duplicate account names9 ms0055
Scenario: Handle null account name1 ms0044
Scenario: Handling of 2 birth messages9 ms001212
Scenario: Handling of a disconnect message from a non existing device7 ms001010
Scenario: I try to find a non-existing connection5 ms0066
Scenario: If user credential expiration date is before today, user can not login4 ms001414
Scenario: If user credential expiration date is today, user can not login it is day inclusive3 ms001414
Scenario: If user credential expiration date is tomorrow, user can login10 ms001313
Scenario: If user credential is in state disabled, user can not login11 ms001414
Scenario: If user credential is in state enabled, user can login9 ms001313
Scenario: If user expiration date is before today, user can not login11 ms001313
Scenario: If user expiration date is today, user can not login because expiration date was reached7 ms001313
Scenario: If user expiration date is tomorrow, user can login3 ms001212
Scenario: Installing a package12 ms27413
Scenario: It is possible to change the configuration items2 ms0044
Scenario: It must be possible to query for specific entries in the role database10 ms0088
Scenario: Job execution factory sanity checks4 ms0022
Scenario: Job factory sanity checks4 ms0033
Scenario: Job with a duplicate name17 ms0099
Scenario: Job with a null name17 ms0088
Scenario: Job with a null scope ID4 ms0099
Scenario: Job with an empty name4 ms0099
Scenario: MetricsInfo client ID and topic data based on the client id26 ms003434
Scenario: MetricsInfo last published date26 ms004848
Scenario: Modify a role that was deleted8 ms0099
Scenario: Modify an existing account4 ms0044
Scenario: Modify last child expiration so that it still expires before parent9 ms001414
Scenario: Modify middle child expiration so that it still expires before parent3 ms001414
Scenario: Modify middle child expiration to outlive parent12 ms001515
Scenario: Modify nonexisting account3 ms0066
Scenario: Modify parent expiration so that it still expires after child2 ms001414
Scenario: Modify parent expiration to before child expiration13 ms001515
Scenario: Nameless role entry8 ms0077
Scenario: Negative scenario when client connects twice with same client id17 ms001111
Scenario: Permission factory sanity checks3 ms0033
Scenario: Positive scenario without stealing link10 ms001212
Scenario: Query based on message ordering27 ms002020
Scenario: Query based on metrics ordering33 ms002020
Scenario: Query before schema search33 ms008282
Scenario: Query for a specific group by name9 ms001616
Scenario: Query for all the access info entities of a specific user4 ms001818
Scenario: Query for all the access info entities of an invalid user4 ms001010
Scenario: Query for executions of a specific job4 ms001919
Scenario: Query for jobs with specified name4 ms0099
Scenario: Query for step definitions4 ms0077
Scenario: Query user6 ms0066
Scenario: Regular connection20 ms0077
Scenario: Regular creation of Access Role entity8 ms001414
Scenario: Regular domain10 ms0055
Scenario: Regular group in random scope4 ms0077
Scenario: Regular group in root scope6 ms0077
Scenario: Regular job creation3 ms001010
Scenario: Regular job execution creation1 ms0088
Scenario: Regular role creation12 ms0099
Scenario: Regular step creation3 ms001212
Scenario: Regular step definition creation20 ms0077
Scenario: Regular step definition with a property list21 ms0044
Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The First Time7 ms232539
Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The Second Time6 ms239647
Scenario: Restarting Job With Invalid "Bundle Start", multiple devices And Step Index=0 For The First Time12 ms2+232+325+539+39
Scenario: Restarting Job With Invalid "Bundle Start", multiple devices And Step Index=0 For The Second Time9 ms2+239+396+647+47
Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The First Time10 ms231639
Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The Second Time7 ms244652
Scenario: Restarting Job With Invalid "Bundle Stop", multiple devices And Step Index=0 For The First Time6 ms2+231+316+639+39
Scenario: Restarting Job With Invalid "Bundle Stop", multiple devices And Step Index=0 For The Second Time7 ms2+244+446+652+52
Scenario: Restarting Job With Invalid "Command Execution" And Step Index=0 For The First Time3 ms225734
Scenario: Restarting Job With Invalid "Command Execution" And Step Index=0 For The Second Time4 ms233742
Scenario: Restarting Job With Invalid "Command Execution", multiple devices And Step Index=0 For The First Time5 ms2+226+267+735+35
Scenario: Restarting Job With Invalid "Command Execution", multiple devices And Step Index=0 For The Second Time4 ms2+234+347+743+43
Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The First Time9 ms232539
Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The Second Time10 ms243651
Scenario: Restarting Job With Valid "Bundle Start", multiple devices And Step Index=0 For The First Time9 ms2+232+325+539+39
Scenario: Restarting Job With Valid "Bundle Start", multiple devicess And Step Index=0 For The Second Time7 ms2+243+436+651+51
Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The First Time6 ms231639
Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The Second Time3 ms244652
Scenario: Restarting Job With Valid "Bundle Stop", multiple devices And Step Index=0 For The First Time8 ms2+231+316+639+39
Scenario: Restarting Job With Valid "Bundle Stop", multiple devices And Step Index=0 For The Second Time7 ms2+244+446+652+52
Scenario: Restarting Job With Valid "Command Execution" And Step Index=0 For The First Time3 ms225734
Scenario: Restarting Job With Valid "Command Execution" And Step Index=0 For The Second Time3 ms233742
Scenario: Restarting Job With Valid "Command Execution", multiple devices And Step Index=0 For The First Time3 ms2+226+267+735+35
Scenario: Restarting Job With Valid "Command Execution", multiple devices And Step Index=0 For The Second Time3 ms2+234+347+743+43
Scenario: Restarting a job with Asset Write and Bundle Start steps7 ms224430
Scenario: Restarting a job with Command Execution and Bundle Start steps6 ms224430
Scenario: Restarting a job with Configuration Put and Bundle Start steps7 ms224430
Scenario: Restarting a job with Package Uninstall and Bundle Start steps10 ms226432
Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices7 ms227433
Scenario: Restarting job with Asset Write step10 ms2131025
Scenario: Restarting job with Asset Write step and multiple devices7 ms222428
Scenario: Restarting job with Bundle Start step7 ms221427
Scenario: Restarting job with Bundle Start step and multiple devices9 ms224430
Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices7 ms229435
Scenario: Restarting job with Bundle Stop and Bundle Start steps5 ms226432
Scenario: Restarting job with Bundle Stop step5 ms221427
Scenario: Restarting job with Bundle Stop step and multiple devices5 ms224430
Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices9 ms227433
Scenario: Restarting job with Command Execution step3 ms2131025
Scenario: Restarting job with Command Execution step and multiple devices5 ms222428
Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices11 ms227433
Scenario: Restarting job with Configuration Put step4 ms2131025
Scenario: Restarting job with Configuration Put step and multiple devices6 ms222428
Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices21 ms455867
Scenario: Restarting job with Package Download/Install step and multiple devices7 ms223429
Scenario: Restarting job with Package Install step0 ms221427
Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device10 ms230436
Scenario: Restarting job with Package Uninstall step7 ms221427
Scenario: Restarting job with Package Uninstall step and multiple device5 ms224430
Scenario: Restarting job with two Bundle Start steps5 ms226432
Scenario: Restarting job with two Bundle Start steps and multiple devices7 ms229435
Scenario: Role creator sanity checks3 ms0022
Scenario: Role entry with no actions3 ms0066
Scenario: Role object equality check6 ms0022
Scenario: Role service related objects sanity checks3 ms0044
Scenario: Search for a non existent client ID5 ms0066
Scenario: Search for an access info entity by an incorrect user ID6 ms001111
Scenario: Search the role database for a random ID7 ms0077
Scenario: Send BIRTH message and then DC message5 ms27615
Scenario: Send BIRTH message and then DC message while broker ip is NOT set17 ms0066
Scenario: Send BIRTH message and then DC message while broker ip is set by System3 ms2248
Scenario: Send BIRTH message and then DC message while broker ip is set by config file3 ms2248
Scenario: Set environment variables0.23 sec005555
Scenario: Setting configuration without mandatory items must raise an error4 ms0055
Scenario: Simple create6 ms001111
Scenario: Simple positive scenario for creating daily index8 ms001414
Scenario: Simple positive scenario for creating default - weekly index9 ms001212
Scenario: Simple positive scenario for creating hourly index13 ms001414
Scenario: Start broker for all scenarios91 ms38-20038-2
Scenario: Start datastore for all scenarios2.1 sec003232
Scenario: Start event broker for all scenarios0.36 sec0044-244-2
Scenario: Starting a job with Asset Write and Bundle Start steps9 ms233540
Scenario: Starting a job with Asset Write step6 ms2131429
Scenario: Starting a job with Bundle Start step10 ms231538
Scenario: Starting a job with Bundle Stop and Bundle Start steps10 ms234642
Scenario: Starting a job with Bundle Stop step13 ms230638
Scenario: Starting a job with Command Execution and Bundle Start steps9 ms234541
Scenario: Starting a job with Command Execution step8 ms2131429
Scenario: Starting a job with Configuration Put and Bundle Start steps7 ms232640
Scenario: Starting a job with Configuration Put step6 ms2131429
Scenario: Starting a job with Package Install Command step7 ms231538
Scenario: Starting a job with Package Install and Bundle Start steps10 ms238545
Scenario: Starting a job with Package Uninstall Command step5 ms233540
Scenario: Starting a job with Package Uninstall and Bundle Start steps7 ms235542
Scenario: Starting a job with invalid Bundle Start step7 ms232539
Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps5 ms236644
Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps and multiple devices6 ms2+236+366+644+44
Scenario: Starting a job with invalid Bundle Stop step10 ms231639
Scenario: Starting a job with invalid Bundle Stop step and multiple devices2 ms2+231+316+639+39
Scenario: Starting a job with invalid Command Execution step3 ms226735
Scenario: Starting a job with two Bundle Start steps7 ms236543
Scenario: Starting a job with two invalid Bundle Start steps16 ms237544
Scenario: Starting a job with two invalid Bundle Start steps and multiple devices6 ms2+237+375+544+44
Scenario: Starting a job with two valid Bundle Start steps5 ms237544
Scenario: Starting a job with two valid Bundle Start steps and multiple devices5 ms2+237+375+544+44
Scenario: Starting a job with valid Bundle Start step12 ms232539
Scenario: Starting a job with valid Bundle Stop and Bundle Start steps5 ms236644
Scenario: Starting a job with valid Bundle Stop and Bundle Start steps and multiple devices5 ms2+236+366+644+44
Scenario: Starting a job with valid Bundle Stop step10 ms231639
Scenario: Starting a job with valid Bundle Stop step and multiple devices4 ms2+231+316+639+39
Scenario: Starting a job with valid Command Execution step3 ms226735
Scenario: Starting and stopping the simulator should create a device entry and properly set its status10 ms214420
Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices5 ms2181535
Scenario: Starting job with Asset Write step and multiple devices7 ms2141531
Scenario: Starting job with Bundle Start step and multiple devices3 ms2141531
Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices2 ms2181535
Scenario: Starting job with Bundle Stop step and multiple devices3 ms2141531
Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices3 ms2181535
Scenario: Starting job with Command Execution step and multiple devices1 ms2141531
Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices4 ms2181535
Scenario: Starting job with Configuration Put step and multiple devices3 ms2141531
Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices7 ms235542
Scenario: Starting job with Package Download/Install step and multiple devices6 ms231538
Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device3 ms2181535
Scenario: Starting job with Package Uninstall step and multiple device8 ms2141531
Scenario: Starting job with invalid Bundle Start step and multiple devices6 ms2+232+325+539+39
Scenario: Starting job with invalid Command Execution and Bundle Start steps10 ms2+238+385+545+45
Scenario: Starting job with invalid Command Execution step and multiple devices0 ms2+230+305+537+37
Scenario: Starting job with invalid Command Execution, invalid Bundle Start steps and multiple devices19 ms2+238+385+545+45
Scenario: Starting job with two Bundle Start steps and multiple devices3 ms2181535
Scenario: Starting job with valid Bundle Start step and multiple devices6 ms2+233+335+540+40
Scenario: Starting job with valid Command Execution and Bundle Start steps7 ms2+238+385+545+45
Scenario: Starting job with valid Command Execution step and multiple devices4 ms2+230+305+537+37
Scenario: Starting job with valid Command Execution, valid Bundle Start steps and multiple devices5 ms2+238+385+545+45
Scenario: Stealing link scenario10 ms2141228
Scenario: Step definition factory sanity checks5 ms0022
Scenario: Step definition with a duplicate name6 ms0066
Scenario: Step definition with a null name10 ms0066
Scenario: Step definition with a null scope ID12 ms0066
Scenario: Step definition with an empty name14 ms0055
Scenario: Step factory sanity checks4 ms0022
Scenario: Step with a null scope ID5 ms001212
Scenario: Stop broker after all scenarios0.34 sec0040-240-2
Scenario: Stop datastore after all scenarios0.18 sec003232
Scenario: Stop event broker for all scenarios0.41 sec0044-244-2
Scenario: Test account query6 ms0044
Scenario: Test the message store with server timestamp indexing20 ms002626
Scenario: Test the message store with timestamp indexing26 ms002626
Scenario: The Client ID is case sensitive6 ms0088
Scenario: To be defined4 ms001313
Scenario: Try to change an existing connection ID5 ms0077
Scenario: Try to create an access into entity with an invalid role id8 ms001212
Scenario: Try to modify the connection client ID10 ms0077
Scenario: Unknown configuiration items are silently ignored3 ms0044
Scenario: Update a group entry in the database13 ms0099
Scenario: Update a group entry with a false ID2 ms001010
Scenario: Update a job XML definition6 ms001010
Scenario: Update a job description3 ms001010
Scenario: Update a job name4 ms001010
Scenario: Update a nonexistent job5 ms001010
Scenario: Update a nonexistent step definition4 ms0077
Scenario: Update a step definition name5 ms0077
Scenario: Update a step definition processor name5 ms0088
Scenario: Update a step definition target type6 ms0088
Scenario: Update existing role name13 ms0088
Scenario: Update job id of an existing execution item2 ms0099
Scenario: Update the end time of an existing execution item3 ms001010
Scenario: Update user6 ms0077
Scenario: Update user that doesn't exist4 ms0055
Scenario: User locking itself out by using out login attempts4 ms001616
Scenario: User locking itself out with failed attempts and not waiting to unlock7 ms001717
Scenario: User locking itself out with failed attempts and waiting to unlock15 ms001717
Scenario: User login with wrong pass, but with enough time between login failures5 ms001919
Scenario: User not locking itself out by using less than max failed login attempts5 ms001717
empty) scope0 ms0044