[KULRICE-13379] Create Web Tests for KRAD Maintenance Document permission check on route Created: 16/Dec/13  Updated: 16/Jan/15

Status: Open
Project: Kuali Rice Development
Component/s: Quality Assurance
Affects Version/s: None
Fix Version/s: Backlog

Type: Task Priority: Major
Reporter: Kristina Taylor (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Old
Remaining Estimate: 1 day
Time Spent: Not Specified
Original Estimate: 1 day

Issue Links:
Cloners
cloned from KULRICE-10657 Create Web Tests for KRAD Maintenance... Closed
Similar issues:
KULRICE-13685Create Web Tests for KRAD Maintenance Permission Features
KULRICE-13402Create Web Tests for KRAD Maintenance Dialogs
KULRICE-10672Create Web Tests for KRAD Maintenance Required Fields
KULRICE-13725Create Web Tests for KRAD Maintenance Document Business Rules to check Inactivation Blocking
KULRICE-10665Create Web Tests for KRAD Maintenance Document Locking
KULRICE-10746Create Web Tests for KRAD Transactional Dialogs
KULRICE-13568Create a smoke test for KRAD maintenance documents permission features
KULRICE-10461Create Web Tests for KRAD Maintenance Document Masked Fields
KULRICE-10657Create Web Tests for KRAD Maintenance Document Business Rules
KULRICE-13730Create Web Tests for KRAD Maintenance Document View Presentation Controller
Rice Team: QA

 Description   

Test that upon document routing (submit/blanket approve), KRAD performs a permission check via the document authorizer to ensure that the initiator can edit that particular business object. This will be a bit tricky to test, because the user that edits the doc will need the permission to start editing the document, but that permission will then need to be revoked to prove that the check is being made.

This will validate that feature M69 from the maintenance document gap analysis is still working. Check with Claus to see if there is a better way to test this feature.



 Comments   
Comment by Claus Niesen [ 12/Feb/14 ]

I don't know a better way to test this.

Generated at Fri Jun 05 14:02:36 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.