Skip to content
[Jenkins]Jenkins
log in

Test Result : (root)

99 failures (±0)
341 tests (±0)
Took 2 hr 36 min.

All Failed Tests

Test NameDurationAge
 JobEngineService execute job on device connect.Executing Job And Then Restarting Device4 min 10 sec131
 JobEngineService execute job on device connect.Executing Job And Then Restarting Device4 min 10 sec131
 JobEngineService execute job on device connect.Executing Job When Device Connected After End Date And Time4 min 10 sec131
 JobEngineService execute job on device connect.Executing Job When Device Connected After End Date And Time4 min 10 sec131
 JobEngineService execute job on device connect.Executing Job When Device Connected After The Specified Start Date And Time4 min 10 sec131
 JobEngineService execute job on device connect.Executing Job When Device Connected After The Specified Start Date And Time4 min 10 sec131
 JobEngineService execute job on device connect.Executing Job When Device Connected Before End Date And Time4 min 10 sec131
 JobEngineService execute job on device connect.Executing Job When Device Connected Before End Date And Time4 min 10 sec131
 JobEngineService execute job on device connect.Executing Job When Device Connected Before The Specified Start Date And Time4 min 10 sec131
 JobEngineService execute job on device connect.Executing Job When Device Connected Before The Specified Start Date And Time4 min 10 sec131
 JobEngineService execute job on device connect.Executing Job Without Steps4 min 10 sec131
 JobEngineService execute job on device connect.Executing Job Without Steps4 min 10 sec131
 JobEngineService execute job on device connect.Start full docker environment1.3 sec131
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters62 ms131
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters50 ms131
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value4 min 10 sec131
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value4 min 10 sec131
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format4 min 10 sec131
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format4 min 10 sec131
 Trigger service tests.Adding "Cron Job" Schedule With End Date Only4 min 10 sec131
 Trigger service tests.Adding "Cron Job" Schedule With End Date Only4 min 10 sec131
 Trigger service tests.Adding "Cron Job" Schedule With End Time before Start time4 min 10 sec131
 Trigger service tests.Adding "Cron Job" Schedule With End Time before Start time4 min 10 sec131
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique End Date Parameter4 min 10 sec131
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique End Date Parameter4 min 10 sec131
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique Start Date Parameter4 min 10 sec131
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique Start Date Parameter4 min 10 sec131
 Trigger service tests.Adding "Cron Job" Schedule With Start Date Only4 min 10 sec131
 Trigger service tests.Adding "Cron Job" Schedule With Start Date Only4 min 10 sec131
 Trigger service tests.Adding "Cron Job" Schedule With the same Start and End time4 min 10 sec131
 Trigger service tests.Adding "Cron Job" Schedule With the same Start and End time4 min 10 sec131
 Trigger service tests.Adding "Cron Job" Schedule Without The Start Date Parameter4 min 10 sec131
 Trigger service tests.Adding "Cron Job" Schedule Without The Start Date Parameter4 min 10 sec131
 Trigger service tests.Adding "Device Connect" Schedule With All Valid Parameters0.89 sec131
 Trigger service tests.Adding "Device Connect" Schedule With All Valid Parameters0.89 sec131
 Trigger service tests.Adding "Device Connect" Schedule With End Date Only0.1 sec131
 Trigger service tests.Adding "Device Connect" Schedule With End Date Only0.1 sec131
 Trigger service tests.Adding "Device Connect" Schedule With End Time before Start time74 ms131
 Trigger service tests.Adding "Device Connect" Schedule With End Time before Start time74 ms131
 Trigger service tests.Adding "Device Connect" Schedule With Max Length Name64 ms131
 Trigger service tests.Adding "Device Connect" Schedule With Max Length Name64 ms131
 Trigger service tests.Adding "Device Connect" Schedule With Min Length Name99 ms131
 Trigger service tests.Adding "Device Connect" Schedule With Min Length Name99 ms131
 Trigger service tests.Adding "Device Connect" Schedule With Name Only83 ms131
 Trigger service tests.Adding "Device Connect" Schedule With Name Only83 ms131
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique End Date Parameter66 ms131
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique End Date Parameter66 ms131
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Name94 ms131
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Name94 ms131
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Start Date Parameter73 ms131
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Start Date Parameter72 ms131
 Trigger service tests.Adding "Device Connect" Schedule With Start Date Only80 ms131
 Trigger service tests.Adding "Device Connect" Schedule With Start Date Only80 ms131
 Trigger service tests.Adding "Device Connect" Schedule With the same Start and End time72 ms131
 Trigger service tests.Adding "Device Connect" Schedule With the same Start and End time73 ms131
 Trigger service tests.Adding "Device Connect" Schedule Without Name89 ms131
 Trigger service tests.Adding "Device Connect" Schedule Without Name89 ms131
 Trigger service tests.Adding "Device Connect" Schedule Without The Start Date Parameter84 ms131
 Trigger service tests.Adding "Device Connect" Schedule Without The Start Date Parameter84 ms131
 Trigger service tests.Adding "Interval Job" Schedule With All Valid Parameters78 ms131
 Trigger service tests.Adding "Interval Job" Schedule With All Valid Parameters63 ms131
 Trigger service tests.Adding "Interval Job" Schedule With End Date Only50 ms131
 Trigger service tests.Adding "Interval Job" Schedule With End Date Only50 ms131
 Trigger service tests.Adding "Interval Job" Schedule With End Time before Start time61 ms131
 Trigger service tests.Adding "Interval Job" Schedule With End Time before Start time61 ms131
 Trigger service tests.Adding "Interval Job" Schedule With Max Length Name53 ms131
 Trigger service tests.Adding "Interval Job" Schedule With Max Length Name53 ms131
 Trigger service tests.Adding "Interval Job" Schedule With Min Length Name67 ms131
 Trigger service tests.Adding "Interval Job" Schedule With Min Length Name67 ms131
 Trigger service tests.Adding "Interval Job" Schedule With Name Only58 ms131
 Trigger service tests.Adding "Interval Job" Schedule With Name Only58 ms131
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique End Date Parameter70 ms131
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique End Date Parameter70 ms131
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Name63 ms131
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Name63 ms131
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Start Date Parameter0.13 sec131
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Start Date Parameter0.13 sec131
 Trigger service tests.Adding "Interval Job" Schedule With Null Interval Number68 ms131
 Trigger service tests.Adding "Interval Job" Schedule With Null Interval Number68 ms131
 Trigger service tests.Adding "Interval Job" Schedule With Start Date Only95 ms131
 Trigger service tests.Adding "Interval Job" Schedule With Start Date Only95 ms131
 Trigger service tests.Adding "Interval Job" Schedule With the same Start and End time51 ms131
 Trigger service tests.Adding "Interval Job" Schedule With the same Start and End time51 ms131
 Trigger service tests.Adding "Interval Job" Schedule Without Interval Number65 ms131
 Trigger service tests.Adding "Interval Job" Schedule Without Interval Number51 ms131
 Trigger service tests.Adding "Interval Job" Schedule Without The Start Date Parameter90 ms131
 Trigger service tests.Adding "Interval Job" Schedule Without The Start Date Parameter90 ms131
 Trigger service tests.Adding "Interval Job" Schedule Without a Name79 ms131
 Trigger service tests.Adding "Interval Job" Schedule Without a Name79 ms131
 Trigger service tests.Deleting "Cron Schedule" Triggering4 min 10 sec131
 Trigger service tests.Deleting "Cron Schedule" Triggering4 min 10 sec131
 Trigger service tests.Deleting "Device Schedule" Triggering4 min 10 sec131
 Trigger service tests.Deleting "Device Schedule" Triggering4 min 10 sec131
 Trigger service tests.Deleting "Interval Schedule" Triggering4 min 10 sec131
 Trigger service tests.Deleting "Interval Schedule" Triggering4 min 10 sec131
 Trigger service tests.Init Security Context for all scenarios5.3 sec131
 Trigger service tests.Init Security Context for all scenarios5.3 sec131
 Trigger service tests.Interval Job" Schedule With Too Long Name70 ms131
 Trigger service tests.Interval Job" Schedule With Too Long Name69 ms131

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Device Event CRUD tests25 sec001212
Device Registry CRUD tests30 sec002626
Device Registry Connection tests16 sec001616
Device Registry Validation Tests19 sec002121
Job service CRUD tests1 min 5 sec003535
Job step definition service CRUD tests20 sec001616
JobEngineService execute job on device connect50 min130114
JobStepService CRUD tests12 sec001111
Tag Service1 min 15 sec005454
Trigger service tests1 hr 40 min860187
User Account Service37 sec002222
User Service42 sec002727