Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-13379

Create Web Tests for KRAD Maintenance Document permission check on route

    Details

    • Type: Task Task
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Quality Assurance
    • Labels:
    • 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.

        Issue Links

          Activity

          Peter Giles (Inactive) made changes -
          Field Original Value New Value
          Link This issue cloned to KULRICE-10657 [ KULRICE-10657 ]
          Peter Giles (Inactive) made changes -
          Description The KRAD Maintenance documents need to have their business rules tested and verified:

          What specifically needs to be tested:
          * The {{isDocumentValidForSave}} is throwing the correct errors in the correct situations
          * The document authorizer does not allow the wrong person to be able to edit a document
          * If there is another document blocking the current document from having changes done, then an error should be thrown.
          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.
          Peter Giles (Inactive) made changes -
          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. 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.
          Kristina Taylor (Inactive) made changes -
          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.
          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.
          Hide
          Claus Niesen added a comment -

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

          Show
          Claus Niesen added a comment - I don't know a better way to test this.
          Jessica Coltrin (Inactive) made changes -
          Project Kuali Rice Development [ 10220 ] Kuali Rice QA [ 11391 ]
          Key KULRICE-11447 RICEQA-122
          KRAD Feature Area Maintenance [ 14292 ]
          Include in Release Notes? Yes [ 14658 ]
          Responsible Team Rice Team [ 10940 ]
          Reviewed by Prioritization Committee No [ 10443 ]
          Fix Version/s 2.4 [ 16913 ]
          Security Public [ 10056 ]
          KTI Review Status Not Required [ 13053 ]
          KAI Review Status Not Required [ 13050 ]
          Requires Application Refactoring No [ 10923 ]
          QA Review Status Pending Review [ 13669 ]
          Code Review Status Not Required [ 14985 ]
          Component/s Quality Assurance [ 14576 ]
          Component/s Quality Assurance [ 11245 ]
          Documentation Review Status Pending Review [ 14643 ]
          Forced Change No [ 11114 ]
          Adam Campbell (Inactive) made changes -
          Project Kuali Rice QA [ 11391 ] Kuali Rice Development [ 10220 ]
          Key RICEQA-122 KULRICE-13379
          Component/s Quality Assurance [ 11245 ]
          Component/s Quality Assurance [ 14576 ]
          Adam Campbell (Inactive) made changes -
          Fix Version/s Backlog [ 15811 ]
          Adam Campbell (Inactive) made changes -
          Rice Team QA [ 16025 ]
          Eric Westfall made changes -
          Labels Old

            People

            • Assignee:
              Unassigned
              Reporter:
              Kristina Taylor (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:

                Time Tracking

                Estimated:
                Original Estimate - 1 day
                1d
                Remaining:
                Remaining Estimate - 1 day
                1d
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Structure Helper Panel