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

        Attachments

          Activity

          gilesp Peter Giles (Inactive) created issue -
          gilesp Peter Giles (Inactive) made changes -
          Field Original Value New Value
          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.

          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.

          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. I would like for whatever we choose to be practical to execute via JUnit tests, so that is one hard constraint.

          Once we've agreed on a tool, you can begin coding it up or setting it up as the case may be.
          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.

          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.
          ewestfal Eric Westfall made changes -
          Fix Version/s 1.0.1 [ 15300 ]
          Fix Version/s 1.0 [ 13481 ]
          ewestfal Eric Westfall made changes -
          Priority Critical [ 2 ] Minor [ 4 ]
          ewestfal Eric Westfall made changes -
          Original Estimate 1 day [ 28800 ]
          Remaining Estimate 1 day [ 28800 ]
          ewestfal Eric Westfall made changes -
          Fix Version/s 1.0.x for KC 2.0 [ 15416 ]
          Fix Version/s 1.0.1 [ 15300 ]
          ewestfal Eric Westfall made changes -
          Fix Version/s 1.1 [ 14190 ]
          Fix Version/s 1.0.x for KC 2.0 [ 15416 ]
          ewestfal Eric Westfall made changes -
          Fix Version/s 1.1? [ 15811 ]
          Fix Version/s 1.1 [ 14190 ]
          gilesp Peter Giles (Inactive) made changes -
          Assignee Srikanth Mummadi [ smummadi ] Peter Giles [ gilesp ]
          gilesp Peter Giles (Inactive) made changes -
          Original Estimate 1 day [ 28800 ] 1 week [ 144000 ]
          Remaining Estimate 1 day [ 28800 ] 1 week [ 144000 ]
          Fix Version/s 1.1 [ 14190 ]
          Fix Version/s 1.1? [ 15811 ]
          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.

          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.
          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.
          Priority Minor [ 4 ] Major [ 3 ]
          ewestfal Eric Westfall made changes -
          Fix Version/s 1.1? [ 15811 ]
          Fix Version/s 1.1 [ 14190 ]
          gilesp Peter Giles (Inactive) made changes -
          Link This issue relies on KRQATC-39 [ KRQATC-39 ]
          gilesp Peter Giles (Inactive) made changes -
          Link This issue relies on KRQATC-39 [ KRQATC-39 ]
          jcoltrin Jessica Coltrin (Inactive) made changes -
          Assignee Peter Giles [ gilesp ]
          eghm-kuali-m Erik Meade made changes -
          Fix Version/s QA-backlog [ 16610 ]
          Affects Version/s QA-backlog [ 16610 ]
          spatterson Shem Patterson (Inactive) made changes -
          Workflow custom [ 73170 ] Copy of custom for rice [ 206718 ]
          spatterson Shem Patterson (Inactive) made changes -
          Workflow Copy of custom for rice [ 206718 ] custom [ 216466 ]
          spatterson Shem Patterson (Inactive) made changes -
          Workflow custom [ 216466 ] Rice Workflow [ 226214 ]
          jcoltrin Jessica Coltrin (Inactive) made changes -
          Fix Version/s QA-backlog [ 16610 ]
          jcoltrin Jessica Coltrin (Inactive) made changes -
          Affects Version/s 1.0 [ 13481 ]
          Affects Version/s QA-backlog [ 16610 ]
          jcoltrin Jessica Coltrin (Inactive) made changes -
          Affects Version/s 1.0 [ 13481 ]
          jcoltrin Jessica Coltrin (Inactive) made changes -
          Rank (Obsolete) 19210000000
          jcoltrin Jessica Coltrin (Inactive) made changes -
          Parent KULRICE-3116 [ 55541 ]
          Issue Type Sub Task [ 43 ] Task [ 3 ]
          jcoltrin Jessica Coltrin (Inactive) made changes -
          Project Kuali Rice Development [ 10220 ] Kuali Rice QA [ 11391 ]
          Key KULRICE-3293 RICEQA-257
          Requires Application Refactoring No [ 10923 ]
          Responsible Team Rice Team [ 10940 ]
          Reviewed by Prioritization Committee No [ 10443 ]
          Component/s Quality Assurance [ 14576 ]
          Component/s Quality Assurance [ 11245 ]
          Fix Version/s Backlog [ 15811 ]
          Forced Change No [ 11114 ]
          acampbell Adam Campbell (Inactive) made changes -
          Project Kuali Rice QA [ 11391 ] Kuali Rice Development [ 10220 ]
          Key RICEQA-257 KULRICE-13693
          Component/s Quality Assurance [ 11245 ]
          Component/s Quality Assurance [ 14576 ]
          acampbell Adam Campbell (Inactive) made changes -
          Fix Version/s Backlog [ 15811 ]
          acampbell Adam Campbell (Inactive) made changes -
          Rice Team QA [ 16025 ]
          ewestfal Eric Westfall made changes -
          Labels Old

            People

            • Assignee:
              Unassigned
              Reporter:
              gilesp 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