-
Notifications
You must be signed in to change notification settings - Fork 312
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
vitest support for CI #2366
Comments
+1 on the request please. |
👍 on this one |
🙏 |
👍 vitest is gaining more and more traction as a replacement of jest. |
Today I was wondering "why did my tests stop showing up in Datadog" and I realized it is because I haven't published a repo that uses jest in several weeks. All my most recent code is using vitest. It is basically a must for the Vue framework and the support for module syntax is superior. And performance. So fast I am an every day Datadog user. This will not stop me from using Datadog but I will not be able to make full use of CI. Using vitest is more necessary to my workflow than seeing it in Datadog |
adding another comment here to request support. is there any traction on this front that can be surfaced here? |
hi everyone! Good news: this is currently being worked on in #4415. It's still going to take a bit but vitest support is coming 😄 |
🎉 🚢 vitest support is now released in |
until we update the docs with the instructions, here's how you can try the vitest integration:
Make sure the Then run your vitest tests passing
For example, if your "scripts": {
"test": "vitest run"
} Run
Take into account that you'll still need an API key or a running agent (see docs for more info) |
@juan-fernandez Thanks for the amazing work getting this done! Does this mean, we can also use I doesn't look like it works, at least running |
thanks for the feedback @thuringia ! It's indeed impossible at the moment to report code coverage to datadog if you're using |
Is there an open issue to track code coverage through |
@karrui total code coverage for |
ℹ️ docs are updated too 😄 : https://docs.datadoghq.com/tests/code_coverage?tab=javascripttypescript#vitest |
Thx! does |
yeah, it should work. Feel free to open an issue. It'll be much easier to fix a potential bug with a reproducible case 😄 |
This is the PR, I'm able to share it since it's open sourced! |
thanks! That's helpful |
vitest is a new test framework similar to Jest that runs on top of Vite.
It would be great if dd-trace-js could instrument vitest similar to how the Jest integration works.
The text was updated successfully, but these errors were encountered: