Add unittest\pytest directly to debug option

[twiggy]

In other Python IDE extensions running tests is directly integrated into the run/debug settings.

In VSCode it seams like you have to "discover" all your tests with the testing/beaker tab/sidebar.

I'm in a mono repo so I'm basically not able to use this as the configure tests as it just allows a top level folder. I have 1000s of varying types etc. So running suites of tests in my IDE is generally not very useful. Builds do it, or if I really need to I'm running complex scripts that run them in parallel etc.

In short I generally have a single test I want to run, and more precise a function in a file that is a test. Some tests are more like integration or end to end tests that don't really fit into the run 100s of tests in the IDE paradigm.

In pyDev I can just open the test file I want, and when I go to debug it ( just hit ctrl+f9) I get an option dialog.

a decent work around is to

if __name__ == "__main__":
    unittest.main()    

in the unit test file and then it will run the tests. there are ways to have it only do one function as well, but does require a bit of cleanup when done debugging.

Thanks!

[eleanorjboyd]

Hi, so to clarify you are trying to run single tests but it is hard to do given you have so many tests? Is the time discovery takes the issue with the test explorer view? Are you looking for ways to specify settings per workspace for testing?

[github-actions]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

Happy Coding!