Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor: central-settlement cgs handler unit tests assertion framework to jest #2095

Closed
10 tasks
vgenev opened this issue Mar 3, 2021 · 0 comments
Closed
10 tasks
Labels
no-longer-applicable This has evolved and has been replaced or this is based on outdated design/implementation story

Comments

@vgenev
Copy link

vgenev commented Mar 3, 2021

Goal:

As a OSS code contributor

I want to refactor the central-settlement tests

so that the narrow integration tests uses the jest native assertion framework

Acceptance Criteria:

  • cgs handler tests are using jest as only test and assertion framework

Complexity:

Uncertainty:


Tasks:

  • TBD [ @? ]

Done

  • Acceptance Criteria pass
  • Designs are up-to date
  • Unit Tests pass
  • Integration Tests pass
  • Code Style & Coverage meets standards
  • Changes made to config (default.json) are broadcast to team and follow-up tasks added to update helm charts and other deployment config.
  • TBD

Pull Requests:

  • TBD

Follow-up:

  • N/A

Dependencies:

  • N/A

Accountability:

  • Owner: TBC
  • QA/Review: TBC
@vgenev vgenev added story oss-core This is an issue - story or epic related to a feature on a Mojaloop core service or related to it labels Mar 3, 2021
@elnyry-sam-k elnyry-sam-k added the no-longer-applicable This has evolved and has been replaced or this is based on outdated design/implementation label Jun 3, 2021
@elnyry-sam-k elnyry-sam-k removed the oss-core This is an issue - story or epic related to a feature on a Mojaloop core service or related to it label Jul 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-longer-applicable This has evolved and has been replaced or this is based on outdated design/implementation story
Projects
None yet
Development

No branches or pull requests

2 participants