-
-
Notifications
You must be signed in to change notification settings - Fork 878
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
Tests: src/resolvers/Mutation/addUserToUserFamily.ts #1817
Comments
I would like to work on this |
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
@NayOoLwin5 Are you working on this? |
Yes, I will be submitting PR soon. |
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
Unassigning as abandoned |
@palisadoes, please assign this. I'll create a PR rn. |
@Cioppolo14, please assign. I've fixed this already |
@pranshugupta54 Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. We sometimes give exceptions for more urgent cases and sometimes we lose track, but the policy stands. You have reached your limit, please wait until your existing issues are closed before requesting more issues. You could unassign yourself from one of the other issues too. |
@Cioppolo14, I know I'm assigned to |
@Cioppolo14, PR got merged. Please assign. |
The Talawa-API code base needs to be 100% reliable. This means we need to have 100% test code coverage.
src/resolvers/Mutation/addUserToUserFamily.ts
tests/
with a.spec.ts
suffix.IMPORTANT:
Please refer to the parent issue on how to implement these tests correctly:
PR Acceptance Criteria
codecov.io
to help with testing.Other
Please coordinate issue assignment and PR reviews with the contributors listed in this issue:
The text was updated successfully, but these errors were encountered: