Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sprint:
      CFAMX 2020R4 Sprint 3
    • SCRUM Team:
      Brotherhood of Mutants
    • Story Points:
      2
    • Work Type Classification:
      Sustaining

      Description

      Details

      With the framework updates required to facilitate more robust API, the site should undergo regular smoke tests. These test should be completed by the QA and product teams. The goal of these tests is to confirm that basic functionality of the site is intact after major back-end updates are deployed.

      Frequency

      Team members should meet and complete high-level smoke tests after any major back-end upgrade. These meetings should require around an hour and any defects or issues found during these test should be documented and submitted as defects.

      UAC

      Confirm

      1. A group smoke test was completed as part of a major back-end software update.
      2. Any issues found during this test have been documented and submitted as defects.

        Attachments

          Issue Links

          There are no Sub-Tasks for this issue.

            Activity

              People

              • Assignee:
                jason.powell Jason Powell
                Reporter:
                jason.powell Jason Powell
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 16h Original Estimate - 16h
                  16h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 25h
                  25h

                    PagerDuty

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