Test Result

218 failures (+42) , 2,634 skipped (+554)
8,017 tests (+743)
Took 2 hr 25 min.

All Failed Tests

Test NameDurationAge
 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 ms1
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric2 ms1
 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 ms1
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics2 ms1
 Scenario: Finding all messages by selecting all metrics.Then I prepare a number of messages with the following details and remember the list as "TestMessages"2 ms1
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics3 ms1
 Scenario: Finding messages with incorrect metric parameters.Then I prepare a number of messages with the following details and remember the list as "TestMessages"0 ms1
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters1 ms1
 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 ms1
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric2 ms1
 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 ms1
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics2 ms1
 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 ms1
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics1 ms1
 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 ms1
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters1 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 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 Time3 ms1
 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 Time3 ms1
 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 Time1 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 Time6 ms1
 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 ms1
 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 ms1
 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 Time5 ms1
 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 Time5 ms1
 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 ms1
 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 Time4 ms1
 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 Time6 ms1
 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 ms2
 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"2 ms2
 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"2 ms2
 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 ms2
 Scenario: Starting a job with valid Command Execution step.When I search for events from device "rpione3" in account "kapua-sys"3 ms2
 Scenario: Starting a job with valid Command Execution step.Scenario: Starting a job with valid Command Execution step4 ms2
 Scenario: Starting a job with invalid Command Execution step.When I search for events from device "rpione3" in account "kapua-sys"2 ms2
 Scenario: Starting a job with invalid Command Execution step.Scenario: Starting a job with invalid Command Execution step3 ms2
 Scenario: Starting a job with valid Bundle Start step.Scenario: Starting a job with valid Bundle Start step5 ms2
 Scenario: Starting a job with invalid Bundle Start step.Scenario: Starting a job with invalid Bundle Start step5 ms2
 Scenario: Starting a job with valid Bundle Stop step.Scenario: Starting a job with valid Bundle Stop step4 ms2
 Scenario: Starting a job with invalid Bundle Stop step.Scenario: Starting a job with invalid Bundle Stop step4 ms2
 Scenario: Starting a job with two valid Bundle Start steps.Scenario: Starting a job with two valid Bundle Start steps5 ms2
 Scenario: Starting a job with two invalid Bundle Start steps.Scenario: Starting a job with two invalid Bundle Start steps5 ms2
 Scenario: Starting a job with valid Bundle Stop and Bundle Start steps.Scenario: Starting a job with valid Bundle Stop and Bundle Start steps6 ms2
 Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps.Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps5 ms2
 Scenario: Start broker for all scenarios.Given Start Broker1 ms3
 Scenario: Start broker for all scenarios.Given Start Broker2 ms3
 Scenario: Start broker for all scenarios.Given Start Broker1 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms3
 Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The First Time.Then Device status is "CONNECTED"4 ms3
 Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The First Time.Then Device status is "CONNECTED"4 ms3
 Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The Second Time.And Bundles are requested3 ms3
 Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The Second Time.And Bundles are requested3 ms3
 Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The First Time.And Bundles are requested4 ms3
 Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The First Time.And Bundles are requested4 ms3
 Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The Second Time.And Bundles are requested2 ms3
 Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The Second Time.And Bundles are requested5 ms3
 Scenario: Starting a job with Command Execution step.And A new job target item1 ms3
 Scenario: Starting a job with Command Execution step.Scenario: Starting a job with Command Execution step3 ms3
 Scenario: Starting a job with Asset Write step.And A new job target item1 ms3
 Scenario: Starting a job with Asset Write step.Scenario: Starting a job with Asset Write step2 ms3
 Scenario: Starting a job with Bundle Start step.Then Device status is "CONNECTED"3 ms3
 Scenario: Starting a job with Bundle Start step.Scenario: Starting a job with Bundle Start step4 ms3
 Scenario: Starting a job with Bundle Stop step.And Bundles are requested2 ms3
 Scenario: Starting a job with Bundle Stop step.Scenario: Starting a job with Bundle Stop step4 ms3
 Scenario: Starting a job with Configuration Put step.And A new job target item1 ms3
 Scenario: Starting a job with Configuration Put step.Scenario: Starting a job with Configuration Put step1 ms3
 Scenario: Starting a job with Package Install Command step.Then Device status is "CONNECTED"2 ms3
 Scenario: Starting a job with Package Install Command step.Scenario: Starting a job with Package Install Command step4 ms3
 Scenario: Starting a job with Package Uninstall Command step.Then Device status is "CONNECTED"2 ms3
 Scenario: Starting a job with Package Uninstall Command step.Scenario: Starting a job with Package Uninstall Command step3 ms3
 Scenario: Starting a job with Command Execution and Bundle Start steps.Then Device status is "CONNECTED"3 ms3
 Scenario: Starting a job with Command Execution and Bundle Start steps.Scenario: Starting a job with Command Execution and Bundle Start steps4 ms3
 Scenario: Starting a job with Asset Write and Bundle Start steps.Then Device status is "CONNECTED"3 ms3
 Scenario: Starting a job with Asset Write and Bundle Start steps.Scenario: Starting a job with Asset Write and Bundle Start steps4 ms3
 Scenario: Starting a job with two Bundle Start steps.Then Device status is "CONNECTED"4 ms3
 Scenario: Starting a job with two Bundle Start steps.Scenario: Starting a job with two Bundle Start steps6 ms3
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.And Bundles are requested2 ms3
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.Scenario: Starting a job with Bundle Stop and Bundle Start steps4 ms3
 Scenario: Starting a job with Configuration Put and Bundle Start steps.And Bundles are requested3 ms3
 Scenario: Starting a job with Configuration Put and Bundle Start steps.Scenario: Starting a job with Configuration Put and Bundle Start steps4 ms3
 Scenario: Starting a job with Package Install and Bundle Start steps.Then Device status is "CONNECTED"2 ms3
 Scenario: Starting a job with Package Install and Bundle Start steps.Scenario: Starting a job with Package Install and Bundle Start steps4 ms3
 Scenario: Starting a job with Package Uninstall and Bundle Start steps.Then Device status is "CONNECTED"2 ms3
 Scenario: Starting a job with Package Uninstall and Bundle Start steps.Scenario: Starting a job with Package Uninstall and Bundle Start steps4 ms3
 Scenario: Starting a job with valid Bundle Start step.Then Device status is "CONNECTED"3 ms3
 Scenario: Starting a job with invalid Bundle Start step.Then Device status is "CONNECTED"4 ms3
 Scenario: Starting a job with valid Bundle Stop step.And Bundles are requested3 ms3
 Scenario: Starting a job with invalid Bundle Stop step.And Bundles are requested3 ms3
 Scenario: Starting a job with two valid Bundle Start steps.Then Device status is "CONNECTED"4 ms3
 Scenario: Starting a job with two invalid Bundle Start steps.Then Device status is "CONNECTED"4 ms3
 Scenario: Starting a job with valid Bundle Stop and Bundle Start steps.And Bundles are requested4 ms3
 Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps.And Bundles are requested3 ms3
 Scenario: Start broker for all scenarios.Given Start Broker2 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms3
 Scenario: Start broker for all scenarios.Given Start Broker1 ms8
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms8
 Scenario: Test LOOSE user coupling on single connection.And The connection status is "CONNECTED"3 ms8
 Scenario: Test LOOSE user coupling on single connection.Scenario: Test LOOSE user coupling on single connection4 ms8
 Scenario: New connection with reserved ID.And The connection status is "CONNECTED"3 ms8
 Scenario: New connection with reserved ID.Scenario: New connection with reserved ID5 ms8
 Scenario: Test STRICT user coupling on single connection.And The connection status is "CONNECTED"3 ms8
 Scenario: Test STRICT user coupling on single connection.Scenario: Test STRICT user coupling on single connection5 ms8
 Scenario: Test STRICT user coupling with user change allowed on single connection.And The connection status is "CONNECTED"3 ms8
 Scenario: Test STRICT user coupling with user change allowed on single connection.Scenario: Test STRICT user coupling with user change allowed on single connection5 ms8
 Scenario: Test LOOSE user coupling with 3 connections.And The connection status is "CONNECTED"2 ms8
 Scenario: Test LOOSE user coupling with 3 connections.Scenario: Test LOOSE user coupling with 3 connections3 ms8
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.And The connection status is "CONNECTED"2 ms8
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.Scenario: Test STRICT user coupling with 3 connections and a reserved user3 ms8
 Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode.And The connection status is "CONNECTED"2 ms8
 Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode.Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode4 ms8
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode.And The connection status is "CONNECTED"2 ms8
 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 ms8
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices.Then I find 1 connection2 ms8
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices.Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices3 ms8
 Scenario: Start broker for all scenarios.Given Start Broker2 ms8
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms8
 Scenario: Start broker for all scenarios.Given Start Broker2 ms8
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms8
 Scenario: Start broker for all scenarios.Given Start Broker2 ms8
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms8
 Scenario: Start broker for all scenarios.Given Start Broker2 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms10
 Scenario: Start broker for all scenarios.Given Start Broker3 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms10
 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"12 ms10
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed12 ms10
 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"6 ms10
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY8 ms10
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown3 ms10
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account4 ms10
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Then An exception was thrown6 ms10
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed7 ms10
 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 ms10
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed6 ms10
 Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown2 ms10
 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 ms10
 Scenario: Start broker for all scenarios.Given Start Broker13 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios13 ms10
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"5 ms10
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY6 ms10
 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"5 ms10
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY7 ms10
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown5 ms10
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account5 ms10
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Then An exception was thrown3 ms10
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed5 ms10
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"4 ms10
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed6 ms10
 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 ms10
 Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed4 ms10
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown2 ms10
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed4 ms10
 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"3 ms10
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms10
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown2 ms10
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed3 ms10
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"6 ms10
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY8 ms10
 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"6 ms10
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY7 ms10
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown3 ms10
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account4 ms10
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"7 ms10
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed7 ms10
 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"6 ms10
 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 allowed8 ms10
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown3 ms10
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed4 ms10
 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 ms10
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms10
 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 ms10
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY4 ms10
 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"8 ms10
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY9 ms10
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown13 ms10
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account15 ms10
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Then An exception was thrown4 ms10
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed5 ms10
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"7 ms10
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed8 ms10
 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 ms10
 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 ms10
 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 ms10
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms10
 Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown3 ms10
 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 ms10
 Scenario: Start broker for all scenarios.Given Start Broker1 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms10
 Scenario: Send BIRTH message and then DC message.And Bundles are requested2 ms10
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message3 ms10
 Scenario: Start broker for all scenarios.Given Start Broker1 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms10
 Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Then Device is connected with "localhost" server ip1 ms10
 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 ms10
 Scenario: Start broker for all scenarios.Given Start Broker1 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms10
 Scenario: Send BIRTH message and then DC message while broker ip is set by System.Then Device is connected with "localhost" server ip2 ms10
 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 ms10
 Scenario: Start broker for all scenarios.Given Start Broker1 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms10
 Scenario: Start broker for all scenarios.Given Start Broker2 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms10
 Scenario: Stealing link scenario.And Client named "client-2" is not connected4 ms10
 Scenario: Stealing link scenario.Scenario: Stealing link scenario6 ms10
 Scenario: Start broker for all scenarios.Given Start Broker2 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms10
 Scenario: Connect to the system and publish some data.Then Device sim-1 for account kapua-sys is registered after 5 seconds5 ms10
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data7 ms10
 Scenario: Start broker for all scenarios.Given Start Broker2 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms10
 Scenario: Start broker for all scenarios.Given Start Broker1 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms10
 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 ms10
 Scenario: Starting and stopping the simulator should create a device entry and properly set its status.Scenario: Starting and stopping the simulator should create a device entry and properly set its status5 ms10
 Scenario: Installing a package.Then Device sim-1 for account kapua-sys is registered after 5 seconds3 ms10
 Scenario: Installing a package.Scenario: Installing a package4 ms10

