-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Add Testing doc #5332
base: vnext
Are you sure you want to change the base?
Add Testing doc #5332
Conversation
It'd be nice if we could link this doc under both sections, TypeScript as well as Node.js/JavaScript. Testing frameworks looks good 🙂 |
The Node.js/JavaScript topics get about 3x the page views of the TypeScript TOC topics so for discovery it might be better to put the page there. We can have an entry in the TypeScript TOC which jumps to the topic under Node.js/JavaScript. |
@isidorn - our Wallaby.js extension was one of the first VS Code extensions in the marketplace. While we provide a commercial product, we also provide free licenses for open source projects and think it could be really beneficial to mention us for JavaScript/TypeScript testing. Thinking a little more about it, would be good to list a number of popular extensions directly on the page to help developers get started. If you agree on adding test runner content, we'd be happy to write a section about Wallaby for you. |
@gregvanl I love that idea. Moving the doc there then. How do I add it to the typescript TOC, I did not find a toc.json like the API section has? @smcenlly thanks for reaching out. I like your idea that we should list all the test extensions. Maybe we can have a section at the end that lists all the others. |
@isidorn - we started using the testing API very shortly after it was released and were an early adopter. I also made some contributions to the Testing API shortly after it was released (microsoft/vscode#132097, microsoft/vscode#132099). |
@smcenlly I was not aware of this, thanks for clarifying! If that works for you then a contribution would be very welcome :) |
@isidorn For a TOC redirect item, you can add a placeholder topic that specifies the TOC placement (Order:) and title (TOCTitle:) |
I couldn't work out how to make an edit to this pull request but have proposed an adjustment to Testing Node.jsVisual Studio Code supports testing Node.js and TypeScript through it's testing framework. You will need to have the right testing extension based on the testing framework that your project uses. MochaThe Mocha Test Explorer allows you to run your Mocha tests in the Sidebar of Visual Studio Code using the Test Explorer UI. PlaywrightPlaywright Test for VSCode allows you to run Playwright tests in Visual Studio Code. JestThe Jest VS Code Extension allows you to run your Jest tests in Visual Studio Code. VitestThe Vitest VS Code Extension allows you to run your Vitest tests in Visual Studio Code. Other extensionsThere are other extensions that support testing in Visual Studio Code. You can find them in the Visual Studio Code Marketplace. Some popular ones are listed below. Wallaby.jsWallaby.js works with most JavaScript testing frameworks and runs your tests immediately as you type, highlighting results right next to your code. It is a paid product for commercial use, but is free for open source projects. |
@smcenlly thanks a lot! Assigning to October so we wrap this up then. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
This PR adds a skeleton for the Testing doc, so we have a location to make progress on this.
@connor4312 @gregvanl where do you think should this document live? Currently I put it under Typescript, but all of this also holds true for Javascript. We do not have a big Javascript section, only nodejs? So alternatively it could be under nodejs, and the Typescript one would only link to that. What do you think?
@MarcusFelling said he can help with the Playwright content
@connor4312 I added sections for the popular testing frameworks, if you think something else should also be covered let me know.
fyi @DanielRosenwasser