new pytests cannot be triggered or queued while previous ones are running

[danieltuzes]

I have multiple python tests set up, and VS Code testing tab finds them and individually or all together can be executed. The success or failure is successfully detected and displayed.

However, if I trigger one test from VS Code, and then want to queue or trigger another test before the previous one finishes, while it shows up on the test results tab next to the terminal, it is never executed.

In this example a test is executed at 1:54:50, and while running, I wanted to trigger or queue another 2 tests at 2:05:40 and at 2:06:25. There is no message in the TEST RESULTS tab for these 2 tests, only for the first test. After the first test completes, the tests I wanted to trigger at 2:05 and 2:06 are never executed.

Versions:
VS Code 1.82.2
python extension from MS: 2023.22.1
pylance: 2023.12.1

[eleanorjboyd]

Will try and repo and take a look. We do not have the idea of "queued" instead all new requests while one is running will be canceled. This being said the icon coming up in the results tab is not ideal. Will look into that. If you want the "queued" feature you can open another issue and just label it as a feature request, thanks

[danieltuzes]

Thank you for the explanation! As far as I remember in some previous versions I was able to trigger (or queue, I didn't check) new test runs while old ones were running. So you say that the expected behavior is to neglect (or simply delete) the request of new tests? The most straightforward could be that new test triggering is disabled while old tests are running.

Thanks for the idea for submitting a feature request!

[eleanorjboyd]

Hi! Just confirmed this was not possible with the prior design, @connor4312 is this something that core has considered? I could queue them from my side but didn't know if this has been discussed at the vscode level.

[github-actions]

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

[connor4312]

We don't have any global behavior for this, it's up to the extension to queue them if it can't run tests concurrently.

[eleanorjboyd]

Given this, @danieltuzes it will stay a feature request and if it gets enough votes from the community will enter our backlog and will be prioritized based on upvotes. Thanks!

[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!

[eleanorjboyd]

Thank you for submitting your feature request and everyone who considered it! Unfortunately, this issue did not receive enough votes over the allotted time, and so we are closing the issue. PRs are welcome so you can create a PR that fixes this if you are passionate about getting this feature across the finish line. Thanks!