Test Result : (root)

304 failures (+28) , 3,534 skipped (+359)
9,059 tests (+443)
Took 7.7 sec.

All Failed Tests

Test NameDurationAge
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY4 ms16
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"3 ms16
 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 ms16
 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"4 ms16
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed4 ms16
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown3 ms16
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms16
 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"4 ms16
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed6 ms16
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown4 ms16
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY4 ms16
 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"3 ms16
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account5 ms16
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown4 ms16
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed5 ms16
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Then An exception was thrown4 ms16
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed6 ms16
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"5 ms16
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data3 ms16
 Scenario: Connect to the system and publish some data.Then Device sim-1 for account kapua-sys is registered after 5 seconds3 ms16
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY4 ms16
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"2 ms16
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed4 ms16
 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"3 ms16
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY5 ms16
 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"3 ms16
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account3 ms16
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown2 ms16
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed14 ms16
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"3 ms16
 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 ms16
 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"2 ms16
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed4 ms16
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown3 ms16
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed9 ms16
 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"4 ms16
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed4 ms16
 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"3 ms16
 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 allowed3 ms16
 Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown1 ms16
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY5 ms16
 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"4 ms16
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account7 ms16
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown6 ms16
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed4 ms16
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Then An exception was thrown2 ms16
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY6 ms16
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"4 ms16
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed4 ms16
 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"2 ms16
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed6 ms16
 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"5 ms16
 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 allowed5 ms16
 Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown4 ms16
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY4 ms16
 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"2 ms16
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account5 ms16
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown4 ms16
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed3 ms16
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Then An exception was thrown2 ms16
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed4 ms16
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"2 ms16
 Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode.And The connection status is "CONNECTED"1 ms14
 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 mode11 ms14
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode.And The connection status is "CONNECTED"2 ms14
 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 mode4 ms14
 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 ms14
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices.Then I find 1 connection3 ms14
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric2 ms7
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric2 ms7
 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 ms7
 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 ms7
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics2 ms7
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics1 ms7
 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 ms7
 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 ms7
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics2 ms7
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics2 ms7
 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 ms7
 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 ms7
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters3 ms7
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters3 ms7
 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 ms7
 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 ms7
 Scenario: Installing a package.Scenario: Installing a package5 ms16
 Scenario: Installing a package.Then Device sim-1 for account kapua-sys is registered after 5 seconds3 ms16
 Scenario: New connection with reserved ID.And The connection status is "CONNECTED"2 ms14
 Scenario: New connection with reserved ID.Scenario: New connection with reserved ID3 ms14
 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 Time5 ms7
 Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The First Time.Then Device status is "CONNECTED"4 ms9
 Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The Second Time.And Bundles are requested2 ms9
 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 ms7
 Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The First Time.And Bundles are requested4 ms9
 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 Time5 ms7
 Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The Second Time.And Bundles are requested2 ms9
 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 ms7
 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 ms7
 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 ms8
 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 ms7
 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"2 ms8
 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 ms7
 Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The First Time.Then Device status is "CONNECTED"3 ms9
 Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The Second Time.And Bundles are requested3 ms9
 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 Time4 ms7
 Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The First Time.And Bundles are requested2 ms9
 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 ms7
 Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The Second Time.And Bundles are requested4 ms9
 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 Time6 ms7
 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 ms7
 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"2 ms8
 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 ms7
 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 ms8
 Scenario: Restarting a job with Asset Write and Bundle Start steps.Scenario: Restarting a job with Asset Write and Bundle Start steps4 ms2
 Scenario: Restarting a job with Asset Write and Bundle Start steps.Then Device status is "CONNECTED"3 ms9
 Scenario: Restarting a job with Command Execution and Bundle Start steps.Scenario: Restarting a job with Command Execution and Bundle Start steps4 ms2
 Scenario: Restarting a job with Command Execution and Bundle Start steps.Then Device status is "CONNECTED"3 ms9
 Scenario: Restarting a job with Configuration Put and Bundle Start steps.Scenario: Restarting a job with Configuration Put and Bundle Start steps5 ms2
 Scenario: Restarting a job with Configuration Put and Bundle Start steps.Then Device status is "CONNECTED"3 ms9
 Scenario: Restarting a job with Package Uninstall and Bundle Start steps.Scenario: Restarting a job with Package Uninstall and Bundle Start steps19 ms2
 Scenario: Restarting a job with Package Uninstall and Bundle Start steps.Then Device status is "CONNECTED"19 ms9
 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 ms1
 Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"2 ms9
 Scenario: Restarting job with Asset Write step.And A new job target item2 ms9
 Scenario: Restarting job with Asset Write step.Scenario: Restarting job with Asset Write step2 ms2
 Scenario: Restarting job with Asset Write step and multiple devices.Scenario: Restarting job with Asset Write step and multiple devices3 ms1
 Scenario: Restarting job with Asset Write step and multiple devices.Then Device status is "CONNECTED"2 ms9
 Scenario: Restarting job with Bundle Start step.Scenario: Restarting job with Bundle Start step5 ms2
 Scenario: Restarting job with Bundle Start step.Then Device status is "CONNECTED"4 ms9
 Scenario: Restarting job with Bundle Start step and multiple devices.Scenario: Restarting job with Bundle Start step and multiple devices4 ms1
 Scenario: Restarting job with Bundle Start step and multiple devices.Then Device status is "CONNECTED"2 ms9
 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 ms1
 Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices.Then Device status is "CONNECTED"2 ms9
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.Scenario: Restarting job with Bundle Stop and Bundle Start steps4 ms2
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.Then Device status is "CONNECTED"2 ms9
 Scenario: Restarting job with Bundle Stop step.Scenario: Restarting job with Bundle Stop step4 ms2
 Scenario: Restarting job with Bundle Stop step.Then Device status is "CONNECTED"3 ms9
 Scenario: Restarting job with Bundle Stop step and multiple devices.Scenario: Restarting job with Bundle Stop step and multiple devices7 ms1
 Scenario: Restarting job with Bundle Stop step and multiple devices.Then Device status is "CONNECTED"7 ms9
 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 devices4 ms1
 Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"2 ms9
 Scenario: Restarting job with Command Execution step.And A new job target item2 ms9
 Scenario: Restarting job with Command Execution step.Scenario: Restarting job with Command Execution step2 ms2
 Scenario: Restarting job with Command Execution step and multiple devices.Scenario: Restarting job with Command Execution step and multiple devices4 ms1
 Scenario: Restarting job with Command Execution step and multiple devices.Then Device status is "CONNECTED"3 ms9
 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 devices6 ms1
 Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"4 ms9
 Scenario: Restarting job with Configuration Put step.And A new job target item1 ms9
 Scenario: Restarting job with Configuration Put step.Scenario: Restarting job with Configuration Put step2 ms2
 Scenario: Restarting job with Configuration Put step and multiple devices.Scenario: Restarting job with Configuration Put step and multiple devices4 ms1
 Scenario: Restarting job with Configuration Put step and multiple devices.Then Device status is "CONNECTED"2 ms9
 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 devices4 ms2
 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 devices5 ms2
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"3 ms9
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"3 ms9
 Scenario: Restarting job with Package Download/Install step and multiple devices.Scenario: Restarting job with Package Download/Install step and multiple devices5 ms1
 Scenario: Restarting job with Package Download/Install step and multiple devices.Then Device status is "CONNECTED"4 ms9
 Scenario: Restarting job with Package Install step.Scenario: Restarting job with Package Install step4 ms2
 Scenario: Restarting job with Package Install step.Then Device status is "CONNECTED"3 ms9
 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 device4 ms1
 Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device.Then Device status is "CONNECTED"3 ms9
 Scenario: Restarting job with Package Uninstall step.Scenario: Restarting job with Package Uninstall step3 ms2
 Scenario: Restarting job with Package Uninstall step.Then Device status is "CONNECTED"2 ms9
 Scenario: Restarting job with Package Uninstall step and multiple device.Scenario: Restarting job with Package Uninstall step and multiple device5 ms1
 Scenario: Restarting job with Package Uninstall step and multiple device.Then Device status is "CONNECTED"4 ms9
 Scenario: Restarting job with two Bundle Start steps.Scenario: Restarting job with two Bundle Start steps5 ms2
 Scenario: Restarting job with two Bundle Start steps.Then Device status is "CONNECTED"4 ms9
 Scenario: Restarting job with two Bundle Start steps and multiple devices.Scenario: Restarting job with two Bundle Start steps and multiple devices4 ms1
 Scenario: Restarting job with two Bundle Start steps and multiple devices.Then Device status is "CONNECTED"3 ms9
 Scenario: Send BIRTH message and then DC message.And Bundles are requested2 ms16
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message2 ms16
 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 ms16
 Scenario: Send BIRTH message and then DC message while broker ip is set by System.Then Device is connected with "localhost" server ip1 ms16
 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 ms16
 Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Then Device is connected with "localhost" server ip2 ms16
 Scenario: Start broker for all scenarios.Given Start Broker1 ms16
 Scenario: Start broker for all scenarios.Given Start Broker1 ms14
 Scenario: Start broker for all scenarios.Given Start Broker1 ms16
 Scenario: Start broker for all scenarios.Given Start Broker2 ms16
 Scenario: Start broker for all scenarios.Given Start Broker0 ms14
 Scenario: Start broker for all scenarios.Given Start Broker2 ms9
 Scenario: Start broker for all scenarios.Given Start Broker2 ms14
 Scenario: Start broker for all scenarios.Given Start Broker2 ms16
 Scenario: Start broker for all scenarios.Given Start Broker15 ms16
 Scenario: Start broker for all scenarios.Given Start Broker1 ms9
 Scenario: Start broker for all scenarios.Given Start Broker1 ms16
 Scenario: Start broker for all scenarios.Given Start Broker0 ms16
 Scenario: Start broker for all scenarios.Given Start Broker2 ms9
 Scenario: Start broker for all scenarios.Given Start Broker1 ms16
 Scenario: Start broker for all scenarios.Given Start Broker1 ms16
 Scenario: Start broker for all scenarios.Given Start Broker1 ms14
 Scenario: Start broker for all scenarios.Given Start Broker1 ms16
 Scenario: Start broker for all scenarios.Given Start Broker2 ms16
 Scenario: Start broker for all scenarios.Given Start Broker1 ms9
 Scenario: Start broker for all scenarios.Given Start Broker2 ms9
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0 ms14
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0 ms16
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms9
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms16
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms16
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms16
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms16
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms16
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms9
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms16
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms16
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms9
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms14
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms16
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms14
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios16 ms16
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms9
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms9
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms16
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms14
 Scenario: Starting a job with Asset Write and Bundle Start steps.Scenario: Starting a job with Asset Write and Bundle Start steps3 ms9
 Scenario: Starting a job with Asset Write and Bundle Start steps.Then Device status is "CONNECTED"2 ms9
 Scenario: Starting a job with Asset Write step.And A new job target item1 ms9
 Scenario: Starting a job with Asset Write step.Scenario: Starting a job with Asset Write step2 ms9
 Scenario: Starting a job with Bundle Start step.Scenario: Starting a job with Bundle Start step5 ms9
 Scenario: Starting a job with Bundle Start step.Then Device status is "CONNECTED"3 ms9
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.And Bundles are requested2 ms9
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.Scenario: Starting a job with Bundle Stop and Bundle Start steps4 ms9
 Scenario: Starting a job with Bundle Stop step.And Bundles are requested2 ms9
 Scenario: Starting a job with Bundle Stop step.Scenario: Starting a job with Bundle Stop step4 ms9
 Scenario: Starting a job with Command Execution and Bundle Start steps.Scenario: Starting a job with Command Execution and Bundle Start steps4 ms9
 Scenario: Starting a job with Command Execution and Bundle Start steps.Then Device status is "CONNECTED"3 ms9
 Scenario: Starting a job with Command Execution step.And A new job target item2 ms9
 Scenario: Starting a job with Command Execution step.Scenario: Starting a job with Command Execution step2 ms9
 Scenario: Starting a job with Configuration Put and Bundle Start steps.And Bundles are requested3 ms9
 Scenario: Starting a job with Configuration Put and Bundle Start steps.Scenario: Starting a job with Configuration Put and Bundle Start steps4 ms9
 Scenario: Starting a job with Configuration Put step.And A new job target item3 ms9
 Scenario: Starting a job with Configuration Put step.Scenario: Starting a job with Configuration Put step3 ms9
 Scenario: Starting a job with Package Install Command step.Scenario: Starting a job with Package Install Command step3 ms9
 Scenario: Starting a job with Package Install Command step.Then Device status is "CONNECTED"2 ms9
 Scenario: Starting a job with Package Install and Bundle Start steps.Scenario: Starting a job with Package Install and Bundle Start steps6 ms9
 Scenario: Starting a job with Package Install and Bundle Start steps.Then Device status is "CONNECTED"4 ms9
 Scenario: Starting a job with Package Uninstall Command step.Scenario: Starting a job with Package Uninstall Command step4 ms9
 Scenario: Starting a job with Package Uninstall Command step.Then Device status is "CONNECTED"3 ms9
 Scenario: Starting a job with Package Uninstall and Bundle Start steps.Scenario: Starting a job with Package Uninstall and Bundle Start steps4 ms9
 Scenario: Starting a job with Package Uninstall and Bundle Start steps.Then Device status is "CONNECTED"3 ms9
 Scenario: Starting a job with invalid Bundle Start step.Scenario: Starting a job with invalid Bundle Start step3 ms8
 Scenario: Starting a job with invalid Bundle Start step.Then Device status is "CONNECTED"2 ms9
 Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps.And Bundles are requested2 ms9
 Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps.Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps3 ms8
 Scenario: Starting a job with invalid Bundle Stop step.And Bundles are requested2 ms9
 Scenario: Starting a job with invalid Bundle Stop step.Scenario: Starting a job with invalid Bundle Stop step4 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 ms8
 Scenario: Starting a job with two Bundle Start steps.Scenario: Starting a job with two Bundle Start steps4 ms9
 Scenario: Starting a job with two Bundle Start steps.Then Device status is "CONNECTED"3 ms9
 Scenario: Starting a job with two invalid Bundle Start steps.Scenario: Starting a job with two invalid Bundle Start steps4 ms8
 Scenario: Starting a job with two invalid Bundle Start steps.Then Device status is "CONNECTED"2 ms9
 Scenario: Starting a job with two valid Bundle Start steps.Scenario: Starting a job with two valid Bundle Start steps4 ms8
 Scenario: Starting a job with two valid Bundle Start steps.Then Device status is "CONNECTED"3 ms9
 Scenario: Starting a job with valid Bundle Start step.Scenario: Starting a job with valid Bundle Start step3 ms8
 Scenario: Starting a job with valid Bundle Start step.Then Device status is "CONNECTED"2 ms9
 Scenario: Starting a job with valid Bundle Stop and Bundle Start steps.And Bundles are requested3 ms9
 Scenario: Starting a job with valid Bundle Stop and Bundle Start steps.Scenario: Starting a job with valid Bundle Stop and Bundle Start steps4 ms8
 Scenario: Starting a job with valid Bundle Stop step.And Bundles are requested2 ms9
 Scenario: Starting a job with valid Bundle Stop step.Scenario: Starting a job with valid Bundle Stop step3 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"2 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 status4 ms16
 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 seconds3 ms16
 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 ms6
 Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices.Then I count 21 ms7
 Scenario: Starting job with Asset Write step and multiple devices.Scenario: Starting job with Asset Write step and multiple devices2 ms6
 Scenario: Starting job with Asset Write step and multiple devices.Then I count 21 ms7
 Scenario: Starting job with Bundle Start step and multiple devices.Scenario: Starting job with Bundle Start step and multiple devices2 ms6
 Scenario: Starting job with Bundle Start step and multiple devices.Then I count 21 ms7
 Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices.Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices2 ms6
 Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices.Then I count 21 ms7
 Scenario: Starting job with Bundle Stop step and multiple devices.Scenario: Starting job with Bundle Stop step and multiple devices2 ms6
 Scenario: Starting job with Bundle Stop step and multiple devices.Then I count 21 ms7
 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 ms6
 Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices.Then I count 21 ms7
 Scenario: Starting job with Command Execution step and multiple devices.Scenario: Starting job with Command Execution step and multiple devices1 ms6
 Scenario: Starting job with Command Execution step and multiple devices.Then I count 21 ms7
 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 ms6
 Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices.Then I count 21 ms7
 Scenario: Starting job with Configuration Put step and multiple devices.Scenario: Starting job with Configuration Put step and multiple devices1 ms6
 Scenario: Starting job with Configuration Put step and multiple devices.Then I count 21 ms7
 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 ms6
 Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"2 ms9
 Scenario: Starting job with Package Download/Install step and multiple devices.Scenario: Starting job with Package Download/Install step and multiple devices3 ms6
 Scenario: Starting job with Package Download/Install step and multiple devices.Then Device status is "CONNECTED"2 ms9
 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 device4 ms6
 Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device.Then I count 21 ms7
 Scenario: Starting job with Package Uninstall step and multiple device.Scenario: Starting job with Package Uninstall step and multiple device3 ms6
 Scenario: Starting job with Package Uninstall step and multiple device.Then I count 22 ms7
 Scenario: Starting job with two Bundle Start steps and multiple devices.Scenario: Starting job with two Bundle Start steps and multiple devices2 ms6
 Scenario: Starting job with two Bundle Start steps and multiple devices.Then I count 22 ms7
 Scenario: Stealing link scenario.And Client named "client-2" is not connected3 ms16
 Scenario: Stealing link scenario.Scenario: Stealing link scenario5 ms16
 Scenario: Test LOOSE user coupling on single connection.And The connection status is "CONNECTED"2 ms14
 Scenario: Test LOOSE user coupling on single connection.Scenario: Test LOOSE user coupling on single connection4 ms14
 Scenario: Test LOOSE user coupling with 3 connections.And The connection status is "CONNECTED"3 ms14
 Scenario: Test LOOSE user coupling with 3 connections.Scenario: Test LOOSE user coupling with 3 connections4 ms14
 Scenario: Test STRICT user coupling on single connection.And The connection status is "CONNECTED"1 ms14
 Scenario: Test STRICT user coupling on single connection.Scenario: Test STRICT user coupling on single connection2 ms14
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.And The connection status is "CONNECTED"10 ms14
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.Scenario: Test STRICT user coupling with 3 connections and a reserved user10 ms14
 Scenario: Test STRICT user coupling with user change allowed on single connection.And The connection status is "CONNECTED"2 ms14
 Scenario: Test STRICT user coupling with user change allowed on single connection.Scenario: Test STRICT user coupling with user change allowed on single connection3 ms14

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope5 ms0044
Scenario: A newly created account must have some metadata3 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic19 ms0088
Scenario: Access info service sanity checks3 ms0044
Scenario: Access service comparison sanity checks5 ms0033
Scenario: Account based ClientInfo data check40 ms002424
Scenario: Account exactly on its expiration date7 ms001414
Scenario: Account expiration date test - Parent and child expiration set, then parent expiration date changed to before child expiration date4 ms0066
Scenario: Account expiration date test - Parent expiration set, child expiration after father expiration5 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 null6 ms0066
Scenario: Account name must not be mutable6 ms0066
Scenario: Account past its expiration date7 ms001414
Scenario: Account wide metrics check28 ms002828
Scenario: Account with future expiration date2 ms001313
Scenario: Account with no expiration date14 ms001313
Scenario: Add Access Info domain permissions to new user10 ms002626
Scenario: Add Credential domain permissions to new user13 ms001818
Scenario: Add Datastore domain permissions to new user92 ms001919
Scenario: Add Device Connection domain permissions to kapua-sys user18 ms001111
Scenario: Add Device Connection domain permissions to new user32 ms002323
Scenario: Add Device Event domain permissions to new user19 ms001616
Scenario: Add Device domain permissions to new user16 ms001717
Scenario: Add Domain domain permissions to kapua-sys user19 ms001717
Scenario: Add Domain domain permissions to new user31 ms003232
Scenario: Add Group domain permissions to new user15 ms001717
Scenario: Add Job domain permissions to new user19 ms001919
Scenario: Add Role domain permissions to new user13 ms001818
Scenario: Add Tag domain permissions to new user15 ms001515
Scenario: Add User domain permissions to new user15 ms002020
Scenario: Add account permissions to the role15 ms001919
Scenario: Add datastore permissions to the role19 ms002727
Scenario: Add deleted role again21 ms001010
Scenario: Add device event permissions to the role22 ms003232
Scenario: Add device permissions to the role20 ms001919
Scenario: Add domain, user and access_info permissions to the role16 ms002323
Scenario: Add endpoint permissions to the role23 ms002626
Scenario: Add group permissions to the role33 ms001919
Scenario: Add job permissions to the role15 ms001919
Scenario: Add role permissions to the role33 ms001919
Scenario: Add same permission twice to the same role18 ms001414
Scenario: Add same role to user twice20 ms001313
Scenario: Add scheduler permissions to the role10 ms003131
Scenario: Add tag permissions to the role21 ms001919
Scenario: Add user permissions to the role34 ms001919
Scenario: Adding Multiple Permissions To User17 ms002020
Scenario: Adding One Permission To User19 ms001111
Scenario: Adding Permissions To Child User18 ms001818
Scenario: Adding Permissions To Parallel User26 ms001818
Scenario: Adding Previously Deleted Permission24 ms002828
Scenario: Adding existing roles to user22 ms001515
Scenario: B1 Broker publish to CTRL_ACC_REPLY7 ms2259
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed9 ms2259
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed7 ms2248
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI6 ms0099
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed9 ms2259
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed10 ms2248
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY7 ms2259
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY15 ms0099
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account9 ms2259
Scenario: B5 Broker publish to CTRL_ACC is not allowed17 ms0099
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed15 ms0099
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed10 ms2248
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI17 ms0099
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed12 ms2259
Scenario: Birth and applications event handling6 ms001212
Scenario: Birth and death message handling19 ms001212
Scenario: Birth and missing event handling9 ms001212
Scenario: Birth message handling from a new device13 ms001313
Scenario: Birth message handling from an existing device18 ms001212
Scenario: Both the parent and child accounts do not expire12 ms001111
Scenario: Both the parent and child accounts have the same expiration date7 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 filters26 ms005050
Scenario: ChannelInfo client ID and topic data based on the client id20 ms002828
Scenario: ChannelInfo client ID based on the account id21 ms002626
Scenario: ChannelInfo last published date23 ms003030
Scenario: ChannelInfo topic data based on the account id21 ms002626
Scenario: Check account properties6 ms0044
Scenario: Check the Device Connection Domain data seetting5 ms0022
Scenario: Check the database cache coherency24 ms003030
Scenario: Check the mapping for message semantic topics26 ms003030
Scenario: Check the message store22 ms002020
Scenario: Check the sanity of the Device Connection Domain data initialization5 ms0022
Scenario: Child account expires after parent11 ms0099
Scenario: Child account expires before parent19 ms001111
Scenario: Child account has null expiration date5 ms0099
Scenario: Client Id based ClientInfo data check23 ms002828
Scenario: Compare domain entries5 ms0033
Scenario: Connect to the system and publish some data7 ms215522
Scenario: Connection Service factory sanity checks3 ms0022
Scenario: Count access info entities in a specific scope18 ms002424
Scenario: Count access role entities by scope5 ms003939
Scenario: Count connections in empty scope7 ms0044
Scenario: Count connections in scope9 ms0055
Scenario: Count domains in a blank database5 ms0044
Scenario: Count domains in the database17 ms0077
Scenario: Count groups4 ms001414
Scenario: Count groups in a blank database3 ms0055
Scenario: Count job items4 ms0077
Scenario: Count job items in wrong - empty - scope15 ms0088
Scenario: Count role permissions in specific scopes6 ms001818
Scenario: Count roles in specific scopes4 ms001515
Scenario: Count step definition items11 ms0044
Scenario: Count step definitions in wrong (empty) scope6 ms0011
Scenario: Count steps in the database9 ms001515
Scenario: Count user5 ms0066
Scenario: Create and count several execution items for a job12 ms001212
Scenario: Create index with specific prefix10 ms001212
Scenario: Create multiple users4 ms0055
Scenario: Create regular access permissions10 ms002020
Scenario: Create some regular role permissions10 ms0099
Scenario: Create user that already exist4 ms0077
Scenario: Create user that has more than DB allowed length9 ms0055
Scenario: Create user with short name11 ms0055
Scenario: Create user with special characters in his name9 ms0055
Scenario: Create with permissions12 ms001414
Scenario: Create with permissions and a role5 ms001717
Scenario: Create with permissions and a role in the wrong scope7 ms001515
Scenario: Creating index with regular user28 ms002525
Scenario: Creating new device and tagging it with specific Tag5 ms001414
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag7 ms001616
Scenario: Creating tag30 ms0044
Scenario: Creating two indexes with daily index9 ms001717
Scenario: Creating two indexes with hourly index10 ms001717
Scenario: Creating two indexes with weekly index17 ms001717
Scenario: Creating user28 ms0055
Scenario: Creation of access role with neither acess info and role entities5 ms001212
Scenario: Creation of access role without an acess info entity7 ms001212
Scenario: D1 Device publish to CTRL_ACC_REPLY7 ms2259
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI13 ms0099
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed7 ms2259
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed12 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY7 ms2259
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY11 ms0099
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account5 ms2259
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC7 ms0099
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI13 ms0099
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed17 ms2259
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed6 ms2259
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed7 ms2248
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed15 ms2259
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI9 ms0099
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed7 ms2259
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms2248
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY9 ms2259
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY7 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account13 ms2259
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed11 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_CLI10 ms0099
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC12 ms0099
Scenario: DV1 Data view publish to CTRL_ACC_REPLY10 ms2259
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed6 ms2259
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed5 ms001010
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed6 ms0099
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed15 ms0099
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed11 ms2259
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed9 ms2248
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY6 ms2259
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY12 ms0099
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account9 ms2259
Scenario: DV5 Data view publish to CTRL_ACC is not allowed10 ms0099
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed11 ms0099
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed5 ms2248
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI6 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 roles10 ms001717
Scenario: Delete a connection from the database3 ms0088
Scenario: Delete a group from the database7 ms001010
Scenario: Delete a group from the database - Unknown group ID8 ms0066
Scenario: Delete a job6 ms001111
Scenario: Delete a job execution item7 ms0099
Scenario: Delete a job execution item twice3 ms001010
Scenario: Delete a job twice17 ms001010
Scenario: Delete a non existing connection12 ms0077
Scenario: Delete a non existing permission entity5 ms001616
Scenario: Delete a non existing role entry11 ms001111
Scenario: Delete a non-existing step6 ms001313
Scenario: Delete a nonexistent domain7 ms0055
Scenario: Delete a step definition6 ms0088
Scenario: Delete a step definition twice6 ms0077
Scenario: Delete access role from user20 ms001212
Scenario: Delete an access info entity twice4 ms001111
Scenario: Delete an access info entity using the wrong scope ID6 ms001111
Scenario: Delete an existing access info entity21 ms001212
Scenario: Delete an existing access permission entity4 ms001515
Scenario: Delete an existing access role entry11 ms002222
Scenario: Delete an existing account3 ms0055
Scenario: Delete an existing role8 ms001010
Scenario: Delete an existing role twice6 ms001616
Scenario: Delete an existing step3 ms001212
Scenario: Delete items based on query results20 ms008484
Scenario: Delete items by date ranges0.28 sec00132132
Scenario: Delete items by the datastore ID19 ms006666
Scenario: Delete middle child expiration4 ms001515
Scenario: Delete nonexisting account4 ms0044
Scenario: Delete nonexisting role permission6 ms001313
Scenario: Delete parent expiration9 ms001414
Scenario: Delete permissions from role17 ms001818
Scenario: Delete role permissions7 ms001010
Scenario: Delete the Kapua system account4 ms0055
Scenario: Delete the last created domain entry7 ms0088
Scenario: Delete user9 ms0066
Scenario: Delete user that doesn't exist5 ms0055
Scenario: Deleting a Permission16 ms002121
Scenario: Deleting tag12 ms0044
Scenario: Deleting user in account that is higher in hierarchy20 ms002323
Scenario: Deleting user in account that is lower in hierarchy28 ms002424
Scenario: Device connection update9 ms0077
Scenario: Domain entry query5 ms0055
Scenario: Domain with null actions7 ms0055
Scenario: Domain with null name8 ms0055
Scenario: Domains with duplicate names5 ms0088
Scenario: Duplicate group name in root scope6 ms001010
Scenario: Duplicate role names7 ms0077
Scenario: Empty query results are supported5 ms0088
Scenario: Every account must have the default configuration items3 ms0033
Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode12 ms240413419
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode6 ms238213397
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices7 ms229310305
Scenario: Find a connection by its IDs9 ms0066
Scenario: Find a connection by its client ID4 ms0066
Scenario: Find a group entry in the database12 ms0099
Scenario: Find account by Id5 ms0044
Scenario: Find account by Ids7 ms0044
Scenario: Find account by name6 ms0044
Scenario: Find account by random Id5 ms0033
Scenario: Find all child accounts8 ms0033
Scenario: Find an access info entity8 ms001111
Scenario: Find an access info entity by user ID3 ms001010
Scenario: Find an existing access role entity7 ms001313
Scenario: Find by name nonexisting account3 ms0033
Scenario: Find correct number of messages by corresponding metric8 ms4381658
Scenario: Find last created permission30 ms001212
Scenario: Find multiple users3 ms0055
Scenario: Find role by ID8 ms0077
Scenario: Find self account by id6 ms001111
Scenario: Find self account by id and scope id10 ms001111
Scenario: Find self account by name12 ms001111
Scenario: Find the last created domain entry7 ms0055
Scenario: Find user by id5 ms0055
Scenario: Find user by name7 ms0055
Scenario: Find user by name that doesn't exist7 ms0033
Scenario: Find user with id and scope id that doesn't exist6 ms0033
Scenario: Finding all messages by selecting all metrics5 ms4201640
Scenario: Finding correct number of messages by corresponding two metrics7 ms4321652
Scenario: Finding messages with incorrect metric parameters10 ms4521672
Scenario: Generic connection query4 ms0088
Scenario: Get metadata6 ms0033
Scenario: Group with a null name4 ms0077
Scenario: Handle account creation23 ms0033
Scenario: Handle duplicate account names8 ms0055
Scenario: Handle null account name8 ms0044
Scenario: Handling of 2 birth messages9 ms001212
Scenario: Handling of a disconnect message from a non existing device17 ms001010
Scenario: I try to find a non-existing connection6 ms0066
Scenario: If user credential expiration date is before today, user can not login6 ms001414
Scenario: If user credential expiration date is today, user can not login it is day inclusive14 ms001414
Scenario: If user credential expiration date is tomorrow, user can login9 ms001313
Scenario: If user credential is in state disabled, user can not login19 ms001414
Scenario: If user credential is in state enabled, user can login4 ms001313
Scenario: If user expiration date is before today, user can not login18 ms001313
Scenario: If user expiration date is today, user can not login because expiration date was reached4 ms001313
Scenario: If user expiration date is tomorrow, user can login8 ms001212
Scenario: Installing a package7 ms27413
Scenario: It is possible to change the configuration items4 ms0044
Scenario: It must be possible to query for specific entries in the role database12 ms0088
Scenario: Job execution factory sanity checks3 ms0022
Scenario: Job factory sanity checks4 ms0033
Scenario: Job with a duplicate name2 ms0099
Scenario: Job with a null name4 ms0088
Scenario: Job with a null scope ID13 ms0099
Scenario: Job with an empty name5 ms0099
Scenario: MetricsInfo client ID and topic data based on the client id24 ms003434
Scenario: MetricsInfo last published date21 ms004848
Scenario: Modify a role that was deleted13 ms0099
Scenario: Modify an existing account5 ms0044
Scenario: Modify last child expiration so that it still expires before parent4 ms001414
Scenario: Modify middle child expiration so that it still expires before parent8 ms001414
Scenario: Modify middle child expiration to outlive parent6 ms001515
Scenario: Modify nonexisting account5 ms0066
Scenario: Modify parent expiration so that it still expires after child7 ms001414
Scenario: Modify parent expiration to before child expiration4 ms001515
Scenario: Nameless role entry14 ms0077
Scenario: Negative scenario when client connects twice with same client id11 ms001111
Scenario: New connection with reserved ID5 ms2191334
Scenario: Permission factory sanity checks6 ms0033
Scenario: Positive scenario without stealing link11 ms001212
Scenario: Query based on message ordering21 ms002020
Scenario: Query based on metrics ordering19 ms002020
Scenario: Query before schema search23 ms008282
Scenario: Query for a specific group by name5 ms001616
Scenario: Query for all the access info entities of a specific user5 ms001818
Scenario: Query for all the access info entities of an invalid user5 ms001010
Scenario: Query for executions of a specific job3 ms001919
Scenario: Query for jobs with specified name3 ms0099
Scenario: Query for step definitions6 ms0077
Scenario: Query user7 ms0066
Scenario: Regular connection21 ms0077
Scenario: Regular creation of Access Role entity16 ms001414
Scenario: Regular domain6 ms0055
Scenario: Regular group in random scope3 ms0077
Scenario: Regular group in root scope13 ms0077
Scenario: Regular job creation7 ms001010
Scenario: Regular job execution creation9 ms0088
Scenario: Regular role creation20 ms0099
Scenario: Regular step creation5 ms001212
Scenario: Regular step definition creation31 ms0077
Scenario: Regular step definition with a property list18 ms0044
Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The First Time9 ms232539
Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The Second Time6 ms239647
Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The First Time17 ms231639
Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The Second Time6 ms244652
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 Valid "Bundle Start" And Step Index=0 For The First Time8 ms232539
Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The Second Time7 ms243651
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 Time13 ms244652
Scenario: Restarting Job With Valid "Command Execution" And Step Index=0 For The First Time4 ms225734
Scenario: Restarting Job With Valid "Command Execution" And Step Index=0 For The Second Time3 ms233742
Scenario: Restarting a job with Asset Write and Bundle Start steps7 ms224430
Scenario: Restarting a job with Command Execution and Bundle Start steps7 ms224430
Scenario: Restarting a job with Configuration Put and Bundle Start steps7 ms224430
Scenario: Restarting a job with Package Uninstall and Bundle Start steps38 ms226432
Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices6 ms2+227+274+433+33
Scenario: Restarting job with Asset Write step5 ms2131025
Scenario: Restarting job with Asset Write step and multiple devices5 ms2+222+224+428+28
Scenario: Restarting job with Bundle Start step9 ms221427
Scenario: Restarting job with Bundle Start step and multiple devices6 ms2+224+244+430+30
Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices5 ms2+229+294+435+35
Scenario: Restarting job with Bundle Stop and Bundle Start steps6 ms226432
Scenario: Restarting job with Bundle Stop step7 ms221427
Scenario: Restarting job with Bundle Stop step and multiple devices14 ms2+224+244+430+30
Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices6 ms2+227+274+433+33
Scenario: Restarting job with Command Execution step4 ms2131025
Scenario: Restarting job with Command Execution step and multiple devices7 ms2+222+224+428+28
Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices10 ms2+227+274+433+33
Scenario: Restarting job with Configuration Put step3 ms2131025
Scenario: Restarting job with Configuration Put step and multiple devices6 ms2+222+224+428+28
Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices15 ms4+255+298+467+35
Scenario: Restarting job with Package Download/Install step and multiple devices9 ms2+223+234+429+29
Scenario: Restarting job with Package Install step7 ms221427
Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device7 ms2+230+304+436+36
Scenario: Restarting job with Package Uninstall step7 ms221427
Scenario: Restarting job with Package Uninstall step and multiple device9 ms2+224+244+430+30
Scenario: Restarting job with two Bundle Start steps9 ms226432
Scenario: Restarting job with two Bundle Start steps and multiple devices7 ms2+229+294+435+35
Scenario: Role creator sanity checks5 ms0022
Scenario: Role entry with no actions9 ms0066
Scenario: Role object equality check5 ms0022
Scenario: Role service related objects sanity checks7 ms0044
Scenario: Search for a non existent client ID7 ms0066
Scenario: Search for an access info entity by an incorrect user ID5 ms001111
Scenario: Search the role database for a random ID7 ms0077
Scenario: Send BIRTH message and then DC message4 ms27615
Scenario: Send BIRTH message and then DC message while broker ip is NOT set16 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 file4 ms2248
Scenario: Set environment variables0.16 sec005555
Scenario: Setting configuration without mandatory items must raise an error4 ms0055
Scenario: Simple create7 ms001111
Scenario: Simple positive scenario for creating daily index13 ms001414
Scenario: Simple positive scenario for creating default - weekly index11 ms001212
Scenario: Simple positive scenario for creating hourly index17 ms001414
Scenario: Start broker for all scenarios87 ms400040
Scenario: Start datastore for all scenarios1.3 sec003232
Scenario: Start event broker for all scenarios0.41 sec004646
Scenario: Starting a job with Asset Write and Bundle Start steps5 ms233540
Scenario: Starting a job with Asset Write step3 ms2131429
Scenario: Starting a job with Bundle Start step7 ms231538
Scenario: Starting a job with Bundle Stop and Bundle Start steps6 ms234642
Scenario: Starting a job with Bundle Stop step6 ms230638
Scenario: Starting a job with Command Execution and Bundle Start steps7 ms234541
Scenario: Starting a job with Command Execution step4 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 step5 ms231538
Scenario: Starting a job with Package Install and Bundle Start steps10 ms238545
Scenario: Starting a job with Package Uninstall Command step7 ms233540
Scenario: Starting a job with Package Uninstall and Bundle Start steps7 ms235542
Scenario: Starting a job with invalid Bundle Start step5 ms232539
Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps5 ms236644
Scenario: Starting a job with invalid Bundle Stop step6 ms231639
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 steps7 ms237544
Scenario: Starting a job with two valid Bundle Start steps7 ms237544
Scenario: Starting a job with valid Bundle Start step5 ms232539
Scenario: Starting a job with valid Bundle Stop and Bundle Start steps7 ms236644
Scenario: Starting a job with valid Bundle Stop step5 ms231639
Scenario: Starting a job with valid Command Execution step4 ms226735
Scenario: Starting and stopping the simulator should create a device entry and properly set its status7 ms214420
Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices4 ms2181535
Scenario: Starting job with Asset Write step and multiple devices3 ms2141531
Scenario: Starting job with Bundle Start step and multiple devices3 ms2141531
Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices3 ms2181535
Scenario: Starting job with Bundle Stop step and multiple devices4 ms2141531
Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices3 ms2181535
Scenario: Starting job with Command Execution step and multiple devices5 ms2141531
Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices3 ms2181535
Scenario: Starting job with Configuration Put step and multiple devices2 ms2141531
Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices6 ms235542
Scenario: Starting job with Package Download/Install step and multiple devices5 ms231538
Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device5 ms2181535
Scenario: Starting job with Package Uninstall step and multiple device5 ms2141531
Scenario: Starting job with two Bundle Start steps and multiple devices4 ms2181535
Scenario: Stealing link scenario7 ms2141228
Scenario: Step definition factory sanity checks11 ms0022
Scenario: Step definition with a duplicate name10 ms0066
Scenario: Step definition with a null name26 ms0066
Scenario: Step definition with a null scope ID16 ms0066
Scenario: Step definition with an empty name9 ms0055
Scenario: Step factory sanity checks4 ms0022
Scenario: Step with a null scope ID14 ms001212
Scenario: Stop broker after all scenarios0.34 sec004242
Scenario: Stop datastore after all scenarios0.19 sec003232
Scenario: Stop event broker for all scenarios0.39 sec004646
Scenario: Test LOOSE user coupling on single connection6 ms2131328
Scenario: Test LOOSE user coupling with 3 connections7 ms2231338
Scenario: Test STRICT user coupling on single connection3 ms2101325
Scenario: Test STRICT user coupling with 3 connections and a reserved user20 ms2481363
Scenario: Test STRICT user coupling with user change allowed on single connection5 ms2211336
Scenario: Test account query7 ms0044
Scenario: Test the message store with server timestamp indexing24 ms002626
Scenario: Test the message store with timestamp indexing44 ms002626
Scenario: The Client ID is case sensitive3 ms0088
Scenario: To be defined9 ms001313
Scenario: Try to change an existing connection ID7 ms0077
Scenario: Try to create an access into entity with an invalid role id5 ms001212
Scenario: Try to modify the connection client ID9 ms0077
Scenario: Unknown configuiration items are silently ignored3 ms0044
Scenario: Update a group entry in the database4 ms0099
Scenario: Update a group entry with a false ID5 ms001010
Scenario: Update a job XML definition11 ms001010
Scenario: Update a job description3 ms001010
Scenario: Update a job name4 ms001010
Scenario: Update a nonexistent job4 ms001010
Scenario: Update a nonexistent step definition7 ms0077
Scenario: Update a step definition name7 ms0077
Scenario: Update a step definition processor name5 ms0088
Scenario: Update a step definition target type5 ms0088
Scenario: Update existing role name11 ms0088
Scenario: Update job id of an existing execution item7 ms0099
Scenario: Update the end time of an existing execution item16 ms001010
Scenario: Update user7 ms0077
Scenario: Update user that doesn't exist4 ms0055
Scenario: User locking itself out by using out login attempts5 ms001616
Scenario: User locking itself out with failed attempts and not waiting to unlock20 ms001717
Scenario: User locking itself out with failed attempts and waiting to unlock4 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