Skip to content
[Jenkins]Jenkins
log in

Test Result : (root)

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

All Failed Tests

Test NameDurationAge
 JobEngineService execute job on device connect.Executing Job And Then Restarting Device4 min 10 sec141
 JobEngineService execute job on device connect.Executing Job And Then Restarting Device4 min 10 sec141
 JobEngineService execute job on device connect.Executing Job When Device Connected After End Date And Time4 min 10 sec141
 JobEngineService execute job on device connect.Executing Job When Device Connected After End Date And Time4 min 10 sec141
 JobEngineService execute job on device connect.Executing Job When Device Connected After The Specified Start Date And Time4 min 10 sec141
 JobEngineService execute job on device connect.Executing Job When Device Connected After The Specified Start Date And Time4 min 10 sec141
 JobEngineService execute job on device connect.Executing Job When Device Connected Before End Date And Time4 min 10 sec141
 JobEngineService execute job on device connect.Executing Job When Device Connected Before End Date And Time4 min 10 sec141
 JobEngineService execute job on device connect.Executing Job When Device Connected Before The Specified Start Date And Time4 min 10 sec141
 JobEngineService execute job on device connect.Executing Job When Device Connected Before The Specified Start Date And Time4 min 10 sec141
 JobEngineService execute job on device connect.Executing Job Without Steps4 min 10 sec141
 JobEngineService execute job on device connect.Executing Job Without Steps4 min 10 sec141
 JobEngineService execute job on device connect.Start full docker environment1.2 sec141
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters47 ms141
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters47 ms141
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value4 min 10 sec141
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value4 min 10 sec141
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format4 min 10 sec141
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format4 min 10 sec141
 Trigger service tests.Adding "Cron Job" Schedule With End Date Only4 min 10 sec141
 Trigger service tests.Adding "Cron Job" Schedule With End Date Only4 min 10 sec141
 Trigger service tests.Adding "Cron Job" Schedule With End Time before Start time4 min 10 sec141
 Trigger service tests.Adding "Cron Job" Schedule With End Time before Start time4 min 10 sec141
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique End Date Parameter4 min 10 sec141
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique End Date Parameter4 min 10 sec141
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique Start Date Parameter4 min 10 sec141
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique Start Date Parameter4 min 10 sec141
 Trigger service tests.Adding "Cron Job" Schedule With Start Date Only4 min 10 sec141
 Trigger service tests.Adding "Cron Job" Schedule With Start Date Only4 min 10 sec141
 Trigger service tests.Adding "Cron Job" Schedule With the same Start and End time4 min 10 sec141
 Trigger service tests.Adding "Cron Job" Schedule With the same Start and End time4 min 10 sec141
 Trigger service tests.Adding "Cron Job" Schedule Without The Start Date Parameter4 min 10 sec141
 Trigger service tests.Adding "Cron Job" Schedule Without The Start Date Parameter4 min 10 sec141
 Trigger service tests.Adding "Device Connect" Schedule With All Valid Parameters0.78 sec141
 Trigger service tests.Adding "Device Connect" Schedule With All Valid Parameters0.78 sec141
 Trigger service tests.Adding "Device Connect" Schedule With End Date Only68 ms141
 Trigger service tests.Adding "Device Connect" Schedule With End Date Only68 ms141
 Trigger service tests.Adding "Device Connect" Schedule With End Time before Start time76 ms141
 Trigger service tests.Adding "Device Connect" Schedule With End Time before Start time76 ms141
 Trigger service tests.Adding "Device Connect" Schedule With Max Length Name64 ms141
 Trigger service tests.Adding "Device Connect" Schedule With Max Length Name65 ms141
 Trigger service tests.Adding "Device Connect" Schedule With Min Length Name79 ms141
 Trigger service tests.Adding "Device Connect" Schedule With Min Length Name80 ms141
 Trigger service tests.Adding "Device Connect" Schedule With Name Only79 ms141
 Trigger service tests.Adding "Device Connect" Schedule With Name Only80 ms141
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique End Date Parameter74 ms141
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique End Date Parameter74 ms141
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Name88 ms141
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Name89 ms141
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Start Date Parameter91 ms141
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Start Date Parameter91 ms141
 Trigger service tests.Adding "Device Connect" Schedule With Start Date Only59 ms141
 Trigger service tests.Adding "Device Connect" Schedule With Start Date Only59 ms141
 Trigger service tests.Adding "Device Connect" Schedule With the same Start and End time59 ms141
 Trigger service tests.Adding "Device Connect" Schedule With the same Start and End time59 ms141
 Trigger service tests.Adding "Device Connect" Schedule Without Name77 ms141
 Trigger service tests.Adding "Device Connect" Schedule Without Name77 ms141
 Trigger service tests.Adding "Device Connect" Schedule Without The Start Date Parameter78 ms141
 Trigger service tests.Adding "Device Connect" Schedule Without The Start Date Parameter79 ms141
 Trigger service tests.Adding "Interval Job" Schedule With All Valid Parameters69 ms141
 Trigger service tests.Adding "Interval Job" Schedule With All Valid Parameters69 ms141
 Trigger service tests.Adding "Interval Job" Schedule With End Date Only54 ms141
 Trigger service tests.Adding "Interval Job" Schedule With End Date Only54 ms141
 Trigger service tests.Adding "Interval Job" Schedule With End Time before Start time48 ms141
 Trigger service tests.Adding "Interval Job" Schedule With End Time before Start time48 ms141
 Trigger service tests.Adding "Interval Job" Schedule With Max Length Name52 ms141
 Trigger service tests.Adding "Interval Job" Schedule With Max Length Name52 ms141
 Trigger service tests.Adding "Interval Job" Schedule With Min Length Name76 ms141
 Trigger service tests.Adding "Interval Job" Schedule With Min Length Name76 ms141
 Trigger service tests.Adding "Interval Job" Schedule With Name Only59 ms141
 Trigger service tests.Adding "Interval Job" Schedule With Name Only59 ms141
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique End Date Parameter49 ms141
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique End Date Parameter49 ms141
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Name62 ms141
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Name62 ms141
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Start Date Parameter64 ms141
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Start Date Parameter64 ms141
 Trigger service tests.Adding "Interval Job" Schedule With Null Interval Number49 ms141
 Trigger service tests.Adding "Interval Job" Schedule With Null Interval Number49 ms141
 Trigger service tests.Adding "Interval Job" Schedule With Start Date Only75 ms141
 Trigger service tests.Adding "Interval Job" Schedule With Start Date Only75 ms141
 Trigger service tests.Adding "Interval Job" Schedule With the same Start and End time62 ms141
 Trigger service tests.Adding "Interval Job" Schedule With the same Start and End time62 ms141
 Trigger service tests.Adding "Interval Job" Schedule Without Interval Number61 ms141
 Trigger service tests.Adding "Interval Job" Schedule Without Interval Number61 ms141
 Trigger service tests.Adding "Interval Job" Schedule Without The Start Date Parameter50 ms141
 Trigger service tests.Adding "Interval Job" Schedule Without The Start Date Parameter50 ms141
 Trigger service tests.Adding "Interval Job" Schedule Without a Name75 ms141
 Trigger service tests.Adding "Interval Job" Schedule Without a Name75 ms141
 Trigger service tests.Deleting "Cron Schedule" Triggering4 min 10 sec141
 Trigger service tests.Deleting "Cron Schedule" Triggering4 min 10 sec141
 Trigger service tests.Deleting "Device Schedule" Triggering4 min 10 sec141
 Trigger service tests.Deleting "Device Schedule" Triggering4 min 10 sec141
 Trigger service tests.Deleting "Interval Schedule" Triggering4 min 10 sec141
 Trigger service tests.Deleting "Interval Schedule" Triggering4 min 10 sec141
 Trigger service tests.Init Security Context for all scenarios4.9 sec141
 Trigger service tests.Init Security Context for all scenarios4.9 sec141
 Trigger service tests.Interval Job" Schedule With Too Long Name67 ms141
 Trigger service tests.Interval Job" Schedule With Too Long Name66 ms141

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Device Event CRUD tests24 sec001212
Device Registry CRUD tests29 sec002626
Device Registry Connection tests16 sec001616
Device Registry Validation Tests19 sec002121
Job service CRUD tests1 min 1 sec003535
Job step definition service CRUD tests18 sec001616
JobEngineService execute job on device connect50 min130114
JobStepService CRUD tests11 sec001111
Tag Service1 min 11 sec005454
Trigger service tests1 hr 40 min860187
User Account Service36 sec002222
User Service41 sec002727