All Tests

PackageDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
(root)9.5 sec218+422621+5544866+1477705+743
org.eclipse.kapua59 ms0033
org.eclipse.kapua.broker.core.plugin2.8 sec001515
org.eclipse.kapua.client.gateway50 ms004343
org.eclipse.kapua.client.gateway.kura0.2 sec001414
org.eclipse.kapua.client.gateway.spi.util2.7 sec001515
org.eclipse.kapua.client.gateway.util2 ms0033
org.eclipse.kapua.commons.about0.47 sec0011
org.eclipse.kapua.commons.configuration44 ms0011
org.eclipse.kapua.commons.configuration.metatype9 ms001919
org.eclipse.kapua.commons.liquibase0.53 sec0044
org.eclipse.kapua.commons.metric4 ms0022
org.eclipse.kapua.commons.model0.13 sec0088
org.eclipse.kapua.commons.model.id6 ms0011
org.eclipse.kapua.commons.security3 sec0033
org.eclipse.kapua.commons.setting0 ms0044
org.eclipse.kapua.commons.util24 ms003838
org.eclipse.kapua.commons.util.xml0.3 sec0099
org.eclipse.kapua.integration.misc0 ms0101
org.eclipse.kapua.integration.service.datastoreJunit0 ms0505
org.eclipse.kapua.kura.simulator.main.simulation5.3 sec001313
org.eclipse.kapua.locator.internal0.14 sec021012
org.eclipse.kapua.message.internal0.31 sec022628
org.eclipse.kapua.message.internal.device.data0 ms0033
org.eclipse.kapua.message.internal.device.lifecycle1 ms002121
org.eclipse.kapua.message.internal.xml70 ms001111
org.eclipse.kapua.service.datastore.test.junit0.21 sec0044
org.eclipse.kapua.service.datastore.test.junit.client0.33 sec0077
org.eclipse.kapua.service.datastore.test.junit.clientTransport65 ms031922
org.eclipse.kapua.service.device.management.commons.message.notification15 ms0022