Skip to content
[Jenkins]Jenkins
log in

Test Result

121 failures (-787) , 448 skipped (-2834)
2,478 tests (-3591)
Took 20 min.

All Failed Tests

Test NameDurationAge
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios4.1 sec2
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account4 ms2
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed6 ms2
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY5 ms2
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account4 ms2
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed5 ms2
 Scenario: Send BIRTH message and then DC message while broker ip is NOT set.And Device birth message is sent0 ms2
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios1.7 sec2
 Scenario: Handling of a disconnect message from a non existing device.Scenario: Handling of a disconnect message from a non existing device0 ms2
 Scenario: Birth and death message handling.Scenario: Birth and death message handling0 ms2
 Scenario: Birth and missing event handling.Scenario: Birth and missing event handling0 ms2
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.67 sec3
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Given Mqtt Device is started0 ms3
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic0 ms3
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Given Mqtt Device is started3 ms3
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY5 ms3
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started4 ms3
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY6 ms3
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started3 ms3
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY4 ms3
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started3 ms3
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.Given Mqtt Device is started0 ms3
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.Scenario: B5 Broker publish to CTRL_ACC is not allowed0 ms3
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started3 ms3
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed5 ms3
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Given Mqtt Device is started7 ms3
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed9 ms3
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started4 ms3
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI7 ms3
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started2 ms3
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed4 ms3
 Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.Given Mqtt Device is started0 ms3
 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 allowed2 ms3
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Given Mqtt Device is started3 ms3
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed5 ms3
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started3 ms3
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI4 ms3
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started5 ms3
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed6 ms3
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started4 ms3
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Given Mqtt Device is started3 ms3
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY4 ms3
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started3 ms3
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY3 ms3
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started2 ms3
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY4 ms3
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started3 ms3
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account4 ms3
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Given Mqtt Device is started3 ms3
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Scenario: D5 Device subscribe - publish - admin on CTRL_ACC5 ms3
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started2 ms3
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI4 ms3
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started4 ms3
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed8 ms3
 Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.Given Mqtt Device is started2 ms3
 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 ms3
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Given Mqtt Device is started2 ms3
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed4 ms3
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Given Mqtt Device is started3 ms3
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI5 ms3
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started6 ms3
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed8 ms3
 Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started0 ms3
 Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed1 ms3
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Given Mqtt Device is started4 ms3
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Given Mqtt Device is started3 ms3
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY4 ms3
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Given Mqtt Device is started3 ms3
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY5 ms3
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Given Mqtt Device is started2 ms3
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Given Mqtt Device is started4 ms3
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Scenario: DV5 Data view publish to CTRL_ACC is not allowed6 ms3
 Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed.Given Mqtt Device is started2 ms3
 Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed.Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed4 ms3
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Given Mqtt Device is started3 ms3
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Given Mqtt Device is started3 ms3
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI5 ms3
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Given Mqtt Device is started4 ms3
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed5 ms3
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Given Mqtt Device is started0 ms3
 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 allowed0 ms3
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Given Mqtt Device is started2 ms3
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed3 ms3
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Given Mqtt Device is started0 ms3
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed1 ms3
 Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed.Given Mqtt Device is started2 ms3
 Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed.Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed4 ms3
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Given Mqtt Device is started4 ms3
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms3
 Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Given Mqtt Device is started2 ms3
 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 allowed3 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios9.9 sec3
 Scenario: Send BIRTH message and then DC message while broker ip is NOT set.Scenario: Send BIRTH message and then DC message while broker ip is NOT set0 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3.8 sec3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.58 sec3
 Scenario: Positive scenario without stealing link.And topic "$EDC/kapua-sys/client-1/MQTT/BIRTH" content "src/test/resources/mqtt/rpione3_MQTT_BIRTH.mqtt" is published by client named "client-1"0 ms3
 Scenario: Positive scenario without stealing link.Scenario: Positive scenario without stealing link0 ms3
 Scenario: Stealing link scenario.And topic "$EDC/kapua-sys/client-1/MQTT/BIRTH" content "src/test/resources/mqtt/rpione3_MQTT_BIRTH.mqtt" is published by client named "client-1"0 ms3
 Scenario: Stealing link scenario.Scenario: Stealing link scenario0 ms3
 Scenario: Negative scenario when client connects twice with same client id.And topic "$EDC/kapua-sys/client-1/MQTT/BIRTH" content "src/test/resources/mqtt/rpione3_MQTT_BIRTH.mqtt" is published by client named "client-1-1"0 ms3
 Scenario: Negative scenario when client connects twice with same client id.Scenario: Negative scenario when client connects twice with same client id0 ms3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 sec3
 Scenario: Connect to the system and publish some data.Then Device sim-1 for account kapua-sys is registered after 5 seconds20 ms3
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data20 ms3
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios3.5 sec3
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0.6 sec3
 Scenario: Birth message handling from a new device.When I login as user with name "kapua-sys" and password "kapua-password"2 ms3
 Scenario: Birth message handling from a new device.Scenario: Birth message handling from a new device3 ms3
 Scenario: Birth message handling from an existing device.When I login as user with name "kapua-sys" and password "kapua-password"0 ms3
 Scenario: Birth message handling from an existing device.Scenario: Birth message handling from an existing device0 ms3
 Scenario: Handling of 2 birth messages.When I login as user with name "kapua-sys" and password "kapua-password"0 ms3
 Scenario: Handling of 2 birth messages.Scenario: Handling of 2 birth messages0 ms3
 Scenario: Handling of a disconnect message from a non existing device.When I login as user with name "kapua-sys" and password "kapua-password"0 ms3
 Scenario: Birth and death message handling.When I login as user with name "kapua-sys" and password "kapua-password"0 ms3
 Scenario: Birth and missing event handling.When I login as user with name "kapua-sys" and password "kapua-password"0 ms3
 Scenario: Birth and applications event handling.When I login as user with name "kapua-sys" and password "kapua-password"0 ms3
 Scenario: Birth and applications event handling.Scenario: Birth and applications event handling0 ms3
 Scenario: Creating new device and tagging it with specific Tag.When I login as user with name "kapua-sys" and password "kapua-password"0 ms3
 Scenario: Creating new device and tagging it with specific Tag.Scenario: Creating new device and tagging it with specific Tag0 ms3
 Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag.When I login as user with name "kapua-sys" and password "kapua-password"0 ms3
 Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag.Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag0 ms3

