-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Show incremental progress when running tests #6407
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
Comments
the real time updates to individual test's status was working in https://marketplace.visualstudio.com/items?itemName=LittleFoxTeam.vscode-python-test-adapter. I had used this extension before the MS python extension provided its own implementation of Test explorer |
We are going through old issues and we noticed that no one from the team had replied to this issue. I want to apologize for the oversight and to let you know that the issue was reviewed by the team and triaged (as shown by the labels applied to this issue). |
Thanks @brettcannon |
This would be a major improvement. waiting for 100+ tests to finish before being able to know what failed is a big pain |
Fixed by #16769 but only for unittest framework, not pytest. |
This will be done with the test adapter improvements for pytest. The UI itself now handles individual test progress. |
Can you please give us an update about the adapter status? |
It's great to see the improvements in the test area !! |
I am having the same problem.
Also I really miss the play button in gutter next to the test class to run
all the tests
…On Tue, Sep 14, 2021, 18:57 François Steinmetz ***@***.***> wrote:
It's great to see the improvements in the test area !!
The incremental test progress seems to work, but not always. When
launching parametrized pytests through the gutter button, I see incremental
status appearing. In the explorer, I can also click several tests, one by
one, which are run in parallel with incremental progress. However, when
running all tests in a file or in a project, the status only appears when
all tests are done.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#6407 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHIYG2PUCO7SD72PZXC6ELUB5WFPANCNFSM4H4ZDVSQ>
.
|
Is there a specific area or issue exist for Test Adapter? Could you link it here please as all searches end up with current ticket. |
@DmytroSokhach #17242 item tracks the progress on the test adapter re-write. |
Has this been solved? I can't really see any sort of progress indication on parameterized pytests, and it is fairly frustrating when there's many of them and they take some time to run... |
Hello! This will soon be a feature following our testing rewrite. Our rewrite is out on insiders using the setting |
Thank you very much for the clear and thoughtful answer!
…On Thu, Jun 22, 2023 at 9:54 PM Eleanor Boyd ***@***.***> wrote:
Hello! This will soon be a feature following our testing rewrite. Our
rewrite is out on insiders using the setting "python.experiments.optInto":
["pythonTestAdapter"],. Once this PR is merged: #21466
<#21466> and you enable
the rewrite, this feature will work. The rewrite will progressively be
shipped to more customers as we are shifting all users to the rewrite but
are in the incremental stages at the moment.
—
Reply to this email directly, view it on GitHub
<#6407 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHIYG5TNMEJ4JIPJS2FQETXMSIFLANCNFSM4H4ZDVSQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Itamar Sharify
Software Engineer
|
this is now out on stable with the experiment turned on and therefore I am closing this as resolved. Thanks! |
When running many tests from the TEST:PYTHON sidebar, all tests are shown to be in progresss (spinning arrow) until all tests have been run.
It would be much nicer if the spinning arrow icon is updated as soon has the test has run. In the Python Test Log this information is readily available, so you can directly see which tests have passed, failed, are running now or are scheduled to be run.
Possibly related to #1718, but that is more about the spinner in the bottom bar
The text was updated successfully, but these errors were encountered: