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 sec113
 JobEngineService execute job on device connect.Executing Job And Then Restarting Device4 min 10 sec113
 JobEngineService execute job on device connect.Executing Job When Device Connected After End Date And Time4 min 10 sec113
 JobEngineService execute job on device connect.Executing Job When Device Connected After End Date And Time4 min 10 sec113
 JobEngineService execute job on device connect.Executing Job When Device Connected After The Specified Start Date And Time4 min 10 sec113
 JobEngineService execute job on device connect.Executing Job When Device Connected After The Specified Start Date And Time4 min 10 sec113
 JobEngineService execute job on device connect.Executing Job When Device Connected Before End Date And Time4 min 10 sec113
 JobEngineService execute job on device connect.Executing Job When Device Connected Before End Date And Time4 min 10 sec113
 JobEngineService execute job on device connect.Executing Job When Device Connected Before The Specified Start Date And Time4 min 10 sec113
 JobEngineService execute job on device connect.Executing Job When Device Connected Before The Specified Start Date And Time4 min 10 sec113
 JobEngineService execute job on device connect.Executing Job Without Steps4 min 10 sec113
 JobEngineService execute job on device connect.Executing Job Without Steps4 min 10 sec113
 JobEngineService execute job on device connect.Start full docker environment1.8 sec113
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters67 ms113
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters66 ms113
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value4 min 10 sec113
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value4 min 10 sec113
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format4 min 10 sec113
 Trigger service tests.Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format4 min 10 sec113
 Trigger service tests.Adding "Cron Job" Schedule With End Date Only4 min 10 sec113
 Trigger service tests.Adding "Cron Job" Schedule With End Date Only4 min 10 sec113
 Trigger service tests.Adding "Cron Job" Schedule With End Time before Start time4 min 10 sec113
 Trigger service tests.Adding "Cron Job" Schedule With End Time before Start time4 min 10 sec113
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique End Date Parameter4 min 10 sec113
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique End Date Parameter4 min 10 sec113
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique Start Date Parameter4 min 10 sec113
 Trigger service tests.Adding "Cron Job" Schedule With Non-Unique Start Date Parameter4 min 10 sec113
 Trigger service tests.Adding "Cron Job" Schedule With Start Date Only4 min 10 sec113
 Trigger service tests.Adding "Cron Job" Schedule With Start Date Only4 min 10 sec113
 Trigger service tests.Adding "Cron Job" Schedule With the same Start and End time4 min 10 sec113
 Trigger service tests.Adding "Cron Job" Schedule With the same Start and End time4 min 10 sec113
 Trigger service tests.Adding "Cron Job" Schedule Without The Start Date Parameter4 min 10 sec113
 Trigger service tests.Adding "Cron Job" Schedule Without The Start Date Parameter4 min 10 sec113
 Trigger service tests.Adding "Device Connect" Schedule With All Valid Parameters0.86 sec113
 Trigger service tests.Adding "Device Connect" Schedule With All Valid Parameters0.86 sec113
 Trigger service tests.Adding "Device Connect" Schedule With End Date Only55 ms113
 Trigger service tests.Adding "Device Connect" Schedule With End Date Only55 ms113
 Trigger service tests.Adding "Device Connect" Schedule With End Time before Start time69 ms113
 Trigger service tests.Adding "Device Connect" Schedule With End Time before Start time69 ms113
 Trigger service tests.Adding "Device Connect" Schedule With Max Length Name66 ms113
 Trigger service tests.Adding "Device Connect" Schedule With Max Length Name65 ms113
 Trigger service tests.Adding "Device Connect" Schedule With Min Length Name85 ms113
 Trigger service tests.Adding "Device Connect" Schedule With Min Length Name84 ms113
 Trigger service tests.Adding "Device Connect" Schedule With Name Only79 ms113
 Trigger service tests.Adding "Device Connect" Schedule With Name Only80 ms113
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique End Date Parameter73 ms113
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique End Date Parameter73 ms113
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Name90 ms113
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Name69 ms113
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Start Date Parameter57 ms113
 Trigger service tests.Adding "Device Connect" Schedule With Non-Unique Start Date Parameter58 ms113
 Trigger service tests.Adding "Device Connect" Schedule With Start Date Only69 ms113
 Trigger service tests.Adding "Device Connect" Schedule With Start Date Only69 ms113
 Trigger service tests.Adding "Device Connect" Schedule With the same Start and End time66 ms113
 Trigger service tests.Adding "Device Connect" Schedule With the same Start and End time66 ms113
 Trigger service tests.Adding "Device Connect" Schedule Without Name81 ms113
 Trigger service tests.Adding "Device Connect" Schedule Without Name81 ms113
 Trigger service tests.Adding "Device Connect" Schedule Without The Start Date Parameter68 ms113
 Trigger service tests.Adding "Device Connect" Schedule Without The Start Date Parameter68 ms113
 Trigger service tests.Adding "Interval Job" Schedule With All Valid Parameters58 ms113
 Trigger service tests.Adding "Interval Job" Schedule With All Valid Parameters58 ms113
 Trigger service tests.Adding "Interval Job" Schedule With End Date Only60 ms113
 Trigger service tests.Adding "Interval Job" Schedule With End Date Only60 ms113
 Trigger service tests.Adding "Interval Job" Schedule With End Time before Start time60 ms113
 Trigger service tests.Adding "Interval Job" Schedule With End Time before Start time47 ms113
 Trigger service tests.Adding "Interval Job" Schedule With Max Length Name67 ms113
 Trigger service tests.Adding "Interval Job" Schedule With Max Length Name66 ms113
 Trigger service tests.Adding "Interval Job" Schedule With Min Length Name52 ms113
 Trigger service tests.Adding "Interval Job" Schedule With Min Length Name52 ms113
 Trigger service tests.Adding "Interval Job" Schedule With Name Only66 ms113
 Trigger service tests.Adding "Interval Job" Schedule With Name Only67 ms113
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique End Date Parameter49 ms113
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique End Date Parameter49 ms113
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Name51 ms113
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Name51 ms113
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Start Date Parameter54 ms113
 Trigger service tests.Adding "Interval Job" Schedule With Non-Unique Start Date Parameter54 ms113
 Trigger service tests.Adding "Interval Job" Schedule With Null Interval Number64 ms113
 Trigger service tests.Adding "Interval Job" Schedule With Null Interval Number63 ms113
 Trigger service tests.Adding "Interval Job" Schedule With Start Date Only62 ms113
 Trigger service tests.Adding "Interval Job" Schedule With Start Date Only62 ms113
 Trigger service tests.Adding "Interval Job" Schedule With the same Start and End time46 ms113
 Trigger service tests.Adding "Interval Job" Schedule With the same Start and End time46 ms113
 Trigger service tests.Adding "Interval Job" Schedule Without Interval Number47 ms113
 Trigger service tests.Adding "Interval Job" Schedule Without Interval Number47 ms113
 Trigger service tests.Adding "Interval Job" Schedule Without The Start Date Parameter58 ms113
 Trigger service tests.Adding "Interval Job" Schedule Without The Start Date Parameter58 ms113
 Trigger service tests.Adding "Interval Job" Schedule Without a Name76 ms113
 Trigger service tests.Adding "Interval Job" Schedule Without a Name76 ms113
 Trigger service tests.Deleting "Cron Schedule" Triggering4 min 10 sec113
 Trigger service tests.Deleting "Cron Schedule" Triggering4 min 10 sec113
 Trigger service tests.Deleting "Device Schedule" Triggering4 min 10 sec113
 Trigger service tests.Deleting "Device Schedule" Triggering4 min 10 sec113
 Trigger service tests.Deleting "Interval Schedule" Triggering4 min 10 sec113
 Trigger service tests.Deleting "Interval Schedule" Triggering4 min 10 sec113
 Trigger service tests.Init Security Context for all scenarios6 sec113
 Trigger service tests.Init Security Context for all scenarios6 sec113
 Trigger service tests.Interval Job" Schedule With Too Long Name65 ms113
 Trigger service tests.Interval Job" Schedule With Too Long Name65 ms113

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 1 sec003535
Job step definition service CRUD tests19 sec001616
JobEngineService execute job on device connect50 min130114
JobStepService CRUD tests12 sec001111
Tag Service1 min 11 sec005454
Trigger service tests1 hr 40 min860187
User Account Service35 sec002222
User Service39 sec002727