Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-13866

Test harness needs to support a common set of props and code to set ports etc.

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Quality Assurance
    • Labels:
    • Rice Team:
      QA

      Description

      KRA and Rice test frameworks work slightly different in how they manage ports. We need some common code at the top of the test stack that manages this common stuff with props named the same for convenience going between environments and applications. We should probably look to the future to different dbs as well and any other common props the 2 projects may have in CI (workflow)>

        Attachments

          Activity

          Hide
          agodert Aaron Godert (Inactive) added a comment -

          Originally reported by Ryan. Changing Reporter field so that he doesn't receive automatic notifications any further.

          Show
          agodert Aaron Godert (Inactive) added a comment - Originally reported by Ryan. Changing Reporter field so that he doesn't receive automatic notifications any further.
          Hide
          ewestfal Eric Westfall added a comment -

          Bryan, is this still an issue for you guys?

          Show
          ewestfal Eric Westfall added a comment - Bryan, is this still an issue for you guys?
          Hide
          bhutchinson Bryan Hutchinson added a comment -

          I'm having a hard time remembering this one, but I think at least the issue with managing the ports has been taken care of. There may still be other things that could/should be generalized.

          Show
          bhutchinson Bryan Hutchinson added a comment - I'm having a hard time remembering this one, but I think at least the issue with managing the ports has been taken care of. There may still be other things that could/should be generalized.
          Hide
          ahamid Aaron Hamid (Inactive) added a comment -

          For what it's worth, I recently added support to the config for generation of random integers. Although this is not a bulletproof solution, given large enough port ranges this might suffice to avoid manual configuration. There are some properties already defined in the test defaults if you want to try using them. E.g.:

          <param name="unittest.jetty.server1.port" override="false" random="true">10000-10999</param>
          <param name="unittest.jetty.server2.port" override="false" random="true">11000-11999</param>
          <param name="unittest.jetty.server3.port" override="false" random="true">12000-12999</param>
          <param name="unittest.jetty.server4.port" override="false" random="true">13000-13999</param>
          <param name="unittest.jetty.server5.port" override="false" random="true">14000-14999</param>
          <param name="unittest.jetty.server6.port" override="false" random="true">15000-15999</param>
          <param name="unittest.jetty.server7.port" override="false" random="true">16000-16999</param>
          <param name="unittest.jetty.server8.port" override="false" random="true">17000-17999</param>
          <param name="unittest.jetty.server9.port" override="false" random="true">18000-18999</param>
          <param name="unittest.jetty.server10.port" override="false" random="true">19000-19999</param>

          There are some subtle complications if you actually want to retrieve the value from within your webapp unit test (and not just within the webapp) due to how the jetty lifecycle makes the webapp config by default override the unit test config (this is now configurable though).

          Show
          ahamid Aaron Hamid (Inactive) added a comment - For what it's worth, I recently added support to the config for generation of random integers. Although this is not a bulletproof solution, given large enough port ranges this might suffice to avoid manual configuration. There are some properties already defined in the test defaults if you want to try using them. E.g.: <param name="unittest.jetty.server1.port" override="false" random="true">10000-10999</param> <param name="unittest.jetty.server2.port" override="false" random="true">11000-11999</param> <param name="unittest.jetty.server3.port" override="false" random="true">12000-12999</param> <param name="unittest.jetty.server4.port" override="false" random="true">13000-13999</param> <param name="unittest.jetty.server5.port" override="false" random="true">14000-14999</param> <param name="unittest.jetty.server6.port" override="false" random="true">15000-15999</param> <param name="unittest.jetty.server7.port" override="false" random="true">16000-16999</param> <param name="unittest.jetty.server8.port" override="false" random="true">17000-17999</param> <param name="unittest.jetty.server9.port" override="false" random="true">18000-18999</param> <param name="unittest.jetty.server10.port" override="false" random="true">19000-19999</param> There are some subtle complications if you actually want to retrieve the value from within your webapp unit test (and not just within the webapp) due to how the jetty lifecycle makes the webapp config by default override the unit test config (this is now configurable though).

            People

            • Assignee:
              Unassigned
              Reporter:
              agodert Aaron Godert (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: