Se agrego otro escenario donde se verifica la duplicidad en los post de los features
This commit is contained in:
@@ -37,3 +37,31 @@ Scenario Outline: List assignees of an activity with bad parameters
|
||||
| Asignando un usuario con type inexistente | 4224292655297723eb98691001100052 | 65496814252977243d57684076211485 | 69191356252cda41acde328048794164 | department |
|
||||
|
||||
|
||||
Scenario Outline: List assignees of an activity using different filters
|
||||
Given I request "project/4224292655297723eb98691001100052/activity/65496814252977243d57684076211485/adhoc-available-assignee?filter=<filter>&start=<start>&limit=<limit>"
|
||||
Then the response status code should be <http_code>
|
||||
And the response charset is "UTF-8"
|
||||
And the content type is "application/json"
|
||||
And the type is "<type>"
|
||||
And the response has <records> records
|
||||
|
||||
Examples:
|
||||
| test_description | filter | start | limit | records | http_code | type |
|
||||
| lowercase | admin | 0 | 1 | 1 | 200 | array |
|
||||
| uppercase | ADMIN | 0 | 1 | 1 | 200 | array |
|
||||
| limit=3 | a | 0 | 3 | 3 | 200 | array |
|
||||
| limit and start | a | 1 | 2 | 2 | 200 | array |
|
||||
| high number for start | a | 1000 | 1 | 0 | 200 | array |
|
||||
| high number for start | a | 1000 | 0 | 0 | 200 | array |
|
||||
| empty result | xyz | 0 | 0 | 0 | 200 | array |
|
||||
| empty string | | 0 | 10000 | 82 | 200 | array |
|
||||
| empty string | | 1 | 2 | 2 | 200 | array |
|
||||
| invalid start | a | b | c | 0 | 400 | string|
|
||||
| invalid limit | a | 0 | c | 0 | 400 | string|
|
||||
| search 0 | 0 | 0 | 0 | 0 | 200 | array |
|
||||
| search 0 | 0 | 0 | 100 | 0 | 200 | array |
|
||||
| negative numbers | a | -10 | -20 | 0 | 400 | string|
|
||||
| real numbers | a | 0.0 | 1.0 | 1 | 200 | string|
|
||||
| real numbers | a | 0.0 | 0.0 | 0 | 200 | string|
|
||||
| real numbers | a | 0.1 | 1.4599 | 0 | 400 | string|
|
||||
| real numbers | a | 1.5 | 1.4599 | 0 | 400 | string|
|
||||
|
||||
@@ -49,24 +49,25 @@ Scenario Outline: Assign a user or group to an activity (Field validation)
|
||||
And the response has <records> records
|
||||
|
||||
Examples:
|
||||
| test_description | filter | start | limit | records | http_code | type |
|
||||
| lowercase | admin | 0 | 1 | 1 | 200 | array |
|
||||
| uppercase | ADMIN | 0 | 1 | 1 | 200 | array |
|
||||
| limit=3 | a | 0 | 3 | 3 | 200 | array |
|
||||
| limit and start | a | 1 | 2 | 2 | 200 | array |
|
||||
| high number for start | a | 1000 | 1 | 0 | 200 | array |
|
||||
| high number for start | a | 1000 | 0 | 0 | 200 | array |
|
||||
| empty result | xyz | 0 | 0 | 0 | 200 | array |
|
||||
| empty string | | 0 | 10000 | 4 | 200 | array |
|
||||
| empty string | | 1 | 2 | 2 | 200 | array |
|
||||
| invalid start | a | b | c | 0 | 400 | string|
|
||||
| invalid limit | a | 0 | c | 0 | 400 | string|
|
||||
| search 0 | 0 | 0 | 0 | 0 | 200 | array |
|
||||
| search 0 | 0 | 0 | 100 | 0 | 200 | array |
|
||||
| negative numbers | a | -10 | -20 | 0 | 400 | string|
|
||||
| real numbers | a | 0.0 | 1.0 | 1 | 200 | string|
|
||||
| real numbers | a | 0.0 | 0.0 | 0 | 200 | string|
|
||||
| real numbers | a | 0.1 | 1.4599 | 0 | 400 | string|
|
||||
| real numbers | a | 1.5 | 1.4599 | 0 | 400 | string|
|
||||
|
||||
| test_description | filter | start | limit | records | http_code | type |
|
||||
| lowercase | admin | 0 | 1 | 1 | 200 | array |
|
||||
| uppercase | ADMIN | 0 | 1 | 1 | 200 | array |
|
||||
| limit=3 | a | 0 | 3 | 3 | 200 | array |
|
||||
| limit and start | a | 1 | 2 | 2 | 200 | array |
|
||||
| high number for start | a | 1000 | 1 | 0 | 200 | array |
|
||||
| high number for start | a | 1000 | 0 | 0 | 200 | array |
|
||||
| empty result | xyz | 0 | 0 | 0 | 200 | array |
|
||||
| empty string | | 0 | 10000 | 4 | 200 | array |
|
||||
| empty string | | 1 | 2 | 2 | 200 | array |
|
||||
| invalid start | a | b | c | 0 | 400 | string |
|
||||
| invalid limit | a | 0 | c | 0 | 400 | string |
|
||||
| search 0 | 0 | 0 | 0 | 0 | 200 | array |
|
||||
| search 0 | 0 | 0 | 100 | 0 | 200 | array |
|
||||
| negative numbers | a | -10 | -20 | 0 | 400 | string |
|
||||
| real numbers | a | 0.0 | 1.0 | 1 | 200 | string |
|
||||
| real numbers | a | 0.0 | 0.0 | 0 | 200 | string |
|
||||
| real numbers | a | 0.1 | 1.4599 | 0 | 400 | string |
|
||||
| real numbers | a | 1.5 | 1.4599 | 0 | 400 | string |
|
||||
|
||||
|
||||
|
||||
@@ -37,7 +37,7 @@ Feature: Case Scheduler Main Tests
|
||||
}
|
||||
"""
|
||||
And I request "project/1265557095225ff5c688f46031700471/case-scheduler"
|
||||
Then the response status code should be 201
|
||||
Then the response status code should be <error_code>
|
||||
And the response charset is "UTF-8"
|
||||
And the content type is "application/json"
|
||||
And the type is "object"
|
||||
@@ -46,21 +46,46 @@ Feature: Case Scheduler Main Tests
|
||||
|
||||
Examples:
|
||||
|
||||
| test_description | sch_uid_number | sch_del_user_name | sch_del_user_pass | tas_uid | sch_name | sch_option | sch_start_date | sch_end_date | sch_start_time | sch_week_days | sch_start_day | sch_start_day_opt_1 | sch_months | sch_start_day_opt_2 | sch_repeat_every |
|
||||
| Create with Daily | 1 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Daily 123@#$ | 1 | 2014-01-30 | 2014-02-20 | 12:00 | | | | | | |
|
||||
| Create with Weekly, sch_week_days=monday | 2 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Weekly monday 345%$# | 2 | 2014-02-20 | 2014-03-20 | 08:00 | 1 | | | | | |
|
||||
| Create with Weekly, sch_week_days=tuesday, wednesday, thursday, friday, saturday, sunday | 3 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Weekly 345%$# | 2 | 2014-02-20 | 2014-03-20 | 08:00 | 2\|3\|4\|5\|6\|7 | | | | | |
|
||||
| Create with Monthly and day of month, day of month=1, of the month(s)=3,4 | 4 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Monthly 567&^% 1 | 3 | 2014-03-21 | 2014-04-18 | 18:00 | | 1 | 15 | 3\|4 | | |
|
||||
| Create with Monthly and day of month, day of month=1, of the month=1,2,5,6,7,8,9,10,11,12 | 5 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Monthly 567&^% 2 | 3 | 2014-03-21 | 2014-04-18 | 18:00 | | 1 | 15 | 1\|2\|5\|6\|7\|8\|9\|10\|11\|12 | | |
|
||||
| Create with Monthly and the day=first and Monday | 6 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Monthly 567&^% 3 | 3 | 2014-03-21 | 2014-04-18 | 18:00 | | 2 | | 3\|4\|5 | 1\|7 | |
|
||||
| Create with Monthly and the day=second and Saturday | 7 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Monthly 567&^% 4 | 3 | 2014-03-21 | 2014-04-18 | 18:00 | | 2 | | 3\|4\|5 | 2\|6 | |
|
||||
| Create with Monthly and the day=Third and Friday | 8 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Monthly 567&^% 5 | 3 | 2014-03-21 | 2014-04-18 | 18:00 | | 2 | | 3\|4\|5 | 3\|5 | |
|
||||
| Create with Monthly and the day=second and Thursday | 9 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Monthly 567&^% 6 | 3 | 2014-03-21 | 2014-04-18 | 18:00 | | 2 | | 3\|4\|5 | 2\|4 | |
|
||||
| Create with Monthly and the day=last and Wednesday | 10 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Monthly 567&^% 7 | 3 | 2014-03-21 | 2014-04-18 | 18:00 | | 2 | | 3\|4\|5 | 5\|3 | |
|
||||
| Create with Monthly and the day=last and Wednesday, of the month=1,2,6,7,8,9,10,11,12 | 11 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Monthly 567&^% 8 | 3 | 2014-03-21 | 2014-04-18 | 18:00 | | 2 | | 1\|2\|6\|7\|8\|9\|10\|11\|12 | 5\|3 | |
|
||||
| Create with One time only | 12 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-One Time only 678%$@ | 4 | | | 20:00 | | | | | | |
|
||||
| Craate with Every | 13 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Every 987&%@ | 5 | | | | | | | | | 12.30 |
|
||||
| test_description | sch_uid_number | sch_del_user_name | sch_del_user_pass | tas_uid | sch_name | sch_option | sch_start_date | sch_end_date | sch_start_time | sch_week_days | sch_start_day | sch_start_day_opt_1 | sch_months | sch_start_day_opt_2 | sch_repeat_every | error_code |
|
||||
| Create with Daily | 1 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Daily 123@#$ | 1 | 2014-01-30 | 2014-02-20 | 12:00 | | | | | | | 201 |
|
||||
| Create with Weekly, sch_week_days=monday | 2 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Weekly monday 345%$# | 2 | 2014-02-20 | 2014-03-20 | 08:00 | 1 | | | | | | 201 |
|
||||
| Create with Weekly, sch_week_days=tuesday, wednesday, thursday, friday, saturday, sunday | 3 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Weekly 345%$# | 2 | 2014-02-20 | 2014-03-20 | 08:00 | 2\|3\|4\|5\|6\|7 | | | | | | 201 |
|
||||
| Create with Monthly and day of month, day of month=1, of the month(s)=3,4 | 4 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Monthly 567&^% 1 | 3 | 2014-03-21 | 2014-04-18 | 18:00 | | 1 | 15 | 3\|4 | | | 201 |
|
||||
| Create with Monthly and day of month, day of month=1, of the month=1,2,5,6,7,8,9,10,11,12 | 5 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Monthly 567&^% 2 | 3 | 2014-03-21 | 2014-04-18 | 18:00 | | 1 | 15 | 1\|2\|5\|6\|7\|8\|9\|10\|11\|12 | | | 201 |
|
||||
| Create with Monthly and the day=first and Monday | 6 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Monthly 567&^% 3 | 3 | 2014-03-21 | 2014-04-18 | 18:00 | | 2 | | 3\|4\|5 | 1\|7 | | 201 |
|
||||
| Create with Monthly and the day=second and Saturday | 7 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Monthly 567&^% 4 | 3 | 2014-03-21 | 2014-04-18 | 18:00 | | 2 | | 3\|4\|5 | 2\|6 | | 201 |
|
||||
| Create with Monthly and the day=Third and Friday | 8 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Monthly 567&^% 5 | 3 | 2014-03-21 | 2014-04-18 | 18:00 | | 2 | | 3\|4\|5 | 3\|5 | | 201 |
|
||||
| Create with Monthly and the day=second and Thursday | 9 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Monthly 567&^% 6 | 3 | 2014-03-21 | 2014-04-18 | 18:00 | | 2 | | 3\|4\|5 | 2\|4 | | 201 |
|
||||
| Create with Monthly and the day=last and Wednesday | 10 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Monthly 567&^% 7 | 3 | 2014-03-21 | 2014-04-18 | 18:00 | | 2 | | 3\|4\|5 | 5\|3 | | 201 |
|
||||
| Create with Monthly and the day=last and Wednesday, of the month=1,2,6,7,8,9,10,11,12 | 11 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Monthly 567&^% 8 | 3 | 2014-03-21 | 2014-04-18 | 18:00 | | 2 | | 1\|2\|6\|7\|8\|9\|10\|11\|12 | 5\|3 | | 201 |
|
||||
| Create with One time only | 12 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-One Time only 678%$@ | 4 | | | 20:00 | | | | | | | 201 |
|
||||
| Create with Every | 13 | admin | admin | 46941969352af5be2ab3f39001216717 | Case Scheduler-Every 987&%@ | 5 | | | | | | | | | 12.30 | 201 |
|
||||
|
||||
|
||||
Scenario: Create a new case scheduler with same name
|
||||
Given POST this data:
|
||||
"""
|
||||
{
|
||||
"sch_option": "5",
|
||||
"sch_name": "Case Scheduler-Every 987&%@",
|
||||
"sch_del_user_name": "admin",
|
||||
"sch_del_user_pass": "admin",
|
||||
"tas_uid": "46941969352af5be2ab3f39001216717",
|
||||
"sch_start_time": "",
|
||||
"sch_start_date": "",
|
||||
"sch_end_date": "",
|
||||
"sch_week_days": "",
|
||||
"sch_start_day": "",
|
||||
"sch_start_day_opt_1": "",
|
||||
"sch_start_day_opt_2": "",
|
||||
"sch_months": "",
|
||||
"sch_repeat_every": "12.30"
|
||||
}
|
||||
"""
|
||||
And I request "project/1265557095225ff5c688f46031700471/case-scheduler"
|
||||
Then the response status code should be 400
|
||||
And the response status message should have the following text "duplicate"
|
||||
|
||||
|
||||
Scenario: Get the case schedulers list when there are exactly 13 case schedulers
|
||||
Given I request "project/1265557095225ff5c688f46031700471/case-schedulers"
|
||||
|
||||
@@ -49,6 +49,20 @@ Feature: Dynaform Main Tests
|
||||
| create dynaform grid P2 | 42445320652cd534acb3824056962285 | Dynaform - Grid | dyn grid P2 | grid | 4 |
|
||||
|
||||
|
||||
Scenario: Create dynaform with same name
|
||||
Given POST this data:
|
||||
"""
|
||||
{
|
||||
"dyn_title": "Dynaform - Normal",
|
||||
"dyn_description": "dyn normal P1",
|
||||
"dyn_type": "xmlform"
|
||||
}
|
||||
"""
|
||||
And I request "project/14414793652a5d718b65590036026581/dynaform"
|
||||
Then the response status code should be 400
|
||||
And the response status message should have the following text "already exists"
|
||||
|
||||
|
||||
Scenario Outline: Create a Dynaform using the Copy/Import method
|
||||
Given POST this data:
|
||||
"""
|
||||
@@ -75,8 +89,28 @@ Feature: Dynaform Main Tests
|
||||
| test_description | project | dyn_title | dyn_description | dyn_type | dyn_uid_number | copy_prj_uid | copy_dyn_uid |
|
||||
| create dynaform copy 1 | 14414793652a5d718b65590036026581 | Dynaform - Copy 1 | dyn copy | xmlform | 5 | 42445320652cd534acb3824056962285 | 70070685552cd53605650f7062918506 |
|
||||
| create dynaform copy 2 | 42445320652cd534acb3824056962285 | Dynaform - Copy 2 | dyn copy | xmlform | 6 | 42445320652cd534acb3824056962285 | 70070685552cd53605650f7062918506 |
|
||||
|
||||
|
||||
|
||||
Scenario: Create a Dynaform using the Copy/Import with same name
|
||||
Given POST this data:
|
||||
"""
|
||||
{
|
||||
"dyn_title": "Dynaform - Copy 1",
|
||||
"dyn_description": "dyn copy",
|
||||
"dyn_type": "xmlform",
|
||||
"copy_import":
|
||||
{
|
||||
"prj_uid": "42445320652cd534acb3824056962285",
|
||||
"dyn_uid": "70070685552cd53605650f7062918506"
|
||||
}
|
||||
}
|
||||
"""
|
||||
And I request "project/14414793652a5d718b65590036026581/dynaform"
|
||||
Then the response status code should be 400
|
||||
And the response status message should have the following text "already exists"
|
||||
|
||||
|
||||
|
||||
Scenario Outline: Create dynaform based on a PMTable
|
||||
Given POST this data:
|
||||
"""
|
||||
@@ -110,6 +144,31 @@ Feature: Dynaform Main Tests
|
||||
| create dynaform pmtable 2 | 42445320652cd534acb3824056962285 | Dynaform - pmtable2 | dyn from pmtable2 | xmlform | 8 | 65193158852cc1a93a5a535084878044 | DYN_UID | @#APPLICATION |
|
||||
|
||||
|
||||
Scenario: Create dynaform based on a PMTable with same name
|
||||
Given POST this data:
|
||||
"""
|
||||
{
|
||||
"dyn_title": "Dynaform - pmtable 1",
|
||||
"dyn_description": "dyn from pmtable1",
|
||||
"dyn_type": "xmlform",
|
||||
"pmtable":
|
||||
{
|
||||
"tab_uid": "65193158852cc1a93a5a535084878044",
|
||||
"fields": [
|
||||
{
|
||||
"fld_name": "DYN_UID",
|
||||
"pro_variable": "@#APPLICATION "
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
"""
|
||||
And I request "project/14414793652a5d718b65590036026581/dynaform"
|
||||
And the content type is "application/json"
|
||||
Then the response status code should be 400
|
||||
And the response status message should have the following text "already exists"
|
||||
|
||||
|
||||
Scenario Outline: Get a List DynaForms of a Project list when there are 9 records, total in both projects
|
||||
Given I request "project/<project>/dynaforms"
|
||||
And the content type is "application/json"
|
||||
|
||||
@@ -58,6 +58,23 @@ Feature: Input Documents Main Tests
|
||||
| Create with special characters in inp doc tags | 14414793652a5d718b65590036026581 | 13 | My InputDocument13 | My InputDocument13 DESCRIPTION | REAL | ORIGINAL | PRIVATE | 1 | | INPU455 @##$$³¤¤ |
|
||||
|
||||
|
||||
Scenario: Create new Input Documents with same name
|
||||
Given POST this data:
|
||||
"""
|
||||
{
|
||||
"inp_doc_title": "My InputDocument1",
|
||||
"inp_doc_description": "My InputDocument2 DESCRIPTION",
|
||||
"inp_doc_form_needed": "VIRTUAL",
|
||||
"inp_doc_original": "ORIGINAL",
|
||||
"inp_doc_published": "PRIVATE",
|
||||
"inp_doc_versioning": "1",
|
||||
"inp_doc_destination_path": "",
|
||||
"inp_doc_tags": "INPUT"
|
||||
}
|
||||
"""
|
||||
And I request "project/14414793652a5d718b65590036026581/input-document"
|
||||
Then the response status code should be 400
|
||||
And the response status message should have the following text "already exists"
|
||||
|
||||
|
||||
Scenario: Get the Input Documents list when there are 13 records
|
||||
|
||||
@@ -88,6 +88,39 @@ Feature: Output Documents Main Tests
|
||||
| Create with special characters in out doc pdf security open password | 4224292655297723eb98691001100052 | 16 | Endpoint New Version PDF 19 | Output Document new version solo pdf | Output 15 | | TCPDF | 0 | Legal | 25 | 25 | 25 | 25 | PDF | HTML | 0 | | 1 | | | 1 | sample432@$#@$¼€¼½ | sample | print |
|
||||
| Create with special characters in out doc pdf security owner password | 4224292655297723eb98691001100052 | 17 | Endpoint New Version 20 | Output Document new version - EndPoint | Output 16 | | TCPDF | 1 | Letter | 30 | 30 | 30 | 30 | BOTH | HTML | 0 | | 0 | | | 0 | | sample432@$#@$¼€¼½ | |
|
||||
|
||||
|
||||
Scenario: Create Output Documents with same name
|
||||
Given POST this data:
|
||||
"""
|
||||
{
|
||||
"out_doc_title": "Endpoint Old Version",
|
||||
"out_doc_description": "Output Document old version - EndPoint",
|
||||
"out_doc_filename": "Output 1",
|
||||
"out_doc_template": "",
|
||||
"out_doc_report_generator": "HTML2PDF",
|
||||
"out_doc_landscape": "1",
|
||||
"out_doc_media": "Letter",
|
||||
"out_doc_left_margin": "30",
|
||||
"out_doc_right_margin": "30",
|
||||
"out_doc_top_margin": "30",
|
||||
"out_doc_bottom_margin": "30",
|
||||
"out_doc_generate": "BOTH",
|
||||
"out_doc_type": "HTML",
|
||||
"out_doc_current_revision": "0",
|
||||
"out_doc_field_mapping": "",
|
||||
"out_doc_versioning": "0",
|
||||
"out_doc_destination_path": "",
|
||||
"out_doc_tags": "",
|
||||
"out_doc_pdf_security_enabled": "0",
|
||||
"out_doc_pdf_security_open_password": "",
|
||||
"out_doc_pdf_security_owner_password": "",
|
||||
"out_doc_pdf_security_permissions": ""
|
||||
}
|
||||
"""
|
||||
And I request "project/4224292655297723eb98691001100052/output-document"
|
||||
Then the response status code should be 400
|
||||
And the response status message should have the following text "same name"
|
||||
|
||||
|
||||
Scenario: Get the Output Documents list when there are 19 records
|
||||
Given I request "project/4224292655297723eb98691001100052/output-documents"
|
||||
|
||||
@@ -73,4 +73,41 @@ Scenario Outline: Update Process
|
||||
| Set initial values | 79409754952f8f5110c4342001470580 | Test Process 2 | | 79409754952f8f5110c4342001470580 | 1 | DAYS | ACTIVE | | NORMAL | 0 | 0 | 0 | 0 | | | | | 0 | 0 | | | 0 | 2014-02-11 10:58:15 | 2014-02-10 10:49:37 | 00000000000000000000000000000001 | 0 | | | | 200 | |
|
||||
| Set initial values | 58773281752f50297d6bf00047802053 | Test Process 1 | | 58773281752f50297d6bf00047802053 | 1 | DAYS | ACTIVE | | NORMAL | 0 | 0 | 0 | 0 | | | | | 0 | 0 | | | 0 | 2014-02-11 10:58:15 | 2014-02-07 10:58:15 | 00000000000000000000000000000001 | 0 | | | | 200 | |
|
||||
|
||||
|
||||
|
||||
Scenario: Update Process
|
||||
Given PUT this data:
|
||||
"""
|
||||
{
|
||||
"pro_title" : "Test Process 2",
|
||||
"pro_description" : "",
|
||||
"pro_parent" : "74737540052e1641ab88249082085472",
|
||||
"pro_time" : "1",
|
||||
"pro_timeunit" : "DAYS",
|
||||
"pro_status" : "ACTIVE",
|
||||
"pro_type_day" : "",
|
||||
"pro_type" : "NORMAL",
|
||||
"pro_assignment" : "0",
|
||||
"pro_show_map" : "0",
|
||||
"pro_show_message" : "0",
|
||||
"pro_subprocess" : "0",
|
||||
"pro_tri_deleted" : "",
|
||||
"pro_tri_canceled" : "",
|
||||
"pro_tri_paused" : "",
|
||||
"pro_tri_reassigned" : "",
|
||||
"pro_show_delegate" : "0",
|
||||
"pro_show_dynaform" : "0",
|
||||
"pro_category" : "",
|
||||
"pro_sub_category" : "",
|
||||
"pro_industry" : "0",
|
||||
"pro_update_date" : "2014-02-10 10:58:15",
|
||||
"pro_create_date" : "2014-02-10 10:49:37",
|
||||
"pro_create_user" : "00000000000000000000000000000001",
|
||||
"pro_debug" : "0",
|
||||
"pro_derivation_screen_tpl": "",
|
||||
"pro_summary_dynaform" : "",
|
||||
"pro_calendar" : ""
|
||||
}
|
||||
"""
|
||||
And I request "project/74737540052e1641ab88249082085472/process"
|
||||
Then the response status code should be 400
|
||||
And the response status message should have the following text "already exists"
|
||||
@@ -171,6 +171,19 @@ Requirements:
|
||||
| Assign a user as Supervisor | 85794888452ceeef3675164057928956 | 2 | SUPERVISOR | 00000000000000000000000000000001 |
|
||||
|
||||
|
||||
Scenario: Assign a supervisor process when it was already assigned
|
||||
Given POST this data:
|
||||
"""
|
||||
{
|
||||
"pu_type": "SUPERVISOR",
|
||||
"usr_uid": "00000000000000000000000000000001"
|
||||
}
|
||||
"""
|
||||
And I request "project/85794888452ceeef3675164057928956/process-supervisor"
|
||||
Then the response status code should be 400
|
||||
And the response status message should have the following text "already exist"
|
||||
|
||||
|
||||
|
||||
Scenario Outline: Assign a dynaform to a process supervisor
|
||||
Given POST this data:
|
||||
@@ -191,6 +204,19 @@ Requirements:
|
||||
| test_description | project | pud_number | dyn_uid |
|
||||
| Assign a dynaform # 3 for Supervisor | 85794888452ceeef3675164057928956 | 1 | 92562207752ceef36c7d874048012431 |
|
||||
|
||||
|
||||
Scenario: Assign a dynaform to a process supervisor when it was already assigned
|
||||
Given POST this data:
|
||||
"""
|
||||
{
|
||||
"dyn_uid": "<92562207752ceef36c7d874048012431>"
|
||||
}
|
||||
"""
|
||||
And I request "project/85794888452ceeef3675164057928956/process-supervisor/dynaform"
|
||||
Then the response status code should be 400
|
||||
And the response status message should have the following text "already exists"
|
||||
|
||||
|
||||
|
||||
Scenario Outline: Assign an input document to a process supervisor
|
||||
Given POST this data:
|
||||
|
||||
@@ -49,8 +49,24 @@ Feature: Project Properties - Step Resources Main Tests
|
||||
| Input Document assigned to Task 1 in mode edit | 16062437052cd6141881e06088349078 | 10163687452cd6234e0dd25086954968 | INPUT_DOCUMENT | 83199959452cd62589576c1018679557 | | 2 | EDIT | 2 |
|
||||
| Output Document assigned to Task 1 in mode edit | 16062437052cd6141881e06088349078 | 10163687452cd6234e0dd25086954968 | OUTPUT_DOCUMENT | 32743823452cd63105006e1076595203 | | 3 | EDIT | 3 |
|
||||
| Dynaform assigned to Task 2 in mode view | 16062437052cd6141881e06088349078 | 89706843252cd9decdcf9b3047762708 | DYNAFORM | 50332332752cd9b9a7cc989003652905 | | 2 | VIEW | 4 |
|
||||
| External step to Task 2 | 16062437052cd6141881e06088349078 | 89706843252cd9decdcf9b3047762708 | EXTERNAL | 6869969705306aaae049a62048840877 | | 3 | VIEW | 5 |
|
||||
|
||||
|
||||
Scenario: Dynaform assigned to the task when it was already assigned
|
||||
Given POST this data:
|
||||
"""
|
||||
{
|
||||
"step_type_obj": "DYNAFORM",
|
||||
"step_uid_obj": "50332332752cd9b9a7cc989003652905",
|
||||
"step_condition": "",
|
||||
"step_position": "1",
|
||||
"step_mode": "EDIT"
|
||||
}
|
||||
"""
|
||||
And I request "project/16062437052cd6141881e06088349078/activity/10163687452cd6234e0dd25086954968/step"
|
||||
Then the response status code should be 400
|
||||
And the response status message should have the following text "exists"
|
||||
|
||||
|
||||
Scenario Outline: Update the five steps and then check if the values had changed
|
||||
Given PUT this data:
|
||||
@@ -77,6 +93,7 @@ Feature: Project Properties - Step Resources Main Tests
|
||||
| Update Input Document Task 1 (step_condition, step_position, step_mode) | 16062437052cd6141881e06088349078 | 10163687452cd6234e0dd25086954968 | @@YEAR==2014 | 5 | VIEW | INPUT_DOCUMENT | 83199959452cd62589576c1018679557 | 2 |
|
||||
| Update Output Document Task 1 (step_condition, step_position, step_mode) | 16062437052cd6141881e06088349078 | 10163687452cd6234e0dd25086954968 | | 6 | VIEW | OUTPUT_DOCUMENT | 32743823452cd63105006e1076595203 | 3 |
|
||||
| Update Dynaform Task 2 (step_condition, step_position, step_mode) | 16062437052cd6141881e06088349078 | 89706843252cd9decdcf9b3047762708 | @@YEAR==2014 | 2 | EDIT | DYNAFORM | 50332332752cd9b9a7cc989003652905 | 4 |
|
||||
| Update Dynaform Task 2 (step_condition, step_position, step_mode) | 16062437052cd6141881e06088349078 | 89706843252cd9decdcf9b3047762708 | @@YEAR==2014 | 3 | EDIT | EXTERNAL | 6869969705306aaae049a62048840877 | 5 |
|
||||
|
||||
|
||||
Scenario Outline: List assigned Steps to "Task1" & "Task 2"
|
||||
@@ -115,6 +132,7 @@ Feature: Project Properties - Step Resources Main Tests
|
||||
| List a triggers in Input Document of Task 1 | 16062437052cd6141881e06088349078 | 10163687452cd6234e0dd25086954968 | 2 |
|
||||
| List a triggers in Output Document of Task 1 | 16062437052cd6141881e06088349078 | 10163687452cd6234e0dd25086954968 | 3 |
|
||||
| List a triggers in Dynaform of task 2 | 16062437052cd6141881e06088349078 | 89706843252cd9decdcf9b3047762708 | 4 |
|
||||
| List a triggers in External Step of task 2 | 16062437052cd6141881e06088349078 | 89706843252cd9decdcf9b3047762708 | 5 |
|
||||
|
||||
|
||||
Scenario Outline: List available Triggers for each assigned step
|
||||
@@ -132,6 +150,7 @@ Feature: Project Properties - Step Resources Main Tests
|
||||
| List available a triggers in Input Document of Task 1 | 16062437052cd6141881e06088349078 | 10163687452cd6234e0dd25086954968 | 2 |
|
||||
| List available a triggers in Output Document of Task 1 | 16062437052cd6141881e06088349078 | 10163687452cd6234e0dd25086954968 | 3 |
|
||||
| List available a triggers in Dynaform of task 2 | 16062437052cd6141881e06088349078 | 89706843252cd9decdcf9b3047762708 | 4 |
|
||||
| List available a triggers in External Step of task 2 | 16062437052cd6141881e06088349078 | 89706843252cd9decdcf9b3047762708 | 5 |
|
||||
|
||||
|
||||
|
||||
@@ -196,6 +215,7 @@ Feature: Project Properties - Step Resources Main Tests
|
||||
| List available a triggers in Input Document of Task 1 | 16062437052cd6141881e06088349078 | 10163687452cd6234e0dd25086954968 | 2 |
|
||||
| List available a triggers in Output Document of Task 1 | 16062437052cd6141881e06088349078 | 10163687452cd6234e0dd25086954968 | 3 |
|
||||
| List available a triggers in Dynaform of task 2 | 16062437052cd6141881e06088349078 | 89706843252cd9decdcf9b3047762708 | 4 |
|
||||
| List available a triggers in External Step of task 2 | 16062437052cd6141881e06088349078 | 89706843252cd9decdcf9b3047762708 | 5 |
|
||||
|
||||
|
||||
|
||||
@@ -305,6 +325,7 @@ Feature: Project Properties - Step Resources Main Tests
|
||||
| Trigger assigned to Task 2 in type After | 16062437052cd6141881e06088349078 | 10163687452cd6234e0dd25086954968 | 2 | 6 |
|
||||
| Trigger assigned to Task 2 in type After | 16062437052cd6141881e06088349078 | 10163687452cd6234e0dd25086954968 | 3 | 0 |
|
||||
| Trigger assigned to Task 2 in type before | 16062437052cd6141881e06088349078 | 89706843252cd9decdcf9b3047762708 | 4 | 0 |
|
||||
| Trigger assigned to External in type before | 16062437052cd6141881e06088349078 | 89706843252cd9decdcf9b3047762708 | 5 | 0 |
|
||||
|
||||
|
||||
Scenario Outline: Unassign all"DynaForm Demo1" from "Task1"
|
||||
|
||||
@@ -56,6 +56,22 @@ Feature: Testing triggers Main Tests
|
||||
| Create trigger without tri param | 251815090529619a99a2bf4013294414 | 5 | otro trigger 5 | descripcion del tercer trigger 5 | | | |
|
||||
|
||||
|
||||
Scenario: Create a new triggers with same name
|
||||
Given POST this data:
|
||||
"""
|
||||
{
|
||||
"tri_title": "nuevo trigger 1",
|
||||
"tri_description": "descripcion del primer trigger 1",
|
||||
"tri_type": "SCRIPT",
|
||||
"tri_webbot": "@@user1 = @@USER_LOGGED; \n $x = rand();",
|
||||
"tri_param": "PRIVATE"
|
||||
}
|
||||
"""
|
||||
And I request "project/251815090529619a99a2bf4013294414/trigger"
|
||||
Then the response status code should be 400
|
||||
And the response status message should have the following text "same name"
|
||||
|
||||
|
||||
Scenario: Get the Triggers List when there are 7 records
|
||||
Given I request "project/251815090529619a99a2bf4013294414/triggers"
|
||||
Then the response status code should be 200
|
||||
|
||||
Reference in New Issue
Block a user