Feature Request: Kill Running Test

[tylerstillwater]

It is not uncommon for a misbehaving test to run for a long time, or indefinitely. It would be fantastic if there was a command/button/shortcut/some way to kill the currently running test.

[ramya-rao-a]

I am little busy at work, and may not be able to get to this any time soon, but this is a very useful feature to have.

PRs are welcome.

I can help out pointing people in the right direction if needed

[tylerstillwater]

Happy to take a peek. No idea where to start 😃 I'm sure I could figure it out if you get me pointed in the right direction. Thanks!!

…

On Aug 11, 2017, 6:30 PM -0600, Ramya Rao ***@***.***>, wrote: I am little busy at work, and may not be able to get to this any time soon, but this is a very useful feature to have. PRs are welcome. I can help out pointing people in the right direction if needed — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[ramya-rao-a]

There are 2 ways that I can think of to do this

• Have a status bar item that shows the status "Cancel Running Tests" that shows up when tests take say more than 5 seconds. Clicking on the status bar item should cancel the test.
• Another way is to use the integrated terminal to run the tests, maybe via tasks. That way the user can just hit Ctrl+C to cancel the process as everything in the terminal is interactive

[tylerstillwater]

Excellent. I love the status bar idea. Would you be able to point me in the right direction as to how to get started with putting something in the status bar?

…

On Aug 11, 2017, 6:40 PM -0600, Ramya Rao ***@***.***>, wrote: There are 2 ways that I can think of to do this • Have a status bar item that shows the status "Cancel Running Tests" that shows up when tests take say more than 5 seconds. Clicking on the status bar item should cancel the test. • Another way is to use the integrated terminal to run the tests, maybe via tasks. That way the user can just hit Ctrl+C to cancel the process as everything in the terminal is interactive — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[ramya-rao-a]

There already is a status bar that appears when the tests are run on save. Clicking on it shows the test output.

Look at the goCheck.ts file.

[tylerstillwater]

Perfect. I'll dig in. Thanks!

…

On Aug 16, 2017, 6:13 PM -0600, Ramya Rao ***@***.***>, wrote: There already is a status bar that appears when the tests are run on save. Clicking on it shows the test output. Look at the goCheck.ts file. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[ramya-rao-a]

This feature is out in the latest update to the Go extension (0.6.82) thanks to @tylerb!

[tylerstillwater]

Hooray! 🎉 Thanks @ramya-rao-a!