[Jenkins]Jenkins

Test Result

122 failures (+122) , 1,361 skipped (+1334)
5,180 tests (±0)
Took 3 hr 39 min.

All Failed Tests

Test NameDurationAge
 Scenario: Start broker for all scenarios.Given Start Broker1 ms23
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms23
 Scenario: Test LOOSE user coupling on single connection.And The connection status is "CONNECTED"1 ms23
 Scenario: Test LOOSE user coupling on single connection.Scenario: Test LOOSE user coupling on single connection2 ms23
 Scenario: New connection with reserved ID.And The connection status is "CONNECTED"3 ms23
 Scenario: New connection with reserved ID.Scenario: New connection with reserved ID3 ms23
 Scenario: Test STRICT user coupling on single connection.And The connection status is "CONNECTED"1 ms23
 Scenario: Test STRICT user coupling on single connection.Scenario: Test STRICT user coupling on single connection2 ms23
 Scenario: Test STRICT user coupling with user change allowed on single connection.And The connection status is "CONNECTED"1 ms23
 Scenario: Test STRICT user coupling with user change allowed on single connection.Scenario: Test STRICT user coupling with user change allowed on single connection3 ms23
 Scenario: Test LOOSE user coupling with 3 connections.And The connection status is "CONNECTED"0 ms23
 Scenario: Test LOOSE user coupling with 3 connections.Scenario: Test LOOSE user coupling with 3 connections0 ms23
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.And The connection status is "CONNECTED"1 ms23
 Scenario: Test STRICT user coupling with 3 connections and a reserved user.Scenario: Test STRICT user coupling with 3 connections and a reserved user2 ms23
 Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode.And The connection status is "CONNECTED"0 ms23
 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 mode0 ms23
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode.And The connection status is "CONNECTED"1 ms23
 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 mode1 ms23
 Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices.Then I find 1 connection2 ms23
 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 ms23
 Scenario: Start broker for all scenarios.Given Start Broker2 ms23
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms23
 Scenario: Start broker for all scenarios.Given Start Broker17 ms23
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios17 ms23
 Scenario: Start broker for all scenarios.Given Start Broker3 ms23
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms23
 Scenario: Start broker for all scenarios.Given Start Broker2 ms23
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms23
 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"2 ms23
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed6 ms23
 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"2 ms23
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY3 ms23
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown1 ms23
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account2 ms23
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Then An exception was thrown2 ms23
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed2 ms23
 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"2 ms23
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed2 ms23
 Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown1 ms23
 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 allowed2 ms23
 Scenario: Start broker for all scenarios.Given Start Broker2 ms23
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms23
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"3 ms23
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY5 ms23
 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 ms23
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY4 ms23
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown1 ms23
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account1 ms23
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Then An exception was thrown2 ms23
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed2 ms23
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"2 ms23
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed4 ms23
 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"2 ms23
 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 ms23
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown2 ms23
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed3 ms23
 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 ms23
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms23
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown1 ms23
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed2 ms23
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"2 ms23
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY4 ms23
 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 ms23
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY4 ms23
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown1 ms23
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account1 ms23
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"2 ms23
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed7 ms23
 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"1 ms23
 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 allowed2 ms23
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown1 ms23
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed2 ms23
 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"1 ms23
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed2 ms23
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"2 ms23
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY3 ms23
 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 ms23
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY4 ms23
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown1 ms23
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account2 ms23
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Then An exception was thrown2 ms23
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed2 ms23
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"4 ms23
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed5 ms23
 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 ms23
 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 ms23
 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 ms23
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed6 ms23
 Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown1 ms23
 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 allowed2 ms23
 Scenario: Start broker for all scenarios.Given Start Broker2 ms23
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms23
 Scenario: Send BIRTH message and then DC message.And Bundles are requested4 ms23
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message4 ms23
 Scenario: Start broker for all scenarios.Given Start Broker2 ms23
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms23
 Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Then Device is connected with "localhost" server ip3 ms23
 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 file3 ms23
 Scenario: Start broker for all scenarios.Given Start Broker2 ms23
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms23
 Scenario: Send BIRTH message and then DC message while broker ip is set by System.Then Device is connected with "localhost" server ip1 ms23
 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 System4 ms23
 Scenario: Start broker for all scenarios.Given Start Broker1 ms23
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms23
 Scenario: Start broker for all scenarios.Given Start Broker2 ms23
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms23
 Scenario: Stealing link scenario.And Client named "client-2" is not connected2 ms23
 Scenario: Stealing link scenario.Scenario: Stealing link scenario3 ms23
 Scenario: Start broker for all scenarios.Given Start Broker2 ms23
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms23
 Scenario: Connect to the system and publish some data.Then Device sim-1 for account kapua-sys is registered after 5 seconds1 ms23
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data2 ms23
 Scenario: Start broker for all scenarios.Given Start Broker1 ms23
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms23
 Scenario: Start broker for all scenarios.Given Start Broker3 ms23
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios4 ms23
 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 ms23
 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 ms23
 Scenario: Installing a package.Then Device sim-1 for account kapua-sys is registered after 5 seconds5 ms23
 Scenario: Installing a package.Scenario: Installing a package7 ms23
 Scenario: Start broker for all scenarios.Given Start Broker1 ms23
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms23

All Tests

PackageDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
(root)4.1 sec122+1221349+13343353-14564824
org.eclipse.kapua27 ms0033
org.eclipse.kapua.broker.core.plugin3.3 sec001515
org.eclipse.kapua.client.gateway88 ms004343
org.eclipse.kapua.client.gateway.kura0.16 sec001414
org.eclipse.kapua.client.gateway.spi.util2.7 sec001515
org.eclipse.kapua.client.gateway.util2 ms0033
org.eclipse.kapua.commons.about0.49 sec0011
org.eclipse.kapua.commons.configuration93 ms0011
org.eclipse.kapua.commons.configuration.metatype17 ms001919
org.eclipse.kapua.commons.liquibase5.9 sec0044
org.eclipse.kapua.commons.metric6 ms0022
org.eclipse.kapua.commons.model0.24 sec0088
org.eclipse.kapua.commons.model.id4 ms0011
org.eclipse.kapua.commons.security2.8 sec0033
org.eclipse.kapua.commons.setting1 ms0044
org.eclipse.kapua.commons.util67 ms003838
org.eclipse.kapua.commons.util.xml0.47 sec0099
org.eclipse.kapua.kura.simulator.main.simulation5.5 sec001313
org.eclipse.kapua.locator.internal0.33 sec021012
org.eclipse.kapua.message.internal0.21 sec022628
org.eclipse.kapua.message.internal.device.data0 ms0033
org.eclipse.kapua.message.internal.device.lifecycle45 ms002121
org.eclipse.kapua.message.internal.xml1.6 sec001111
org.eclipse.kapua.service.authentication.shiro.exceptions20 ms0022
org.eclipse.kapua.service.authorization.shiro17 sec001919
org.eclipse.kapua.service.datastore.client.transport0.35 sec031922
org.eclipse.kapua.service.datastore.internal6 min 11 sec052732
org.eclipse.kapua.service.datastore.internal.client3.2 sec0077
org.eclipse.kapua.service.device.management.commons.message.notification7 ms0022
org.eclipse.kapua.service.user.internal.setting0.26 sec0011