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 sec140
 JobEngineService execute job on device connect.Executing Job And Then Restarting Device4 min 10 sec140
 JobEngineService execute job on device connect.Executing Job When Device Connected After End Date And Time4 min 10 sec140
 JobEngineService execute job on device connect.Executing Job When Device Connected After End Date And Time4 min 10 sec140
 JobEngineService execute job on device connect.Executing Job When Device Connected After The Specified Start Date And Time4 min 10 sec140
 JobEngineService execute job on device connect.Executing Job When Device Connected After The Specified Start Date And Time4 min 10 sec140
 JobEngineService execute job on device connect.Executing Job When Device Connected Before End Date And Time4 min 10 sec140
 JobEngineService execute job on device connect.Executing Job When Device Connected Before End Date And Time4 min 10 sec140
 JobEngineService execute job on device connect.Executing Job When Device Connected Before The Specified Start Date And Time4 min 10 sec140
 JobEngineService execute job on device connect.Executing Job When Device Connected Before The Specified Start Date And Time4 min 10 sec140
 JobEngineService execute job on device connect.Executing Job Without Steps4 min 10 sec140
 JobEngineService execute job on device connect.Executing Job Without Steps4 min 10 sec140
 JobEngineService execute job on device connect.Start full docker environment1.3 sec140
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters72 ms140
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters72 ms140
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value4 min 10 sec140
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value4 min 10 sec140
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format4 min 10 sec140
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format4 min 10 sec140
 Trigger service tests.Adding "Cron Job" Schedule With End Date Only4 min 10 sec140
 Trigger service tests.Adding "Cron Job" Schedule With End Date Only4 min 10 sec140
 Trigger service tests.Adding "Cron Job" Schedule With End Time before Start time4 min 10 sec140
 Trigger service tests.Adding "Cron Job" Schedule With End Time before Start time4 min 10 sec140
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique End Date Parameter4 min 10 sec140
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique End Date Parameter4 min 10 sec140
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique Start Date Parameter4 min 10 sec140
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique Start Date Parameter4 min 10 sec140
 Trigger service tests.Adding "Cron Job" Schedule With Start Date Only4 min 10 sec140
 Trigger service tests.Adding "Cron Job" Schedule With Start Date Only4 min 10 sec140
 Trigger service tests.Adding "Cron Job" Schedule With the same Start and End time4 min 10 sec140
 Trigger service tests.Adding "Cron Job" Schedule With the same Start and End time4 min 10 sec140
 Trigger service tests.Adding "Cron Job" Schedule Without The Start Date Parameter4 min 10 sec140
 Trigger service tests.Adding "Cron Job" Schedule Without The Start Date Parameter4 min 10 sec140
 Trigger service tests.Adding "Device Connect" Schedule With All Valid Parameters0.89 sec140
 Trigger service tests.Adding "Device Connect" Schedule With All Valid Parameters0.91 sec140
 Trigger service tests.Adding "Device Connect" Schedule With End Date Only0.13 sec140
 Trigger service tests.Adding "Device Connect" Schedule With End Date Only0.13 sec140
 Trigger service tests.Adding "Device Connect" Schedule With End Time before Start time96 ms140
 Trigger service tests.Adding "Device Connect" Schedule With End Time before Start time96 ms140
 Trigger service tests.Adding "Device Connect" Schedule With Max Length Name91 ms140
 Trigger service tests.Adding "Device Connect" Schedule With Max Length Name91 ms140
 Trigger service tests.Adding "Device Connect" Schedule With Min Length Name84 ms140
 Trigger service tests.Adding "Device Connect" Schedule With Min Length Name84 ms140
 Trigger service tests.Adding "Device Connect" Schedule With Name Only73 ms140
 Trigger service tests.Adding "Device Connect" Schedule With Name Only73 ms140
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique End Date Parameter92 ms140
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique End Date Parameter92 ms140
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Name89 ms140
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Name89 ms140
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Start Date Parameter82 ms140
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Start Date Parameter82 ms140
 Trigger service tests.Adding "Device Connect" Schedule With Start Date Only71 ms140
 Trigger service tests.Adding "Device Connect" Schedule With Start Date Only71 ms140
 Trigger service tests.Adding "Device Connect" Schedule With the same Start and End time75 ms140
 Trigger service tests.Adding "Device Connect" Schedule With the same Start and End time75 ms140
 Trigger service tests.Adding "Device Connect" Schedule Without Name65 ms140
 Trigger service tests.Adding "Device Connect" Schedule Without Name65 ms140
 Trigger service tests.Adding "Device Connect" Schedule Without The Start Date Parameter61 ms140
 Trigger service tests.Adding "Device Connect" Schedule Without The Start Date Parameter61 ms140
 Trigger service tests.Adding "Interval Job" Schedule With All Valid Parameters59 ms140
 Trigger service tests.Adding "Interval Job" Schedule With All Valid Parameters59 ms140
 Trigger service tests.Adding "Interval Job" Schedule With End Date Only73 ms140
 Trigger service tests.Adding "Interval Job" Schedule With End Date Only73 ms140
 Trigger service tests.Adding "Interval Job" Schedule With End Time before Start time75 ms140
 Trigger service tests.Adding "Interval Job" Schedule With End Time before Start time74 ms140
 Trigger service tests.Adding "Interval Job" Schedule With Max Length Name64 ms140
 Trigger service tests.Adding "Interval Job" Schedule With Max Length Name64 ms140
 Trigger service tests.Adding "Interval Job" Schedule With Min Length Name70 ms140
 Trigger service tests.Adding "Interval Job" Schedule With Min Length Name70 ms140
 Trigger service tests.Adding "Interval Job" Schedule With Name Only72 ms140
 Trigger service tests.Adding "Interval Job" Schedule With Name Only72 ms140
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique End Date Parameter53 ms140
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique End Date Parameter53 ms140
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Name56 ms140
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Name84 ms140
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Start Date Parameter53 ms140
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Start Date Parameter53 ms140
 Trigger service tests.Adding "Interval Job" Schedule With Null Interval Number61 ms140
 Trigger service tests.Adding "Interval Job" Schedule With Null Interval Number61 ms140
 Trigger service tests.Adding "Interval Job" Schedule With Start Date Only58 ms140
 Trigger service tests.Adding "Interval Job" Schedule With Start Date Only58 ms140
 Trigger service tests.Adding "Interval Job" Schedule With the same Start and End time60 ms140
 Trigger service tests.Adding "Interval Job" Schedule With the same Start and End time80 ms140
 Trigger service tests.Adding "Interval Job" Schedule Without Interval Number71 ms140
 Trigger service tests.Adding "Interval Job" Schedule Without Interval Number71 ms140
 Trigger service tests.Adding "Interval Job" Schedule Without The Start Date Parameter83 ms140
 Trigger service tests.Adding "Interval Job" Schedule Without The Start Date Parameter83 ms140
 Trigger service tests.Adding "Interval Job" Schedule Without a Name77 ms140
 Trigger service tests.Adding "Interval Job" Schedule Without a Name77 ms140
 Trigger service tests.Deleting "Cron Schedule" Triggering4 min 10 sec140
 Trigger service tests.Deleting "Cron Schedule" Triggering4 min 10 sec140
 Trigger service tests.Deleting "Device Schedule" Triggering4 min 10 sec140
 Trigger service tests.Deleting "Device Schedule" Triggering4 min 10 sec140
 Trigger service tests.Deleting "Interval Schedule" Triggering4 min 10 sec140
 Trigger service tests.Deleting "Interval Schedule" Triggering4 min 10 sec140
 Trigger service tests.Init Security Context for all scenarios5.3 sec140
 Trigger service tests.Init Security Context for all scenarios5.3 sec140
 Trigger service tests.Interval Job" Schedule With Too Long Name74 ms140
 Trigger service tests.Interval Job" Schedule With Too Long Name76 ms140

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Device Event CRUD tests27 sec001212
Device Registry CRUD tests31 sec002626
Device Registry Connection tests18 sec001616
Device Registry Validation Tests21 sec002121
Job service CRUD tests1 min 7 sec003535
Job step definition service CRUD tests21 sec001616
JobEngineService execute job on device connect50 min130114
JobStepService CRUD tests13 sec001111
Tag Service1 min 18 sec005454
Trigger service tests1 hr 40 min860187
User Account Service39 sec002222
User Service45 sec002727