-
-
Notifications
You must be signed in to change notification settings - Fork 655
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
Resolvers: Create tests for updateOrganization.js #552
Comments
can you assign this to me |
You already have 3 issues assigned. Please focus on closing those. |
Two issues are already approved and merged and I've made a PR for the 3rd issue too. So now I can work on a new issue |
Why aren't the issues closed? |
can i close it by myself as the PRs are merged? |
There is an autoclosing feature in GitHub. It's outlined in the CONTRIBUTING.md file. |
Please use the templates that we provide for submitting your PRs. They are there for a reason. In this case, the issues would have been closed automatically. |
The time of our contributors and reviewers is valuable. I'm sure you understand. The procedures are put in place to help everyone, you included. Please follow the process in future. I'll assign the issue |
yes, I understand. sorry for missing these details, I'll keep this in mind from now on. |
The Talawa-API code base needs to be 100% reliable. This means we need to have 100% test code coverage.
Tests need to be written for file
lib/resolvers/organization_mutations/updateOrganization.js
single file with the name
tests/resolvers/organization_mutations/updateOrganization.spec.js
. You may need to create the appropriate directory structure to do this.IMPORTANT:
Please refer to the parent issue on how to implement these tests correctly:
PR Acceptance Criteria
The text was updated successfully, but these errors were encountered: