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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

vitest doc section for VS Code #32

Open
isidorn opened this issue May 11, 2022 · 8 comments
Open

vitest doc section for VS Code #32

isidorn opened this issue May 11, 2022 · 8 comments
Labels
p2-nice-to-have Not breaking anything but nice to have (priority)

Comments

@isidorn
Copy link

isidorn commented May 11, 2022

Hi VS Code PM here 馃憢

We are currently in the process of making the testing story more discoverable in vscode.
As part of that we are writing docs for the VS Code testing framework, and we really like your testing extension and we want to have a section on it.

This is the draft PR microsoft/vscode-docs#5332
Do you have some good docs to point us to that we could reuse? Or would you like to contribute to our PR directly?

Thanks

@isidorn isidorn added the p2-nice-to-have Not breaking anything but nice to have (priority) label May 11, 2022
@zxch3n
Copy link
Member

zxch3n commented May 12, 2022

Thanks! I'm happy to help. Is this doc about quickly setting up tests in VS Code for TypeScript projects?

@isidorn
Copy link
Author

isidorn commented May 12, 2022

@zxch3n awesome! Yeah setting up tests for TypeScript projects is something that we are aiming for.
Covering also nodeJs would work. I am not sure how specific each of those flows are?

@zxch3n
Copy link
Member

zxch3n commented May 12, 2022

Users can follow the guide here to set up Vitest. It works for both TypeScript and NodeJS out of the box, and you can try it online on StackBlitz.

@isidorn
Copy link
Author

isidorn commented May 12, 2022

@zxch3n then I suggest that the docs in VS Code just link to that guide and add some VS Code specifics. Like what extension is needed etc... What do you think?

@zxch3n
Copy link
Member

zxch3n commented May 12, 2022

Yeah, I agree. I'll contribute to the PR by tomorrow

@isidorn
Copy link
Author

isidorn commented May 13, 2022

No rush. Looking forward to it. Thanks!

@sheremet-va
Copy link
Member

@isidorn is it something that you are still working on?

@isidorn
Copy link
Author

isidorn commented Mar 27, 2024

Unfortunately no. But we are open to PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p2-nice-to-have Not breaking anything but nice to have (priority)
Projects
None yet
Development

No branches or pull requests

3 participants