Details

    • Sprint:
      CFAMX 2020R1 - SA Sprint 4
    • SCRUM Team:
      Globogym Purple Cobras
    • Story Points:
      8
    • SOW (Time Tracking) Project:
      44918
    • Work Type Classification:
      Sustaining

      Description

      As a developer executing the load tests I want 300 Open stores to be identified for load testing so that all load tests can run for a sustained period

      When the original scripts were written, to identify 100 stores, and create 100 users a couple of things were missed.

      1. Some of the stores that were identified were/are no in a Closed status
      2. As new features were created, the User Role associated to the users that were created were not maintained

      It is Will's belief that the list of 100 stores needs to be expanded to 300 (possibly more, but let's start here).
      Some of the load tests complete before the load test period is done, as they are out of data.
      Question: Is this due to the total number of stores or the number of stores that are in each of the csv files used for load testing?

      Please update the script to identify 300 stores that are in an Open state

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                caner.saritac Caner Saritac
                Reporter:
                will.englefield Will Englefield (Inactive)
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 13.5h Original Estimate - 13.5h
                  13.5h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 15h 1m
                  15h 1m

                    PagerDuty

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