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

Come up with an automated solution for link verification in the Rice portal

    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-7388Analysis on portal implementations
      KULRICE-968Add section to KFS portal to link up the new KSB web app links for the message queue
      KULRICE-5188Need to remove ImmutableListAdapter and ImmutableCollectionAdapter from our service definitions and come up with a better solution because it is producing undesirable XML
      KULRICE-11159Come up with proposal for handling xml ingested updates
      KULRICE-4780remove the "RIA Mapping" link in the rice portal
      KULRICE-12628Need to come up with a generalized solution for adding new plugins that create non KRAD components in the DOM
      KULRICE-2949Create a proper Rice "portal"
      KULRICE-14160Document how we want to handle testing and verification of pull requests from external entities
      KULRICE-4691manual test cases for all of the different screens that are linked off of the Rice portal
      KULRICE-11984DemoLookUpOperatorsAft: update so only result table is used for verification
    • Rice Team:
      QA

      Description

      As part of our functional testing, we will want to verify that all the links in the portal are valid – that they take us to other pages in the portal, and that those pages don't give us an exception incident form or some other clear indication of brokenness – and do so in an automated fashion. It would be a bonus to do HTML validation as we go.

      What I'd like you to do is begin by assessing our options here. We can use a specific link checking tool, or we could write our own crawler & link checker using HtmlUnit/JWebUnit or Selenium.

      I would like for whatever we choose to be practical to execute via JUnit tests, so that is one hard constraint.

      One advantage of using Selenium is that it will get you familiar with that tool set which we're planning to use for more specific functional testing testing of our pages, but I want you to be free to choose something else if is compellingly better.

      Once we've agreed on a tool, you can begin coding it up or setting it up as the case may be.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Peter Giles (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Time Tracking

              Estimated:
              Original Estimate - 1 week
              1w
              Remaining:
              Remaining Estimate - 1 week
              1w
              Logged:
              Time Spent - Not Specified
              Not Specified

                Structure Helper Panel