Test Result

83 failures (+24) , 842 skipped (+416)
19,913 tests (±0)
Took 1 hr 47 min.

All Failed Tests

Test NameDurationAge
 Scenario: Send BIRTH message and then DC message.And Bundles are requested1 ms1
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message2 ms1
 Scenario: Restarting a job with valid Configuration Put step two times.When Device is connected4 ms1
 Scenario: Restarting a job with valid Configuration Put step two times.Scenario: Restarting a job with valid Configuration Put step two times5 ms1
 Scenario: Restarting a job with invalid Configuration Put step two times.When Device is connected0 ms1
 Scenario: Restarting a job with invalid Configuration Put step two times.Scenario: Restarting a job with invalid Configuration Put step two times0 ms1
 Scenario: Restarting a job with valid Package Install step two times.And Device is connected0 ms1
 Scenario: Restarting a job with valid Package Install step two times.Scenario: Restarting a job with valid Package Install step two times0 ms1
 Scenario: Restarting a job with invalid Package Install step two times.And Device is connected0 ms1
 Scenario: Restarting a job with invalid Package Install step two times.Scenario: Restarting a job with invalid Package Install step two times0 ms1
 Scenario: Restarting job With valid Asset Write step two times.When Device is connected0 ms1
 Scenario: Restarting job With valid Asset Write step two times.Scenario: Restarting job With valid Asset Write step two times0 ms1
 Scenario: Restarting job with invalid Asset Write step two times.When Device is connected0 ms1
 Scenario: Restarting job with invalid Asset Write step two times.Scenario: Restarting job with invalid Asset Write step two times0 ms1
 Scenario: Restarting job with valid Configuration Put and Command Execution steps two times.And Device is connected0 ms1
 Scenario: Restarting job with valid Configuration Put and Command Execution steps two times.Scenario: Restarting job with valid Configuration Put and Command Execution steps two times0 ms1
 Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times.And Device is connected1 ms1
 Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times.Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times1 ms1
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times.When Device is connected0 ms1
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times.Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times0 ms1
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times.When Device is connected0 ms1
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times.Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times0 ms1
 Scenario: Restarting a job with valid Configuration Put step and multiple devices two times.And Devices are connected0 ms1
 Scenario: Restarting a job with valid Configuration Put step and multiple devices two times.Scenario: Restarting a job with valid Configuration Put step and multiple devices two times0 ms1
 Scenario: Restarting a job with invalid Configuration Put and multiple devices two times.And Devices are connected0 ms1
 Scenario: Restarting a job with invalid Configuration Put and multiple devices two times.Scenario: Restarting a job with invalid Configuration Put and multiple devices two times0 ms1
 Scenario: Restarting a job with valid Package Install step and multiple devices two times.And Devices are connected0 ms1
 Scenario: Restarting a job with valid Package Install step and multiple devices two times.Scenario: Restarting a job with valid Package Install step and multiple devices two times0 ms1
 Scenario: Restarting a job with invalid Package Install step and multiple devices two times.And Devices are connected0 ms1
 Scenario: Restarting a job with invalid Package Install step and multiple devices two times.Scenario: Restarting a job with invalid Package Install step and multiple devices two times0 ms1
 Scenario: Restarting job with valid Asset Write step and multiple devices two times.When Devices are connected0 ms1
 Scenario: Restarting job with valid Asset Write step and multiple devices two times.Scenario: Restarting job with valid Asset Write step and multiple devices two times0 ms1
 Scenario: Restarting job With invalid Asset Write and multiple two times.When Devices are connected0 ms1
 Scenario: Restarting job With invalid Asset Write and multiple two times.Scenario: Restarting job With invalid Asset Write and multiple two times0 ms1
 Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times.And Devices are connected0 ms1
 Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times.Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times0 ms1
 Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times.And Devices are connected0 ms1
 Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times.Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times0 ms1
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times.When Devices are connected0 ms1
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times.Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times0 ms1
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times.When Devices are connected0 ms1
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times.Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times0 ms1
 Scenario: Create scheduler with end date before start date.Then I create a new trigger from the existing creator with previously defined date properties7 ms15
 Scenario: Create scheduler with end date before start date.Scenario: Create scheduler with end date before start date7 ms15
 Scenario: Create scheduler with correct end date.Then I create a new trigger from the existing creator with previously defined date properties1 ms15
 Scenario: Create scheduler with correct end date.Scenario: Create scheduler with correct end date2 ms15
 Scenario: Update trigger definition.And I try to edit trigger definition to "Cron Job"1 ms15
 Scenario: Update trigger definition.Scenario: Update trigger definition2 ms15
 Scenario: Update scheduler end date.And I try to edit end date to 13-12-2020 at 10:001 ms15
 Scenario: Update scheduler end date.Scenario: Update scheduler end date2 ms15
 org.eclipse.kapua.integration.misc.DefaultAuthenticatorTest.connectAdminTest11 ms17
 org.eclipse.kapua.integration.misc.DefaultAuthenticatorTest.disconnectAdminTest2 ms17
 org.eclipse.kapua.integration.misc.DefaultAuthenticatorTest.disconnectUserTest1 ms17
 org.eclipse.kapua.integration.misc.DefaultAuthenticatorTest.connectAdminEmptyOptionsTest2 ms17
 Scenario: List Endpoints From "kapua-sys" Account.Then I find 3 endpoints1 ms17
 Scenario: List Endpoints From "kapua-sys" Account.Scenario: List Endpoints From "kapua-sys" Account1 ms17
 Scenario: List Endpoints From Sub-account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22221 ms17
 Scenario: List Endpoints From Sub-account.Scenario: List Endpoints From Sub-account2 ms17
 Scenario: List Endpoints Created From Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22221 ms17
 Scenario: List Endpoints Created From Sub-Account.Scenario: List Endpoints Created From Sub-Account2 ms17
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms17
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.Scenario: List Endpoints From Sub-Account Of Another Sub-Account2 ms17
 Scenario: Start datastore for all scenarios.Given Start Datastore1 ms17
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios1 ms17
 Scenario: Add datastore permissions to the role.And I search for data message with id "fake-id"1 ms17
 Scenario: Add datastore permissions to the role.Scenario: Add datastore permissions to the role1 ms17
 Scenario: Init Security Context for all scenarios.Scenario: Init Security Context for all scenarios0.95 sec17
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios0.9 sec17
 Scenario: Deleting user in account that is lower in hierarchy.Scenario: Deleting user in account that is lower in hierarchy0.89 sec17
 Scenario: Deleting user in account that is higher in hierarchy.Scenario: Deleting user in account that is higher in hierarchy0.91 sec17
 Scenario: Create same user in different accounts.Scenario: Create same user in different accounts0.88 sec17
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios0.9 sec17
 Scenario: Reset Security Context for all scenarios.Scenario: Reset Security Context for all scenarios0.89 sec17
 Scenario: Start Jetty server for all scenarios.Given Start Jetty Server on host "127.0.0.1" at port "8081"0 ms19
 Scenario: Start Jetty server for all scenarios.Scenario: Start Jetty server for all scenarios1 ms19
 Scenario: Simple Jetty with rest-api war.When REST POST call at "/v1/authentication/user" with JSON "{"password": "kapua-password", "username": "kapua-sys"}"1 ms19
 Scenario: Simple Jetty with rest-api war.Scenario: Simple Jetty with rest-api war1 ms19
 Scenario: Bug when user can retrieve user in another account if it has other account's user id.Then REST POST call at "/v1/authentication/user" with JSON "{"password": "ToManySecrets123#", "username": "kapua-a"}"1 ms19
 Scenario: Bug when user can retrieve user in another account if it has other account's user id.Scenario: Bug when user can retrieve user in another account if it has other account's user id2 ms19
 Scenario: Execute possible docker steps to show its usage.Given List images by name "kapua/kapua-broker:1.5.0-SNAPSHOT"1 ms24
 Scenario: Execute possible docker steps to show its usage.Scenario: Execute possible docker steps to show its usage2 ms24
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"4 ms37
 Scenario: Creating unique Access Group with special symbols in description.Scenario: Creating unique Access Group with special symbols in description5 ms37

