-
Notifications
You must be signed in to change notification settings - Fork 136
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
[GOFLOW-31] Unit testing and coverage are missing #31
Comments
@giorgiozoppi This is where I need help. I didn't had enough bandwidth to look at the project recently. Do you have any idea how we can start ? |
I would start from the lower level possibile. Is that the datastore? I also use this way of doing tickets for matching branches. |
We need to test this first This has all core functionalities |
Ok, i branch out, please use the same schema to rename different issues. The name of teh banch will be feature/goflow-31-unit-testing. |
Lets use - issue-31
…On Sat, 11 Mar 2023 at 23:01, Giorgio Zoppi ***@***.***> wrote:
Ok, i branch out, please use the same schema to rename different issues.
The name of teh banch will be feature/goflow-31-unit-testing.
—
Reply to this email directly, view it on GitHub
<#31 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABYIJ2REFCFQQQTV2TPKO73W3SOUJANCNFSM6AAAAAASGAASJE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Branched out, i start working on this. |
Goflow: Unit testing and coverage
Goal
Provide a 95% unit test mocking where it's opportune with gomock. No tests are present in the current code base.
The text was updated successfully, but these errors were encountered: