Test Result

122 failures (±0) , 1,347 skipped (±0)
5,849 tests (±0)
Took 2 hr 4 min.

All Failed Tests

Test NameDurationAge
 Scenario: Start broker for all scenarios.Given Start Broker2 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms4
 Scenario: Test LOOSE user coupling on single connection.And The connection status is "CONNECTED"2 ms4
 Scenario: Test LOOSE user coupling on single connection.Scenario: Test LOOSE user coupling on single connection4 ms4
 Scenario: New connection with reserved ID.And The connection status is "CONNECTED"3 ms4
 Scenario: New connection with reserved ID.Scenario: New connection with reserved ID5 ms4
 Scenario: Test STRICT user coupling on single connection.And The connection status is "CONNECTED"3 ms4
 Scenario: Test STRICT user coupling on single connection.Scenario: Test STRICT user coupling on single connection5 ms4
 Scenario: Test STRICT user coupling with user change allowed on single connection.And The connection status is "CONNECTED"2 ms4
 Scenario: Test STRICT user coupling with user change allowed on single connection.Scenario: Test STRICT user coupling with user change allowed on single connection46 ms4
 Scenario: Test LOOSE user coupling with 3 connections.And The connection status is "CONNECTED"2 ms4
 Scenario: Test LOOSE user coupling with 3 connections.Scenario: Test LOOSE user coupling with 3 connections4 ms4
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.And The connection status is "CONNECTED"2 ms4
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.Scenario: Test STRICT user coupling with 3 connections and a reserved user4 ms4
 Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode.And The connection status is "CONNECTED"3 ms4
 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 ms4
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode.And The connection status is "CONNECTED"2 ms4
 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 mode7 ms4
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices.Then I find 1 connection2 ms4
 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 ms4
 Scenario: Start broker for all scenarios.Given Start Broker2 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms4
 Scenario: Start broker for all scenarios.Given Start Broker1 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms4
 Scenario: Start broker for all scenarios.Given Start Broker2 ms4
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms4
 Scenario: Start broker for all scenarios.Given Start Broker2 ms6
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms6
 Scenario: Start broker for all scenarios.Given Start Broker1 ms6
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms6
 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"3 ms6
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed5 ms6
 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"1 ms6
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY1 ms6
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown4 ms6
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account6 ms6
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Then An exception was thrown4 ms6
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed5 ms6
 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"6 ms6
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed8 ms6
 Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown3 ms6
 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 allowed6 ms6
 Scenario: Start broker for all scenarios.Given Start Broker14 ms6
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios14 ms6
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"3 ms6
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY4 ms6
 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 ms6
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY4 ms6
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown2 ms6
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account3 ms6
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Then An exception was thrown2 ms6
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed4 ms6
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"10 ms6
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed11 ms6
 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"7 ms6
 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 allowed8 ms6
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown8 ms6
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed8 ms6
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"6 ms6
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed8 ms6
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown2 ms6
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms6
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"2 ms6
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY4 ms6
 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 ms6
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY5 ms6
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown2 ms6
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account4 ms6
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"2 ms6
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed4 ms6
 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 ms6
 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 allowed3 ms6
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown2 ms6
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed4 ms6
 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"6 ms6
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed8 ms6
 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 ms6
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY6 ms6
 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 ms6
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY4 ms6
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown2 ms6
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account3 ms6
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Then An exception was thrown2 ms6
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed3 ms6
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"8 ms6
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed8 ms6
 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"4 ms6
 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 allowed6 ms6
 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"2 ms6
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed4 ms6
 Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown5 ms6
 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 ms6
 Scenario: Start broker for all scenarios.Given Start Broker4 ms6
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms6
 Scenario: Send BIRTH message and then DC message.And Bundles are requested1 ms6
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message1 ms6
 Scenario: Start broker for all scenarios.Given Start Broker2 ms6
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms6
 Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Then Device is connected with "localhost" server ip3 ms6
 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 file4 ms6
 Scenario: Start broker for all scenarios.Given Start Broker2 ms6
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms6
 Scenario: Send BIRTH message and then DC message while broker ip is set by System.Then Device is connected with "localhost" server ip1 ms6
 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 ms6
 Scenario: Start broker for all scenarios.Given Start Broker2 ms6
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms6
 Scenario: Start broker for all scenarios.Given Start Broker1 ms6
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms6
 Scenario: Stealing link scenario.And Client named "client-2" is not connected3 ms6
 Scenario: Stealing link scenario.Scenario: Stealing link scenario5 ms6
 Scenario: Start broker for all scenarios.Given Start Broker1 ms6
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms6
 Scenario: Connect to the system and publish some data.Then Device sim-1 for account kapua-sys is registered after 5 seconds2 ms6
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data4 ms6
 Scenario: Start broker for all scenarios.Given Start Broker0 ms6
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms6
 Scenario: Start broker for all scenarios.Given Start Broker1 ms6
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms6
 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 ms6
 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 ms6
 Scenario: Installing a package.Then Device sim-1 for account kapua-sys is registered after 5 seconds3 ms6
 Scenario: Installing a package.Scenario: Installing a package4 ms6

All Tests

PackageDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
(root)6.4 sec122133440815537
org.eclipse.kapua84 ms0033
org.eclipse.kapua.broker.core.plugin3 sec001515
org.eclipse.kapua.client.gateway49 ms004343
org.eclipse.kapua.client.gateway.kura0.14 sec001414
org.eclipse.kapua.client.gateway.spi.util2.7 sec001515
org.eclipse.kapua.client.gateway.util0 ms0033
org.eclipse.kapua.commons.about0.3 sec0011
org.eclipse.kapua.commons.configuration62 ms0011
org.eclipse.kapua.commons.configuration.metatype15 ms001919
org.eclipse.kapua.commons.liquibase2.7 sec0044
org.eclipse.kapua.commons.metric3 ms0022
org.eclipse.kapua.commons.model4.3 sec0088
org.eclipse.kapua.commons.model.id3 ms0011
org.eclipse.kapua.commons.security3 sec0033
org.eclipse.kapua.commons.setting1 ms0044
org.eclipse.kapua.commons.util49 ms003838
org.eclipse.kapua.commons.util.xml0.39 sec0099
org.eclipse.kapua.integration.misc0 ms0101
org.eclipse.kapua.integration.service.datastoreJunit0 ms0505
org.eclipse.kapua.kura.simulator.main.simulation5.5 sec001313
org.eclipse.kapua.locator.internal0.13 sec021012
org.eclipse.kapua.message.internal0.25 sec022628
org.eclipse.kapua.message.internal.device.data0 ms0033
org.eclipse.kapua.message.internal.device.lifecycle51 ms002121
org.eclipse.kapua.message.internal.xml1.4 sec001111
org.eclipse.kapua.service.datastore.test.junit0.2 sec0044
org.eclipse.kapua.service.datastore.test.junit.client0.28 sec0077
org.eclipse.kapua.service.datastore.test.junit.clientTransport99 ms031922
org.eclipse.kapua.service.device.management.commons.message.notification7 ms0022