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/EventManagement from Jest to Vitest #2546

Closed
VanshikaSabharwal opened this issue Dec 1, 2024 · 10 comments
Closed

Refactor: src/screens/EventManagement from Jest to Vitest #2546

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

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/EventManagement 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
@Adhish1612Acharya
Copy link

Hello @palisadoes ,

I would like to work on this issue. Could you please assign it to me?

@shivasankaran18
Copy link
Contributor

@Adhish1612Acharya are you still working on this..?..can I work on it

@palisadoes
Copy link
Contributor

Unassigning. Inactive and no PR

@palisadoes
Copy link
Contributor

palisadoes commented Jan 3, 2025

  1. @prathmesh703 You should work on this issue too
  2. Ask to be assigned

@prathmesh703
Copy link
Contributor

sure , @palisadoes you can assign this issue to me

@shivasankaran18
Copy link
Contributor

can I work on this issue ..? @palisadoes @Cioppolo14

@prathmesh703
Copy link
Contributor

@shivasankaran18 i have completed the work of this issue and is linked in PR which also resolves the other issue

@Cioppolo14
Copy link
Contributor

@prathmesh703 If your still working on the issue, please do not unassign yourself.

@Cioppolo14
Copy link
Contributor

@prathmesh703 I am going to reassign you this item, but please do not repeat this strategy.

@prathmesh703
Copy link
Contributor

@Cioppolo14 sorry for this thing , actually i have made a PR(#3149) for this issue and for other issue(#3024) that's why i have unassigned myself from this issue and asked you to assign another issue.

@github-project-automation github-project-automation bot moved this from Backlog to Done in Talawa-Admin (Tests) Jan 9, 2025
@github-project-automation github-project-automation bot moved this from Backlog to Done in Talawa Admin - Refactoring Jan 9, 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 refactor Refactor the code to improve its quality test Testing application
Projects
Status: Done
Archived in project
Development

No branches or pull requests

7 participants