All Tests

PackageDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
(root)1 min 4 sec121-786436-28341566+292123-3591
org.eclipse.kapua36 ms0011
org.eclipse.kapua.broker.core.plugin2.9 sec001515
org.eclipse.kapua.client.gateway19 ms004343
org.eclipse.kapua.client.gateway.kura0.13 sec001414
org.eclipse.kapua.client.gateway.spi.util2.7 sec001515
org.eclipse.kapua.client.gateway.util31 ms0033
org.eclipse.kapua.commons.about0.22 sec0011
org.eclipse.kapua.commons.configuration45 ms0011
org.eclipse.kapua.commons.configuration.metatype9 ms001919
org.eclipse.kapua.commons.metric5 ms0022
org.eclipse.kapua.commons.model0.15 sec0088
org.eclipse.kapua.commons.model.id12 ms0011
org.eclipse.kapua.commons.security2.8 sec0033
org.eclipse.kapua.commons.setting2 ms0044
org.eclipse.kapua.commons.util78 ms003838
org.eclipse.kapua.commons.util.xml0.21 sec0099
org.eclipse.kapua.kura.simulator.main.simulation4.4 sec001313
org.eclipse.kapua.locator.internal0.16 sec021012
org.eclipse.kapua.message.internal0.33 sec022426
org.eclipse.kapua.message.internal.device.data1 ms0044
org.eclipse.kapua.message.internal.device.lifecycle12 ms002525
org.eclipse.kapua.message.internal.xml1.8 sec001111
org.eclipse.kapua.service.authentication.shiro.exceptions25 ms0022
org.eclipse.kapua.service.authorization.shiro13 sec001919
org.eclipse.kapua.service.datastore.client.transport0.37 sec031922
org.eclipse.kapua.service.datastore.internal4 min 46 sec0-1527+132
org.eclipse.kapua.service.datastore.internal.client3.9 sec0077
org.eclipse.kapua.service.liquibase13 sec0044
org.eclipse.kapua.service.user.internal.setting0 ms0011