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

Enable parallel tests in vitest #539

Merged
merged 3 commits into from Mar 14, 2023
Merged

Enable parallel tests in vitest #539

merged 3 commits into from Mar 14, 2023

Conversation

LudvigHz
Copy link
Member

@LudvigHz LudvigHz commented Feb 14, 2023

By using a separate DB in mongo for each thread, we can easily
parallelize all tests.

Resolves ABA-229

Copy link
Contributor

@PeterJFB PeterJFB left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm 🦔 👍

@LudvigHz LudvigHz force-pushed the parallel-tests branch 2 times, most recently from 940294c to 2f5381e Compare February 17, 2023 14:12
@linear
Copy link

linear bot commented Feb 18, 2023

ABA-229 Parallelize tests

Vitest is super easy to parallelize.

We need to make the tests thread safe and work in parallel. I would suggest the easy method and just use a separate test DB for each thread. Just need to modify the setup function for vitest to connect to the right db.

By using a separate DB in mongo for each thread, we can easily
parallelize all tests.
@LudvigHz LudvigHz force-pushed the parallel-tests branch 5 times, most recently from 3e6a9db to 66649f7 Compare March 14, 2023 18:14
This makes testing alot easier. Also a nice to have.
Also remove annoying mongoose deprecation warnings.
@LudvigHz LudvigHz enabled auto-merge March 14, 2023 18:40
@LudvigHz LudvigHz merged commit bbaa9c5 into master Mar 14, 2023
@LudvigHz LudvigHz deleted the parallel-tests branch March 14, 2023 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants