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

Understand and Fix Integration Tests

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sprint:
      2022.R2 New Features Sprint 5
    • SCRUM Team:
      Brotherhood of Mutants
    • Story Points:
      2
    • Work Type Classification:
      Sustaining

      Description

      Story 

      As a developer, I would like to have the integration tests working. 

       

      Description

      Here is the confluence document for details: 

      https://fourthlimited.atlassian.net/wiki/spaces/RBCD/pages/1727955414/CFA+Integration+Testing

       

      We have started getting integration test failures:

      The following Integration Tests have failed:
       - TestDoTBCOutsideSalesNotLinkedToCustomersExist: Assert.IsTrue failed. Outside Sale without Customer not found.
         - Stacktrace:    at Mx.Financial.Tests.Integration.BankingCloseRepositoryTests.TestDoTBCOutsideSalesNotLinkedToCustomersExist()

       

      AC

      Confirm that integration tests are running with no errors. 

       

        Attachments

        There are no Sub-Tasks for this issue.

          Activity

            People

            • Assignee:
              caner.saritac Caner Saritac
              Reporter:
              jason.powell Jason Powell
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 7h
                7h
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 2h 7m Time Not Required
                2h 7m

                  PagerDuty

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