Skip to content

Unit tests for transactions microservice #35

@jashmehta3300

Description

@jashmehta3300

Expected Behavior

For each code unit, it is essential to have an associated test. Incorporating these tests is crucial for evaluating whether subsequent pull requests (PRs) introduce any regressions or issues.

Actual Behavior

Currently, there are no unit tests present for the 'transactions' microservice.

Checklist

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is neededpythonPull requests that update Python code

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions