Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.4
    • Fix Version/s: 2.4
    • Component/s: Quality Assurance
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-11108Analyze CI Failures for 2.4.0-m3 QA Sprint 2
      KULRICE-11229Analyze CI Failures for 2.4.0-m3 QA Sprint 3
      KULRICE-11338Analyze CI Failures for 2.4.0-m3 QA Sprint 4
      KULRICE-11956Analyze CI Failures for 2.4.0-rc1 QA Sprint 1
      KULRICE-11781Analyze CI Failures for 2.4.0-QA QA Sprint 1
      KULRICE-10804Analyze CI Failures for 2.4.0-m2 QA Sprint 4
      KULRICE-13547Analyze AFT failures - 2.5.0-m4 QA Sprint 1
      KULRICE-13613Analyze AFT failures - QA 2.5.0-m5 Sprint 1
      KULRICE-13801Analyze CI Failures for 2.4.0-rc1 QA Sprint 9
      KULRICE-11568Analyze CI Failures for 2.4.0-m4 QA Sprint 2
    • Rice Team:
      QA
    • Sprint:
      2.4.0-m3 QA Sprint 1
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required

      Description

      Go through the 2.4 functional tests, examining new failures. Typically these failures need to be run locally in order to determine if it's an environment or timing issue. If an Incident Report, 404, 500 error is present, add a checkForIncidentReport before the failure point. Create a Jira if a legitimate failure, update JiraAwareFailure to speed up future analysis of failures. In some cases a "message" version of a method might need to be created in WebDriverLegacyITBase (usually trivial to do) so the JiraAwareFailure can use the message as a key.

      Existing failing tests need to be glanced through as it is not uncommon for a test that already failing to fail with a new error.

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Erik Meade
              Reporter:
              Erik Meade
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 3 days
                3d
                Remaining:
                Time Spent - 2 days, 3 minutes Remaining Estimate - 7 hours, 57 minutes
                7h 57m
                Logged:
                Time Spent - 2 days, 3 minutes Remaining Estimate - 7 hours, 57 minutes
                2d 3m

                  Agile

                    Structure Helper Panel