Uploaded image for project: 'mod-orders'
  1. mod-orders
  2. MODORDERS-212

Split up unit tests

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Priority: P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 5.0.0
    • Labels:
    • Template:
    • Sprint:
      ACQ Sprint 62
    • Story Points:
      2
    • Development Team:
      Thunderjet

      Description

      Overview:
      The mod-orders unit tests are getting a little unwieldy... all of the testing is done in a single huge test class (> 47k SLOC). This should be refactored to make it easier to manage. A few ideas:

      • Pull out mock server into separate class
      • Split up test cases into logical groups... e.g. via API: composite-orders, order-lines, etc.
      • Split common/shared code out into base classes and/or utilities
      • Use test suites (see mod-orders-storage)

      Time Box: 2 days - follow-on stories can be created if necessary.

      Acceptance Criteria:

      • Test coverage is the same or higher than before
      • Test run duration is reduced or lower than before
      • Follow-on stories have been created if necessary

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                cmcnally Craig McNally
                Reporter:
                cmcnally Craig McNally
                Tester Assignee:
                Craig McNally Craig McNally
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases