Display py.test results as they come in #91
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This will allow us to define hooks to report status while the test suite is being run.
Necessary because Python does not flush stdout automatically if run non-interactively.
This functionality was lost in the model/view split.
|
After: Before: |
|
This is very nice work @jitseniesen, I like it :-). |
|
@jitseniesen maybe we should change the name from |
jitseniesen
force-pushed
the
realtime
branch
from
45b0559
to
b35a099
Compare
On Windows, access to the underlying binary buffer is required.
jitseniesen
force-pushed
the
realtime
branch
from
80cf885
to
244702d
Compare
|
Great addition @jitseniesen! |
Otherwise py.test thinks that classes like TestDetails contain tests and emits a warning message.
Good idea --> #92 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The goal of this pull request is to give the user continuous feedback on the test run, instead of waiting till the end before displaying any results. I find it curiously satisfying to see the count of successful test go up and up. 😉 This required a change in the design: instead of parsing the JUnitXml (which is generated after the test run), the plugin now interacts with py.test's API.
This turned out to be more work than I expected, but it is almost done now. Hopefully the new design will pay back in the future.
To do:
RunnerBase.start()andPytestRunner.start()RunnerBasetoNoseRunnerFixes #13
Fixes #50