-
Notifications
You must be signed in to change notification settings - Fork 97
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
Vscode standardized test system #272
Comments
Yeah, I'm pretty sure that this will take a while, if it will make it at all. |
@GeorchW Please make sure you upvote so that we can get this in and tell your friends. Still need 3 more people! |
I think we can close this issue. |
@GeorchW why? It's made it into the backlog for vs code. |
It looks like there's a new spot where they are tracking the design of the new API. Hey @stefanforsberg, they are taking input from the community since end Sept. Might be worth checking over what they have so far. I'll try work my way through it over the next couple weeks also. |
any plan to deal with? |
Would love to see this extension updated to support the built-in VSCode testing. https://code.visualstudio.com/api/extension-guides/testing
|
Hmm, I'd love to work on this, but time is kinda tight right now. If I had a few weeks without active side projects, I could probably do this besides the job. But I fear that this won't be the case for at least another month or two, maybe even longer... :-/ |
There is some ongoing discussion regarding a standardize way to handle test framework in vscode here microsoft/vscode#97919.
@GeorchW I have a feeling that this implementation (of the team choose to act upon it) is still long-isch in the future but regarding the discussion we've been having lately it can be good to have at the back of the head when we are discussing possible development for the extension.
The text was updated successfully, but these errors were encountered: