Details

    • Type: Task
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 1.0.3.1
    • Fix Version/s: 1.0.3.1
    • Component/s: Administrative
    • Labels:
      None

      Description

      Enable contributors to provide well tested contributions to KEW by documenting how to write a KEW unit test.

      This work could include making a template test that has all the configuration hooks documented (which we could add to source control), or simply finding a canonical example amongst the existing KEW tests and documenting it. I'll spend a bit of time seeing if I can find such an example to help get things started.

        Attachments

          Activity

          Hide
          gilesp Peter Giles (Inactive) added a comment - - edited

          This work will be really useful to new members of the Rice team as well.

          Some config hooks / utilities to document:

          • org.kuali.rice.kew.test.KEWTestCase.loadTestData() – see ActionRequestScenariosTest, QuickLinksServiceTest
          • org.kuali.rice.kew.test.KEWTestCase.setUpAfterDataLoad() – see ActionItemServiceTest
          • org.kuali.rice.kew.test.KEWTestCase.getKEWBootstrapSpringFile() – see RiceServiceOverrideTest
          • adding/overriding rice config via ConfigFactoryBean.configLocations – see RiceServiceOverrideTestSpringBeans.xml
          • org.kuali.rice.kew.test.KEWTestCase.loadXmlFile(...) for content ingestion – see ActionRequestScenariosTest (and just about every other KEW test)
          • org.kuali.rice.test.SQLDataLoader for direct SQL updating – see QuickLinksServiceTest
          • org.kuali.rice.kew.test.TestUtilities for workflow doc related assertions, etc – see ActionRequestScenariosTest

          Looking around a bit it's clear that we're not going to find all of these in one existing test, so I think making a template test extending KEWTestCase with these hooks in there and well commented would be a good way to start. Then create a wiki page that documents use of the template.

          Show
          gilesp Peter Giles (Inactive) added a comment - - edited This work will be really useful to new members of the Rice team as well. Some config hooks / utilities to document: org.kuali.rice.kew.test.KEWTestCase.loadTestData() – see ActionRequestScenariosTest, QuickLinksServiceTest org.kuali.rice.kew.test.KEWTestCase.setUpAfterDataLoad() – see ActionItemServiceTest org.kuali.rice.kew.test.KEWTestCase.getKEWBootstrapSpringFile() – see RiceServiceOverrideTest adding/overriding rice config via ConfigFactoryBean.configLocations – see RiceServiceOverrideTestSpringBeans.xml org.kuali.rice.kew.test.KEWTestCase.loadXmlFile(...) for content ingestion – see ActionRequestScenariosTest (and just about every other KEW test) org.kuali.rice.test.SQLDataLoader for direct SQL updating – see QuickLinksServiceTest org.kuali.rice.kew.test.TestUtilities for workflow doc related assertions, etc – see ActionRequestScenariosTest Looking around a bit it's clear that we're not going to find all of these in one existing test, so I think making a template test extending KEWTestCase with these hooks in there and well commented would be a good way to start. Then create a wiki page that documents use of the template.
          Hide
          wbalderamos William Balderamos (Inactive) added a comment - - edited

          Going to put the documentation for this here: https://wiki.kuali.org/display/KULRICE/KEWContributions

          Show
          wbalderamos William Balderamos (Inactive) added a comment - - edited Going to put the documentation for this here: https://wiki.kuali.org/display/KULRICE/KEWContributions
          Hide
          wbalderamos William Balderamos (Inactive) added a comment -

          The initial work for this has been completed, once we have a test drive going through the process we should revisit this and update. I believe we will have to make adjustments regardless come rice 1.1.

          Show
          wbalderamos William Balderamos (Inactive) added a comment - The initial work for this has been completed, once we have a test drive going through the process we should revisit this and update. I believe we will have to make adjustments regardless come rice 1.1.
          Hide
          jcoltrin Jessica Coltrin (Inactive) added a comment -

          closing since 1.0.3.1 is released.

          Show
          jcoltrin Jessica Coltrin (Inactive) added a comment - closing since 1.0.3.1 is released.

            People

            • Assignee:
              wbalderamos William Balderamos (Inactive)
              Reporter:
              gilesp Peter Giles (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 4 days
                4d
                Remaining:
                Time Spent - 3 days Remaining Estimate - 1 day
                1d
                Logged:
                Time Spent - 3 days Remaining Estimate - 1 day
                3d