Skip to content

Test Result

99 failures (-23) , 5 skipped (-1356)
2,438 tests (-2742)
Took 1 hr 23 min.

All Failed Tests

Test NameDurationAge
 JobEngineService execute job on device connect.Start full docker environment1.6 sec108
 JobEngineService execute job on device connect.Executing Job When Device Connected After The Specified Start Date And Time4 min 10 sec108
 JobEngineService execute job on device connect.Executing Job When Device Connected After The Specified Start Date And Time4 min 10 sec108
 JobEngineService execute job on device connect.Executing Job When Device Connected Before The Specified Start Date And Time4 min 10 sec108
 JobEngineService execute job on device connect.Executing Job When Device Connected Before The Specified Start Date And Time4 min 10 sec108
 JobEngineService execute job on device connect.Executing Job When Device Connected Before End Date And Time4 min 10 sec108
 JobEngineService execute job on device connect.Executing Job When Device Connected Before End Date And Time4 min 10 sec108
 JobEngineService execute job on device connect.Executing Job When Device Connected After End Date And Time4 min 10 sec108
 JobEngineService execute job on device connect.Executing Job When Device Connected After End Date And Time4 min 10 sec108
 JobEngineService execute job on device connect.Executing Job And Then Restarting Device4 min 10 sec108
 JobEngineService execute job on device connect.Executing Job And Then Restarting Device4 min 10 sec108
 JobEngineService execute job on device connect.Executing Job Without Steps4 min 10 sec108
 JobEngineService execute job on device connect.Executing Job Without Steps4 min 10 sec108
 Trigger service tests.Init Security Context for all scenarios5.8 sec108
 Trigger service tests.Init Security Context for all scenarios5.8 sec108
 Trigger service tests.Adding "Device Connect" Schedule With All Valid Parameters0.94 sec108
 Trigger service tests.Adding "Device Connect" Schedule With All Valid Parameters0.94 sec108
 Trigger service tests.Adding "Device Connect" Schedule Without Name89 ms108
 Trigger service tests.Adding "Device Connect" Schedule Without Name89 ms108
 Trigger service tests.Adding "Device Connect" Schedule With Name Only88 ms108
 Trigger service tests.Adding "Device Connect" Schedule With Name Only88 ms108
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Name97 ms108
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Name97 ms108
 Trigger service tests.Adding "Device Connect" Schedule With Max Length Name0.1 sec108
 Trigger service tests.Adding "Device Connect" Schedule With Max Length Name0.1 sec108
 Trigger service tests.Adding "Device Connect" Schedule With Min Length Name78 ms108
 Trigger service tests.Adding "Device Connect" Schedule With Min Length Name78 ms108
 Trigger service tests.Adding "Device Connect" Schedule Without The Start Date Parameter0.11 sec108
 Trigger service tests.Adding "Device Connect" Schedule Without The Start Date Parameter0.11 sec108
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Start Date Parameter95 ms108
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Start Date Parameter96 ms108
 Trigger service tests.Adding "Device Connect" Schedule With Start Date Only83 ms108
 Trigger service tests.Adding "Device Connect" Schedule With Start Date Only84 ms108
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique End Date Parameter92 ms108
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique End Date Parameter92 ms108
 Trigger service tests.Adding "Device Connect" Schedule With End Date Only91 ms108
 Trigger service tests.Adding "Device Connect" Schedule With End Date Only92 ms108
 Trigger service tests.Adding "Device Connect" Schedule With End Time before Start time70 ms108
 Trigger service tests.Adding "Device Connect" Schedule With End Time before Start time70 ms108
 Trigger service tests.Adding "Device Connect" Schedule With the same Start and End time88 ms108
 Trigger service tests.Adding "Device Connect" Schedule With the same Start and End time88 ms108
 Trigger service tests.Adding "Interval Job" Schedule With All Valid Parameters80 ms108
 Trigger service tests.Adding "Interval Job" Schedule With All Valid Parameters81 ms108
 Trigger service tests.Adding "Interval Job" Schedule Without a Name80 ms108
 Trigger service tests.Adding "Interval Job" Schedule Without a Name80 ms108
 Trigger service tests.Adding "Interval Job" Schedule With Name Only81 ms108
 Trigger service tests.Adding "Interval Job" Schedule With Name Only81 ms108
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Name60 ms108
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Name60 ms108
 Trigger service tests.Adding "Interval Job" Schedule With Max Length Name77 ms108
 Trigger service tests.Adding "Interval Job" Schedule With Max Length Name77 ms108
 Trigger service tests.Interval Job" Schedule With Too Long Name77 ms108
 Trigger service tests.Interval Job" Schedule With Too Long Name78 ms108
 Trigger service tests.Adding "Interval Job" Schedule With Min Length Name81 ms108
 Trigger service tests.Adding "Interval Job" Schedule With Min Length Name81 ms108
 Trigger service tests.Adding "Interval Job" Schedule Without The Start Date Parameter57 ms108
 Trigger service tests.Adding "Interval Job" Schedule Without The Start Date Parameter57 ms108
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Start Date Parameter81 ms108
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Start Date Parameter82 ms108
 Trigger service tests.Adding "Interval Job" Schedule With Start Date Only0.1 sec108
 Trigger service tests.Adding "Interval Job" Schedule With Start Date Only0.1 sec108
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique End Date Parameter68 ms108
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique End Date Parameter68 ms108
 Trigger service tests.Adding "Interval Job" Schedule With End Date Only56 ms108
 Trigger service tests.Adding "Interval Job" Schedule With End Date Only56 ms108
 Trigger service tests.Adding "Interval Job" Schedule With End Time before Start time80 ms108
 Trigger service tests.Adding "Interval Job" Schedule With End Time before Start time80 ms108
 Trigger service tests.Adding "Interval Job" Schedule With the same Start and End time72 ms108
 Trigger service tests.Adding "Interval Job" Schedule With the same Start and End time72 ms108
 Trigger service tests.Adding "Interval Job" Schedule With Null Interval Number75 ms108
 Trigger service tests.Adding "Interval Job" Schedule With Null Interval Number75 ms108
 Trigger service tests.Adding "Interval Job" Schedule Without Interval Number52 ms108
 Trigger service tests.Adding "Interval Job" Schedule Without Interval Number52 ms108
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters63 ms108
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters63 ms108
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format4 min 10 sec108
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format4 min 10 sec108
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value4 min 10 sec108
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value4 min 10 sec108
 Trigger service tests.Adding "Cron Job" Schedule Without The Start Date Parameter4 min 10 sec108
 Trigger service tests.Adding "Cron Job" Schedule Without The Start Date Parameter4 min 10 sec108
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique Start Date Parameter4 min 10 sec108
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique Start Date Parameter4 min 10 sec108
 Trigger service tests.Adding "Cron Job" Schedule With Start Date Only4 min 10 sec108
 Trigger service tests.Adding "Cron Job" Schedule With Start Date Only4 min 10 sec108
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique End Date Parameter4 min 10 sec108
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique End Date Parameter4 min 10 sec108
 Trigger service tests.Adding "Cron Job" Schedule With End Date Only4 min 10 sec108
 Trigger service tests.Adding "Cron Job" Schedule With End Date Only4 min 10 sec108
 Trigger service tests.Adding "Cron Job" Schedule With End Time before Start time4 min 10 sec108
 Trigger service tests.Adding "Cron Job" Schedule With End Time before Start time4 min 10 sec108
 Trigger service tests.Adding "Cron Job" Schedule With the same Start and End time4 min 10 sec108
 Trigger service tests.Adding "Cron Job" Schedule With the same Start and End time4 min 10 sec108
 Trigger service tests.Deleting "Interval Schedule" Triggering4 min 10 sec108
 Trigger service tests.Deleting "Interval Schedule" Triggering4 min 10 sec108
 Trigger service tests.Deleting "Cron Schedule" Triggering4 min 10 sec108
 Trigger service tests.Deleting "Cron Schedule" Triggering4 min 10 sec108
 Trigger service tests.Deleting "Device Schedule" Triggering4 min 10 sec108
 Trigger service tests.Deleting "Device Schedule" Triggering4 min 10 sec108

All Tests

PackageDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
(root)2 hr 37 min99-230-1349242-3111341-4483
org.eclipse.kapua0.27 sec00102+99102+99
org.eclipse.kapua.app.api.core0.24 sec0031+3131+31
org.eclipse.kapua.app.api.core.auth0.5 sec003+33+3
org.eclipse.kapua.app.api.core.exception10 ms0010+1010+10
org.eclipse.kapua.app.api.core.model73 ms0021+2121+21
org.eclipse.kapua.app.api.core.model.data0.14 sec0038+3838+38
org.eclipse.kapua.app.api.core.model.device.management0.12 sec0030+3030+30
org.eclipse.kapua.app.api.core.model.message51 ms007+77+7
org.eclipse.kapua.app.api.core.resources1 ms005+55+5
org.eclipse.kapua.app.api.core.settings0 ms001+11+1
org.eclipse.kapua.app.api.web9.3 sec0013+1313+13
org.eclipse.kapua.broker.client.protocol0.44 sec0021+2121+21
org.eclipse.kapua.commons.about3 ms0012+1112+11
org.eclipse.kapua.commons.cache0.45 sec008+88+8
org.eclipse.kapua.commons.configuration3 sec00132+131132+131
org.eclipse.kapua.commons.configuration.metatype28 ms00134+115134+115
org.eclipse.kapua.commons.crypto0 ms009+99+9
org.eclipse.kapua.commons.event9 ms0036+3636+36
org.eclipse.kapua.commons.liquibase1.2 sec0044
org.eclipse.kapua.commons.metric13 ms003+13+1
org.eclipse.kapua.commons.model44 ms0044+3644+36
org.eclipse.kapua.commons.model.id0.17 sec0025+2425+24
org.eclipse.kapua.commons.model.query62 ms00124+124124+124
org.eclipse.kapua.commons.model.query.predicate0 ms0029+2929+29
org.eclipse.kapua.commons.rest.model.errors0.36 sec0023+2323+23
org.eclipse.kapua.commons.security3 sec0033
org.eclipse.kapua.commons.service.event.store.internal24 ms0023+2323+23
org.eclipse.kapua.commons.service.internal.cache0 ms005+55+5
org.eclipse.kapua.commons.service.internal.cache.dummy0 ms0055+5555+55
org.eclipse.kapua.commons.setting18 ms00101+97101+97
org.eclipse.kapua.commons.setting.system0 ms004+44+4
org.eclipse.kapua.commons.util1.8 sec00169+131169+131
org.eclipse.kapua.commons.util.log0.98 sec0027+2727+27
org.eclipse.kapua.commons.util.xml0.56 sec0015+615+6
org.eclipse.kapua.entity0 ms002+22+2
org.eclipse.kapua.event3 ms0016+1616+16
org.eclipse.kapua.integration.misc11 sec00112+112112+112
org.eclipse.kapua.job.engine.exception0.19 sec0012+1212+12
org.eclipse.kapua.kura.simulator.main.simulation5.7 sec001313
org.eclipse.kapua.locator7 ms0010+1010+10
org.eclipse.kapua.locator.internal1.9 sec03+114+417+5
org.eclipse.kapua.message.internal0.53 sec022628
org.eclipse.kapua.message.internal.device.data1 ms0033
org.eclipse.kapua.message.internal.device.lifecycle1.2 sec0017-417-4
org.eclipse.kapua.message.internal.xml1.2 sec001111
org.eclipse.kapua.model0 ms001+11+1
org.eclipse.kapua.model.domain0 ms002+22+2
org.eclipse.kapua.model.id0 ms004+44+4
org.eclipse.kapua.model.query0 ms002+22+2
org.eclipse.kapua.model.type1 ms0017+1717+17
org.eclipse.kapua.model.xml0.16 sec0019+1919+19
org.eclipse.kapua.model.xml.adapters0.4 sec002+22+2
org.eclipse.kapua.service.account.xml3 sec005+55+5
org.eclipse.kapua.service.authentication.credential.mfa.shiro29 ms0032+3232+32
org.eclipse.kapua.service.authentication.credential.shiro32 ms0030+3030+30
org.eclipse.kapua.service.authentication.exception0.19 sec005+55+5
org.eclipse.kapua.service.authentication.shiro1 ms0035+3535+35
org.eclipse.kapua.service.authentication.shiro.exceptions81 ms0014+1214+12
org.eclipse.kapua.service.authentication.shiro.mfa21 sec0012+1212+12
org.eclipse.kapua.service.authentication.shiro.realm1.2 sec0051+5151+51
org.eclipse.kapua.service.authentication.shiro.registration20 ms006+66+6
org.eclipse.kapua.service.authentication.shiro.setting0 ms002+22+2
org.eclipse.kapua.service.authentication.shiro.utils4.3 sec0016+1616+16
org.eclipse.kapua.service.authentication.token.shiro38 ms0037+3737+37
org.eclipse.kapua.service.authorization.access.shiro0.42 sec0078+7878+78
org.eclipse.kapua.service.authorization.domain.shiro30 ms0041+4141+41
org.eclipse.kapua.service.authorization.exception0.63 sec007+77+7
org.eclipse.kapua.service.authorization.group.shiro24 ms0025+2525+25
org.eclipse.kapua.service.authorization.role.shiro0.51 sec0034+3434+34
org.eclipse.kapua.service.authorization.shiro36 ms005-145-14
org.eclipse.kapua.service.authorization.shiro.setting0 ms001+11+1
org.eclipse.kapua.service.config5 ms0013+1313+13
org.eclipse.kapua.service.device.call.exception0.15 sec003+33+3
org.eclipse.kapua.service.device.management.commons.message.notification12 ms0022
org.eclipse.kapua.service.elasticsearch.client.utils0.18 sec003+33+3
org.eclipse.kapua.service.security99 ms0022+2222+22
org.eclipse.kapua.service.storable.exception48 ms0010+1010+10
org.eclipse.kapua.service.tag.internal0.37 sec001+11+1
org.eclipse.kapua.transport.exception0.14 sec005+55+5
org.eclipse.kapua.transport.mqtt.test.message.mqtt0.38 sec0023+2323+23
org.eclipse.kapua.transport.mqtt.test.mqtt1 ms008+88+8
org.eclipse.kapua.transport.mqtt.test.mqtt.exception25 ms0012+1212+12
org.eclipse.kapua.transport.utils0.21 sec004+44+4