-
Notifications
You must be signed in to change notification settings - Fork 33
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
Add Proper Unit Test Coverage #12
Comments
/bounty 150 |
💎 $150 bounty • Permit.ioSteps to solve:
Thank you for contributing to permitio/permit-cli! Add a bounty • Share on socials
|
New Quest!A new Quest has been launched in @permitio’s repo. Loot of 250 USD has been stashed in this issue to reward the solver! 🗡 Comment ⚔️ When you submit a PR, comment Questions? Check out the docs. |
/attempt #12 Options |
@quest-bot embark |
@varshith257 has embarked on their Quest. 🗡
This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR. Questions? Check out the docs. |
@quest-bot embark |
@sachinks07 has embarked on their Quest. 🗡
This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR. Questions? Check out the docs. |
@gemanor How do you feel about using Jest for the tests, if we use it, I can start working on this right away. Also should we also use something like Codecov together with Jest for ensuring coverage, or just Jest with GitHub Actions is fine? |
@Neptune650 I have done progress on it integrating Jest. Just left with the task of increasing code coverage. Increases to 70 till now :) PS: Updated progress so that we don't make duplicate efforts IMAO |
@quest-bot embark |
@Bhavyajain21 has embarked on their Quest. 🗡
This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR. Questions? Check out the docs. |
🧚 @varshith257 has submitted PR #23 and is claiming the loot. Keep up the pace, or you'll be left in the shadows. Questions? Check out the docs. |
Seems like @varshith257 is the only one working on it. @sachinks07 are you planning to submit something or can I assign @varshith257 |
@gemanor I think you an assign me. I have already covered good coverage of 85% as of now |
I think there are few bugs in login.tsx and policy.tsx, I think there needed fixes |
@gemanor You can assign to @varshith257 |
@quest-bot embark |
@naaa760 has embarked on their Quest. 🗡
This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR. Questions? Check out the docs. |
Is there any work left on tests? I am willing to contribute if needed. |
hey @gemanor, is this issue still open, else i can work on it, as no-one is assigned to it Few resource on how these test case looks: Let me know your views on it |
🧚 @varshith257 has submitted PR #34 and is claiming the loot. Keep up the pace, or you'll be left in the shadows. cc @Bhavyajain21 Questions? Check out the docs. |
/attempt #12 Options |
Related to permitio#12 Add unit tests and integrate Jest for 90% code coverage. * **Add Jest and Update Configuration** - Add Jest as a dev dependency in `package.json`. - Update the `test` script to use Jest. - Add Jest configuration to `package.json`. * **Update GitHub Actions Workflow** - Add a step to run Jest tests in `.github/workflows/node.js.yml`. - Add a step to generate coverage reports. * **Add Unit Tests** - Add unit tests for `ApiKey` component in `source/commands/apiKey.test.tsx`. - Add unit tests for `Login` component in `source/commands/login.test.tsx`. - Add unit tests for `Logout` component in `source/commands/logout.test.tsx`. - Add unit tests for `Policy` component in `source/commands/opa/policy.test.tsx`. - Add unit tests for `Check` component in `source/commands/pdp/check.test.tsx`. - Add unit tests for `Run` component in `source/commands/pdp/run.test.tsx`. - Add unit tests for `AuthProvider` component in `source/components/AuthProvider.test.tsx`. - Add unit tests for `PDPCommand` component in `source/components/PDPCommand.test.tsx`. * **Update Documentation** - Add instructions for running tests locally in `README.md`. - Add instructions for writing new tests in `README.md`.
/attempt #12
|
/attempt #12
|
@quest-bot embark |
@Abiji-2020 has embarked on their Quest. 🗡
This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR. Questions? Check out the docs. |
🧚 @Abiji-2020 has submitted PR #43 and is claiming the loot. Keep up the pace, or you'll be left in the shadows. cc @varshith257 Questions? Check out the docs. |
💡 @Abiji-2020 submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
@quest-bot embark |
@ayimdomnic has embarked on their Quest. 🗡
This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR. Questions? Check out the docs. |
@quest-bot embark |
@ARYPROGRAMMER has embarked on their Quest. 🗡
This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR. Questions? Check out the docs. |
🧚 @ARYPROGRAMMER has submitted PR #46 and is claiming the loot. Keep up the pace, or you'll be left in the shadows. cc @varshith257 Questions? Check out the docs. |
This issue is about getting to 90% coverage for the Permit CLI. The current tests use only Node test runner and do not pass completely, so the task is also to stabilize the tests and choose the right tooling for efficient unit test writing.
Acceptance Criteria:
The text was updated successfully, but these errors were encountered: