Module and class headings are to late on stdout

I would name line #4 the module heading and line #5 the class heading

The output from line 2 & 3 comes from the setUpClass() method.

I would assume that the heading for module is print to stdout before setUpModul() is called and the heading for the class before the call of setUpClass().

What do you think?

[CleanCut]

I finished my investigation. Green has never supported capturing output from module/class setups or teardowns, despite me thinking I had implemented that. Though I would like to add this as a feature, it is extremely difficult and I am not planning on taking it on. If someone would like to give it a try, I’d be happy to collaborate on a pull request. The place to start is green/suite.py in GreenTestSuite.run.

The workaround is: Don’t write to stdout/stderr in class/module setups or teardowns.

I updated the documentation for -a/--allow-stdout to point out that we only capture output for tests, not setups and teardowns.

[CleanCut]

No problem! Sorry I couldn’t provide a more satisfying response in this instance. This is the drawback of hitching Green to unittest – having to deal with it’s internal implementation. On the other hand, there’s no barrier to using Green nor any “vendor lock-in”. Always tradeoffs!