-
Notifications
You must be signed in to change notification settings - Fork 252
StrykerJS + vitest #3465
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
Comments
Any updates for this? |
No, it is on the roadmap, but it will take some time to implement. Feel free to implement this feature if you want it to work sooner 😅 |
@nicojs sure I could take a stab at it, I'd probably need some context on how to build it, could you point me in that direction? |
Sure! I would love that! 💜 Instead of explaining it here inside this issue, I'm adding a big slap of documentation into our "create a plugin" guide: Please let me know what I can do to help! (you can also join our slack). If you want to contribute this plugin to the StrykerJS monorepo, you can look at our CONTRIBUTING.md to help you get started with our environment. |
We are working on possible solution! Please help us and upvote this issue vitest-dev/vitest#2167 |
Will be great to have this support, love mutation testing and your work here on Stryker, thanks. |
Hey @lbenie ✋ do you are working on this? I would love to help |
Hey man, no unfortunately I haven't had time to work on this. Seems like the stryker team took a jab at it though |
@rqbazan I think @TeunLamers looks like the person to ping if you're looking to help, looks like they were working on a prototype in October last year. |
Yes. @TeunLamers was a graduate student implementing Svelte support. Which is almost implemented (see PR). Unfortunately he had to drop Vitest support, because it was to much work to finish during his graduation assignment period. We still have support planned, I hope we can start on it in February |
Thanks for the update @nicojs :) Good luck @TeunLamers with your work for graduation |
Hi there, Any updates on vite support? Planning to implement it early on in a new project. Thanks! :) |
Hey, you should keep an eye on this pull request for vitest support! :) |
@TeunLamers Thank you! Does this also work with typescript? Hope your graduation went well! :) |
I succesfully graduated in late January and recently started working in mid March! Depending on your stack it will most likely work. The Vitest runner should work with Typescript projects because Typescript support is already build in StrykerJS. For Svelte projects Typescript does not work at the moment but is planned at a later date. This Pull request needs te be merged first for Svelte integration and Typescript support comes at a later date after that! |
@TeunLamers Good to hear! I also need to graduate this year. ^^ Even though I really like Svelte, I want to keep the Tech Stack more average with Vue, Storybook and .NET as backend. Not sure if or when we need to scale this project, so this setup will be probably the best for us. |
@SemSnel Good luck with your graduation! ^^ That seems like a solid stack! If you choose a different test runner StrykerJS will for sure work with Vue and Typescript. I have no clue how good testrunner integrations are with Vite besides Vitest so it might be worth the wait. |
Hey! I've seen that the PR for adding support for vitest has been merged. How is the status of this issue? Thanks! |
@DanielRamosAcosta how cool! I will try to implement and report back |
Thanks, everyone, for your patients. 🎉 The vitest runner is released: in v7.0.0 See https://github.com/stryker-mutator/stryker-js/releases/tag/v7.0.0 For the docs, see https://stryker-mutator.io/docs/stryker-js/vitest-runner/ If you have any issues, please let us know. A blog article about this release will be published following Monday. |
Amazing news, I'll see about adding this into a project :) |
Blog article here: https://stryker-mutator.io/blog/announcing-stryker-js-7/ |
Is your feature request related to a problem? Please describe.
I've been slowly migrating my projects to use
vite
as the config bundler. With that they recently introduced vitest which allows to share a common transformation pipeline during dev, build, and test time. I don't believe with the current mutators that it would work withvitest
as there are no runners forvitest
.Describe the solution you'd like
I don't know if it would be feasible to work with the
vitest
core dev team and allow astryker-js
configuration using vitest?Describe alternatives you've considered
unfortunately I don't see any
Additional context
none
The text was updated successfully, but these errors were encountered: