Add new options to report fixture setup and teardown#1647
Conversation
Factor setuponly code out of runtestprotocol().
Add printing of fixture dependencies
* Fix the tests * Fix .format string failures on python 2.6
3 similar comments
| config = self._fixturemanager.config | ||
| capman = config.pluginmanager.getplugin('capturemanager') | ||
| if capman: | ||
| capman.suspendcapture() |
There was a problem hiding this comment.
Some earlier PR of @nicoddemus did the same, but did out, err = capman.suspendcapture() and then printed out/err to stdout/stderr after resuming capturing, as to not lose any captured content. Wouldn't the same apply here as well?
There was a problem hiding this comment.
You're right, we didn't realise that .suspendcapture() + .resumecapture() loses the output unless explicitly passed through. Fixed.
|
I haven't investigated yet, but I get this with |
|
Your qutebrowser test error is caused by |
|
@The-Compiler the qutebrowser issue should be fixed by the last commit. |
|
Interestingly enough this now triggers a segfault in Qt/PyQt 😆 Pretty sure that's not your fault though. |
|
The segfault happens in this line: Where |
|
That seems like a PyQt issue indeed, reported to their mailing list. |
Also, changed their group from "general" to "debugconfig".
|
thanks! |
This PR implements the cli flags to show potential fixtures without actually executing it (
--setup-plan) and actually testing all the setup and teardown of fixtures without executing the test functions (--setup-only).Here's a quick checklist that should be present in PRs:
master; for new features, targetfeaturesAUTHORSCHANGELOG(choose any open position to avoid merge conflicts with other PRs)