Modificaciones a los features case actions, input document, assignee, step y triggers

This commit is contained in:
Wendy Nestor
2014-04-16 10:31:32 -04:00
parent e76287245d
commit ffc93f9abf
6 changed files with 40 additions and 16 deletions

View File

@@ -191,7 +191,7 @@ Scenario: Returns a list of the cases for the logged in user (Draft)
Scenario Outline: Returns the variables can be system variables and/or case variables.
Scenario Outline: Returns case variables generated by triggers before assignment (ba), before routing (br) and after routing (ar).
Given I request "cases/app_uid/variables" with the key "app_uid" stored in session array as variable "app_uid_<case_number>"
Then the response status code should be 200
And the response charset is "UTF-8"
@@ -202,8 +202,8 @@ Scenario Outline: Returns the variables can be system variables and/or case vari
Examples:
| test_description | case_number |
| Derivate case of the process "Derivation rules - sequential" | 6 |
| test_description | case_number |
| Derivate case of the process "Derivation rules - sequential" with triggers | 6 |
Scenario Outline: Sends variables to a case
@@ -258,9 +258,7 @@ Scenario Outline: Route a case to the next task in the process
| Derivate case of the process "Derivation rules - evaluation" | 7 |
| Derivate case of the process "Derivation rules - Parallel" | 8 |
| Derivate case of the process "Derivation rules - parallel evaluation" | 9 |
| Derivate case of the process "Derivation rules - selection" | 10 |
| Derivate case of the process "Derivation rules - evaluation" | 27 |
Scenario Outline: Returns the variables can be system variables and/or case variables.
Given I request "cases/app_uid/variables" with the key "app_uid" stored in session array as variable "app_uid_<case_number>"
@@ -283,7 +281,7 @@ Scenario: Returns a list of the cases for the logged in user (Inbox)
Then the response status code should be 200
And the response charset is "UTF-8"
And the type is "array"
And the response has 18 records
And the response has 15 records
Scenario Outline: Cancel a case

View File

@@ -47,7 +47,7 @@ Scenario Outline: Create a new case Impersonate (Negative Test)
Examples:
| Description | pro_uid | usr_uid | tas_uid | error_code | error_message |
| Create new case with process "Derivation rules - sequential" invalid pro_uid | 99201111111111111138927000421575 | 51049032352d56710347233042615067 | 68707275350ec281ada1c95068712556 | 400 | pro_uid |
| Create new case with process "Derivation rules - evaluation" invalid tas_uid | 99209594750ec27ea338927000421575 | 44811996752d567110634a1013636964 | 68707211111111111111111111712556 | 400 | tas_uid |
| Create new case with process "Derivation rules - evaluation" invalid tas_uid | 99209594750ec27ea338927000421575 | 44811996752d567110634a1013636964 | 68707211111111111111111111712556 | 400 | tas_uid |
| Create new case with process "Derivation rules - Parallel" usr_uid | 99209594750ec27ea338927000421575 | 24166331111111111111115035621101 | 68707275350ec281ada1c95068712556 | 400 | usr_uid |
| Create new case with process "Derivation rules - without pro_uid | | 86677227852d5671f40ba25017213081 | 68707275350ec281ada1c95068712556 | 400 | pro_uid |
| Create new case with process "Derivation rules - selection" tas_uid | 99209594750ec27ea338927000421575 | 62625000752d5672d6661e6072881167 | | 400 | tas_uid |

View File

@@ -10,7 +10,7 @@ Background:
Scenario: Returns a list of the uploaded documents for a given case
Given I request "cases/170220159534214f642abb8058832900/input-documents"
Then the response status code should be 404
Then the response status code should be 400
Scenario Outline: Post metadata and then upload documents for a given case
Given POST upload an input document "<document_file>" to "cases/<case_uid>/input-document"