All Tests

PackageDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
(root)18 sec79+24832+41615652-44016563
Scenario: Creating And Account Without "6 ms0066
org.eclipse.kapua0.14 sec00102102
org.eclipse.kapua.app.api.core.model.data0.32 sec003838
org.eclipse.kapua.app.api.web4.7 sec001010
org.eclipse.kapua.broker29 ms0077
org.eclipse.kapua.broker.core79 ms0099
org.eclipse.kapua.broker.core.converter0.15 sec007474
org.eclipse.kapua.broker.core.listener85 ms002424
org.eclipse.kapua.broker.core.message0.6 sec004141
org.eclipse.kapua.broker.core.message.system18 ms0077
org.eclipse.kapua.broker.core.plugin2.2 sec008484
org.eclipse.kapua.broker.core.plugin.authentication0 ms0011
org.eclipse.kapua.broker.core.plugin.authorization58 ms001414
org.eclipse.kapua.broker.core.plugin.metric17 ms0099
org.eclipse.kapua.broker.core.pool0.26 sec003434
org.eclipse.kapua.broker.core.router0.54 sec007171
org.eclipse.kapua.broker.core.security27 ms002222
org.eclipse.kapua.broker.core.setting0 ms0044
org.eclipse.kapua.client.gateway52 ms006262
org.eclipse.kapua.client.gateway.kura0.36 sec003535
org.eclipse.kapua.client.gateway.kura.internal62 ms002222
org.eclipse.kapua.client.gateway.mqtt0.29 sec004141
org.eclipse.kapua.client.gateway.mqtt.fuse0.38 sec002121
org.eclipse.kapua.client.gateway.mqtt.fuse.internal18 ms0044
org.eclipse.kapua.client.gateway.mqtt.paho.internal0.2 sec001818
org.eclipse.kapua.client.gateway.profile.kura0.1 sec001616
org.eclipse.kapua.client.gateway.spi0.19 sec00241241
org.eclipse.kapua.client.gateway.spi.util5.2 sec008888
org.eclipse.kapua.client.gateway.util2 ms0033
org.eclipse.kapua.commons.about0.72 sec001212
org.eclipse.kapua.commons.cache0.12 sec0088
org.eclipse.kapua.commons.configuration75 ms00137137
org.eclipse.kapua.commons.configuration.metatype7 ms00134134
org.eclipse.kapua.commons.event2 ms003939
org.eclipse.kapua.commons.liquibase0.54 sec0044
org.eclipse.kapua.commons.metric7 ms0066
org.eclipse.kapua.commons.model1 ms004848
org.eclipse.kapua.commons.model.id93 ms002424
org.eclipse.kapua.commons.model.query0 ms00119119
org.eclipse.kapua.commons.model.query.predicate1 ms002929
org.eclipse.kapua.commons.security3 sec0033
org.eclipse.kapua.commons.service.event.store.internal14 ms002323
org.eclipse.kapua.commons.service.internal.cache68 ms002222
org.eclipse.kapua.commons.service.internal.cache.dummy11 ms005555
org.eclipse.kapua.commons.setting81 ms00101101
org.eclipse.kapua.commons.setting.system0 ms0044
org.eclipse.kapua.commons.util4.1 sec00166166
org.eclipse.kapua.commons.util.log2.1 sec002727
org.eclipse.kapua.commons.util.xml0.91 sec001212
org.eclipse.kapua.entity0 ms0022
org.eclipse.kapua.event66 ms001616
org.eclipse.kapua.integration.misc9.9 sec41483488
org.eclipse.kapua.integration.service.datastoreJunit0 ms0505
org.eclipse.kapua.kura.simulator.main.simulation5.3 sec001313
org.eclipse.kapua.locator2 ms001010
org.eclipse.kapua.locator.internal0.12 sec021012
org.eclipse.kapua.message.internal17 ms022628
org.eclipse.kapua.message.internal.device.data1 ms0033
org.eclipse.kapua.message.internal.device.lifecycle5 ms001717
org.eclipse.kapua.message.internal.xml1.8 sec001111
org.eclipse.kapua.model0 ms0011
org.eclipse.kapua.model.domain0 ms0022
org.eclipse.kapua.model.id1 ms0044
org.eclipse.kapua.model.query1 ms0022
org.eclipse.kapua.model.type4 ms001717
org.eclipse.kapua.model.xml22 ms001919
org.eclipse.kapua.service.authentication.credential.mfa.shiro74 ms005151
org.eclipse.kapua.service.authentication.credential.shiro80 ms003737
org.eclipse.kapua.service.authentication.shiro14 ms004949
org.eclipse.kapua.service.authentication.shiro.exceptions26 ms001414
org.eclipse.kapua.service.authentication.shiro.mfa20 sec001414
org.eclipse.kapua.service.authentication.shiro.realm0.72 sec002727
org.eclipse.kapua.service.authentication.shiro.registration7 ms0066
org.eclipse.kapua.service.authentication.shiro.setting89 ms0066
org.eclipse.kapua.service.authentication.shiro.utils2.8 sec001919
org.eclipse.kapua.service.authentication.token.shiro0.61 sec003939
org.eclipse.kapua.service.authorization.access.shiro64 ms008585
org.eclipse.kapua.service.authorization.domain.shiro16 ms004141
org.eclipse.kapua.service.authorization.group.shiro5 ms002525
org.eclipse.kapua.service.authorization.role.shiro14 ms003838
org.eclipse.kapua.service.authorization.shiro5 ms0055
org.eclipse.kapua.service.authorization.shiro.exception3 ms001313
org.eclipse.kapua.service.authorization.shiro.setting1 ms0033
org.eclipse.kapua.service.config30 ms001313
org.eclipse.kapua.service.datastore.test.junit0.16 sec0066
org.eclipse.kapua.service.datastore.test.junit.utils0.17 sec0077
org.eclipse.kapua.service.device.management.commons.message.notification6 ms0022
org.eclipse.kapua.service.elasticsearch.client.transport2.2 sec0055
org.eclipse.kapua.service.elasticsearch.client.utils0.1 sec0033
org.eclipse.kapua.service.stream3 ms0044
org.eclipse.kapua.transport.exception22 ms002929
org.eclipse.kapua.transport.mqtt.test.message.mqtt18 ms002323
org.eclipse.kapua.transport.mqtt.test.mqtt33 ms0088
org.eclipse.kapua.transport.mqtt.test.mqtt.exception70 ms004343
org.eclipse.kapua.transport.utils40 ms0044