Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-6808

Load Test Ordering

    Details

    • Sprint:
      CFAMX 2020R1 Sprint 3
    • SCRUM Team:
      Brotherhood of Mutants
    • Story Points:
      3
    • SOW (Time Tracking) Project:
      44918
    • Work Type Classification:
      Sustaining

      Description

      Update the Ordering Load test to do the following:

      1. Create an order for 100 items
        • It may be necessary to update the scripts used to stage data to ensure that the target stores have an appropriate vendor that has 100 items.
        • I am not convinced that this is currently true
      2. Make the ordering test a single test, that cleans up after itself
      3. In other words, receive the order that was just placed, as a part of the test
      4. Currently there are two load tests for ordering:
        • CreateOrder
        • ReceiveOrders
        • Merge these into one single test

        Attachments

          Issue Links

          implements

          Feature Request - CFAMX-2238 Load Test Automation Execution during 2020R1

          • Major - Major loss of function.
          • Closed
          There are no Sub-Tasks for this issue.

            Activity

              People

              • Assignee:
                soma.dixon Soma Dixon (Inactive)
                Reporter:
                will.englefield Will Englefield (Inactive)
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 29h 25m Original Estimate - 29h 25m
                  29h 25m
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 29.5h
                  29.5h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.