Skip to content
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

Refactor: src/screens/OrgPost from Jest to Vitest #2566

Open
VanshikaSabharwal opened this issue Dec 1, 2024 · 5 comments
Open

Refactor: src/screens/OrgPost from Jest to Vitest #2566

VanshikaSabharwal opened this issue Dec 1, 2024 · 5 comments
Assignees
Labels
good first issue Good for newcomers no-issue-activity No issue activity refactor Refactor the code to improve its quality test Testing application unapproved

Comments

@VanshikaSabharwal
Copy link
Contributor

Is your feature request related to a problem? Please describe.
This file is currently tested using Jest. As part of our migration to Vitest, we need to refactor this file's test cases to align with Vitest's syntax and features.

Acceptance Criteria

  1. Replace Jest-specific functions and mocks with Vitest equivalents
  2. Ensure all tests in src/screens/OrgPost pass after migration using npm run test:vitest
  3. Maintain the test coverage for the file as 100% after migration
  4. Upload a video or photo for this specific file coverage is 100% in the PR description

Additional context

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

@github-actions github-actions bot added documentation Improvements or additions to documentation refactor Refactor the code to improve its quality test Testing application unapproved labels Dec 1, 2024
@palisadoes palisadoes added good first issue Good for newcomers and removed documentation Improvements or additions to documentation feature request labels Dec 3, 2024
@bandhan-majumder
Copy link
Contributor

Hi @palisadoes . Can I work on this ?

@dhanagopu
Copy link

@bandhan-majumder 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. 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.

@Nirvanjha2004
Copy link

Nirvanjha2004 commented Dec 14, 2024

@dhanagopu @palisadoes can i work on this issue

@Nirvanjha2004
Copy link

update on issue #2566 -

  1. completed the migration from jest to vitest
    image

Copy link

github-actions bot commented Jan 4, 2025

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.

@github-actions github-actions bot added the no-issue-activity No issue activity label Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers no-issue-activity No issue activity refactor Refactor the code to improve its quality test Testing application unapproved
Projects
Status: Backlog
Status: Backlog
Development

No branches or pull requests

5 participants