Test Result

129 failures (+72) , 633 skipped (+219)
19,913 tests (±0)
Took 2 hr 34 min.

All Failed Tests

Test NameDurationAge
 Scenario: Delete items by date ranges.Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"2 ms1
 Scenario: Delete items by date ranges.Scenario: Delete items by date ranges3 ms1
 Scenario: Delete items by the datastore ID.Given I delete all indices0 ms1
 Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID1 ms1
 Scenario: Delete items based on query results.Then I store the messages from list "TestMessages1" and remember the IDs as "StoredMessageIDs1"2 ms1
 Scenario: Delete items based on query results.Scenario: Delete items based on query results3 ms1
 Scenario: Check the mapping for message semantic topics.Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"2 ms1
 Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics3 ms1
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.When broker with clientId "client-1" and user "kapua-sys" and password "kapua-password" is listening on topic "#"0 ms1
 Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic0 ms1
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY0 ms1
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY0 ms1
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "$EDC/acme/client-1/CONF-V1/REPLY"0 ms1
 Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY0 ms1
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: B5 Broker publish to CTRL_ACC is not allowed.Scenario: B5 Broker publish to CTRL_ACC is not allowed0 ms1
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed0 ms1
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "$EDC/acme/client-1/foo"0 ms1
 Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI0 ms1
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed0 ms1
 Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 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 allowed0 ms1
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "acme/client-1/foo"0 ms1
 Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI0 ms1
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed0 ms1
 Scenario: D1 Device publish to CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""1 ms1
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY1 ms1
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY0 ms1
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "$EDC/acme/client-1/CONF-V1/REPLY"0 ms1
 Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY0 ms1
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "$EDC/acme/foo"0 ms1
 Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Scenario: D5 Device subscribe - publish - admin on CTRL_ACC0 ms1
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "$EDC/acme/client-1/foo"0 ms1
 Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI0 ms1
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed0 ms1
 Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 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 allowed0 ms1
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "acme/client-1/foo"0 ms1
 Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI0 ms1
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed0 ms1
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY0 ms1
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY0 ms1
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "$EDC/acme/client-1/CONF-V1/REPLY"0 ms1
 Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY0 ms1
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Scenario: DV5 Data view publish to CTRL_ACC is not allowed0 ms1
 Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 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 allowed0 ms1
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "$EDC/acme/client-1/foo"0 ms1
 Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI0 ms1
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed0 ms1
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""1 ms1
 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 allowed2 ms1
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic "acme"0 ms1
 Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed0 ms1
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed0 ms1
 Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 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 allowed0 ms1
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.When broker with clientId "client-1" and user "luise" and password "KeepCalm123." is listening on topic ""0 ms1
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed0 ms1
 Scenario: Connect to the system and publish some data.Then I expect the number of messages for this device to be 51 ms1
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data2 ms1
 Scenario: Restarting job with valid Bundle Stop step and multiple devices two times.And Bundles are requested12 ms1
 Scenario: Restarting job with valid Bundle Stop step and multiple devices two times.Scenario: Restarting job with valid Bundle Stop step and multiple devices two times13 ms1
 Scenario: Executing Job When Device Connected After The Specified Start Date And Time.Scenario: Executing Job When Device Connected After The Specified Start Date And Time2 ms2
 Scenario: Executing Job When Device Connected Before The Specified Start Date And Time.Scenario: Executing Job When Device Connected Before The Specified Start Date And Time4 ms2
 Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time2 ms2
 Scenario: Executing Job When Device Connected After End Date And Time.Scenario: Executing Job When Device Connected After End Date And Time3 ms2
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device3 ms2
 Scenario: Executing Job Without Steps.Scenario: Executing Job Without Steps3 ms2
 Scenario: Create scheduler with end date before start date.Then I create a new trigger from the existing creator with previously defined date properties14 ms4
 Scenario: Create scheduler with end date before start date.Scenario: Create scheduler with end date before start date14 ms4
 Scenario: Create scheduler with correct end date.Then I create a new trigger from the existing creator with previously defined date properties2 ms4
 Scenario: Create scheduler with correct end date.Scenario: Create scheduler with correct end date4 ms4
 Scenario: Update trigger definition.And I try to edit trigger definition to "Cron Job"1 ms4
 Scenario: Update trigger definition.Scenario: Update trigger definition2 ms4
 Scenario: Update scheduler end date.And I try to edit end date to 13-12-2020 at 10:001 ms4
 Scenario: Update scheduler end date.Scenario: Update scheduler end date2 ms4
 org.eclipse.kapua.integration.misc.DefaultAuthenticatorTest.connectAdminTest24 ms6
 org.eclipse.kapua.integration.misc.DefaultAuthenticatorTest.disconnectAdminTest3 ms6
 org.eclipse.kapua.integration.misc.DefaultAuthenticatorTest.disconnectUserTest3 ms6
 org.eclipse.kapua.integration.misc.DefaultAuthenticatorTest.connectAdminEmptyOptionsTest2 ms6
 Scenario: List Endpoints From "kapua-sys" Account.Then I find 3 endpoints1 ms6
 Scenario: List Endpoints From "kapua-sys" Account.Scenario: List Endpoints From "kapua-sys" Account1 ms6
 Scenario: List Endpoints From Sub-account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms6
 Scenario: List Endpoints From Sub-account.Scenario: List Endpoints From Sub-account4 ms6
 Scenario: List Endpoints Created From Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22223 ms6
 Scenario: List Endpoints Created From Sub-Account.Scenario: List Endpoints Created From Sub-Account3 ms6
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms6
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.Scenario: List Endpoints From Sub-Account Of Another Sub-Account3 ms6
 Scenario: Start datastore for all scenarios.Given Start Datastore1 ms6
 Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios2 ms6
 Scenario: Add datastore permissions to the role.And I search for data message with id "fake-id"1 ms6
 Scenario: Add datastore permissions to the role.Scenario: Add datastore permissions to the role2 ms6
 Scenario: Init Security Context for all scenarios.Scenario: Init Security Context for all scenarios1.9 sec6
 Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios1.9 sec6
 Scenario: Deleting user in account that is lower in hierarchy.Scenario: Deleting user in account that is lower in hierarchy1.9 sec6
 Scenario: Deleting user in account that is higher in hierarchy.Scenario: Deleting user in account that is higher in hierarchy1.8 sec6
 Scenario: Create same user in different accounts.Scenario: Create same user in different accounts1.9 sec6
 Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios1.8 sec6
 Scenario: Reset Security Context for all scenarios.Scenario: Reset Security Context for all scenarios1.8 sec6
 Scenario: Start Jetty server for all scenarios.Given Start Jetty Server on host "127.0.0.1" at port "8081"1 ms8
 Scenario: Start Jetty server for all scenarios.Scenario: Start Jetty server for all scenarios2 ms8
 Scenario: Simple Jetty with rest-api war.When REST POST call at "/v1/authentication/user" with JSON "{"password": "kapua-password", "username": "kapua-sys"}"2 ms8
 Scenario: Simple Jetty with rest-api war.Scenario: Simple Jetty with rest-api war3 ms8
 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"}"2 ms8
 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 id3 ms8
 Scenario: Execute possible docker steps to show its usage.Given List images by name "kapua/kapua-broker:1.5.0-SNAPSHOT"2 ms13
 Scenario: Execute possible docker steps to show its usage.Scenario: Execute possible docker steps to show its usage2 ms13
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"11 ms26
 Scenario: Creating unique Access Group with special symbols in description.Scenario: Creating unique Access Group with special symbols in description11 ms26
 Scenario: Executing Job When Device Connected After The Specified Start Date And Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms731
 Scenario: Executing Job When Device Connected Before The Specified Start Date And Time.When I search for events from device "rpione3" in account "kapua-sys"2 ms731
 Scenario: Executing Job When Device Connected Before End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms731
 Scenario: Executing Job When Device Connected After End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"2 ms731
 Scenario: Executing Job And Then Restarting Device.When I search for events from device "rpione3" in account "kapua-sys"2 ms731
 Scenario: Executing Job Without Steps.When I search for events from device "rpione3" in account "kapua-sys"2 ms731

All Tests

PackageDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
(root)34 sec125+72623+21915815-29116563
Scenario: Creating And Account Without "7 ms0066
org.eclipse.kapua0.45 sec00102102
org.eclipse.kapua.app.api.core.model.data0.67 sec003838
org.eclipse.kapua.app.api.web9.2 sec001010
org.eclipse.kapua.broker28 ms0077
org.eclipse.kapua.broker.core0.18 sec0099
org.eclipse.kapua.broker.core.converter0.28 sec007474
org.eclipse.kapua.broker.core.listener0.21 sec002424
org.eclipse.kapua.broker.core.message1.3 sec004141
org.eclipse.kapua.broker.core.message.system33 ms0077
org.eclipse.kapua.broker.core.plugin4.7 sec008484
org.eclipse.kapua.broker.core.plugin.authentication0 ms0011
org.eclipse.kapua.broker.core.plugin.authorization66 ms001414
org.eclipse.kapua.broker.core.plugin.metric36 ms0099
org.eclipse.kapua.broker.core.pool0.41 sec003434
org.eclipse.kapua.broker.core.router1.1 sec007171
org.eclipse.kapua.broker.core.security63 ms002222
org.eclipse.kapua.broker.core.setting0 ms0044
org.eclipse.kapua.client.gateway0.2 sec006262
org.eclipse.kapua.client.gateway.kura0.7 sec003535
org.eclipse.kapua.client.gateway.kura.internal0.16 sec002222
org.eclipse.kapua.client.gateway.mqtt0.91 sec004141
org.eclipse.kapua.client.gateway.mqtt.fuse0.72 sec002121
org.eclipse.kapua.client.gateway.mqtt.fuse.internal31 ms0044
org.eclipse.kapua.client.gateway.mqtt.paho.internal0.47 sec001818
org.eclipse.kapua.client.gateway.profile.kura0.22 sec001616
org.eclipse.kapua.client.gateway.spi0.45 sec00241241
org.eclipse.kapua.client.gateway.spi.util5.5 sec008888
org.eclipse.kapua.client.gateway.util3 ms0033
org.eclipse.kapua.commons.about1 sec001212
org.eclipse.kapua.commons.cache0.23 sec0088
org.eclipse.kapua.commons.configuration0.15 sec00137137
org.eclipse.kapua.commons.configuration.metatype7 ms00134134
org.eclipse.kapua.commons.event4 ms003939
org.eclipse.kapua.commons.liquibase1.1 sec0044
org.eclipse.kapua.commons.metric7 ms0066
org.eclipse.kapua.commons.model4 ms004848
org.eclipse.kapua.commons.model.id0.23 sec002424
org.eclipse.kapua.commons.model.query0 ms00119119
org.eclipse.kapua.commons.model.query.predicate0 ms002929
org.eclipse.kapua.commons.security3 sec0033
org.eclipse.kapua.commons.service.event.store.internal34 ms002323
org.eclipse.kapua.commons.service.internal.cache36 ms002222
org.eclipse.kapua.commons.service.internal.cache.dummy9 ms005555
org.eclipse.kapua.commons.setting90 ms00101101
org.eclipse.kapua.commons.setting.system0 ms0044
org.eclipse.kapua.commons.util2.1 sec00166166
org.eclipse.kapua.commons.util.log4.7 sec002727
org.eclipse.kapua.commons.util.xml2.2 sec001212
org.eclipse.kapua.entity0 ms0022
org.eclipse.kapua.event80 ms001616
org.eclipse.kapua.integration.misc18 sec41483488
org.eclipse.kapua.integration.service.datastoreJunit0 ms0505
org.eclipse.kapua.kura.simulator.main.simulation5.7 sec001313
org.eclipse.kapua.locator5 ms001010
org.eclipse.kapua.locator.internal0.75 sec021012
org.eclipse.kapua.message.internal75 ms022628
org.eclipse.kapua.message.internal.device.data0 ms0033
org.eclipse.kapua.message.internal.device.lifecycle10 ms001717
org.eclipse.kapua.message.internal.xml3.9 sec001111
org.eclipse.kapua.model0 ms0011
org.eclipse.kapua.model.domain1 ms0022
org.eclipse.kapua.model.id0 ms0044
org.eclipse.kapua.model.query57 ms0022
org.eclipse.kapua.model.type8 ms001717
org.eclipse.kapua.model.xml44 ms001919
org.eclipse.kapua.service.authentication.credential.mfa.shiro0.16 sec005151
org.eclipse.kapua.service.authentication.credential.shiro0.22 sec003737
org.eclipse.kapua.service.authentication.shiro30 ms004949
org.eclipse.kapua.service.authentication.shiro.exceptions46 ms001414
org.eclipse.kapua.service.authentication.shiro.mfa39 sec001414
org.eclipse.kapua.service.authentication.shiro.realm1.4 sec002727
org.eclipse.kapua.service.authentication.shiro.registration7 ms0066
org.eclipse.kapua.service.authentication.shiro.setting0.2 sec0066
org.eclipse.kapua.service.authentication.shiro.utils5.4 sec001919
org.eclipse.kapua.service.authentication.token.shiro1.3 sec003939
org.eclipse.kapua.service.authorization.access.shiro95 ms008585
org.eclipse.kapua.service.authorization.domain.shiro28 ms004141
org.eclipse.kapua.service.authorization.group.shiro17 ms002525
org.eclipse.kapua.service.authorization.role.shiro56 ms003838
org.eclipse.kapua.service.authorization.shiro52 ms0055
org.eclipse.kapua.service.authorization.shiro.exception4 ms001313
org.eclipse.kapua.service.authorization.shiro.setting2 ms0033
org.eclipse.kapua.service.config70 ms001313
org.eclipse.kapua.service.datastore.test.junit0.39 sec0066
org.eclipse.kapua.service.datastore.test.junit.utils0.48 sec0077
org.eclipse.kapua.service.device.management.commons.message.notification12 ms0022
org.eclipse.kapua.service.elasticsearch.client.transport4.1 sec0055
org.eclipse.kapua.service.elasticsearch.client.utils0.2 sec0033
org.eclipse.kapua.service.stream4 ms0044
org.eclipse.kapua.transport.exception48 ms002929
org.eclipse.kapua.transport.mqtt.test.message.mqtt76 ms002323
org.eclipse.kapua.transport.mqtt.test.mqtt2 ms0088
org.eclipse.kapua.transport.mqtt.test.mqtt.exception0.2 sec004343
org.eclipse.kapua.transport.utils36 ms0044