On Tue, Jan 10, 2012 at 9:06 AM, Graham Binns <email address hidden> wrote:
> Public bug reported:
>
> What happens:
> If you run the Launchpad tests with --subunit, it will report the layer setup and teardown notices as tests, which they aren't. This leads to test count inflation, which gets very confusing for developers (especially when you're running parallel tests, which means that you add about 20 such notices per lxc instance).
>
> Proposed solution (from lifeless):
> - Update the zope.testing subunit support so that layer setup and teardown messages are tagged with "layer".
> - Subunit needs to know about tags.
> - Testr needs to not count or record layer-tagged things as tests.
> - Testr should still dump the layer-tagged messages to the raw stream on disk.
Some thoughts:
* zope.testing already outputs a 'zope:layer' tag after emitting the
start of the test that represents the layer
* It treats layers as tests to provide a place to put layer
setUp/tearDown errors
* It would be nicer for testr to not know about layers, but rather to
achieve the same result with (not yet existing) subunit filtering
tools
On Tue, Jan 10, 2012 at 9:06 AM, Graham Binns <email address hidden> wrote:
> Public bug reported:
>
> What happens:
> If you run the Launchpad tests with --subunit, it will report the layer setup and teardown notices as tests, which they aren't. This leads to test count inflation, which gets very confusing for developers (especially when you're running parallel tests, which means that you add about 20 such notices per lxc instance).
>
> Proposed solution (from lifeless):
> - Update the zope.testing subunit support so that layer setup and teardown messages are tagged with "layer".
> - Subunit needs to know about tags.
> - Testr needs to not count or record layer-tagged things as tests.
> - Testr should still dump the layer-tagged messages to the raw stream on disk.
Some thoughts:
* zope.testing already outputs a 'zope:layer' tag after emitting the
start of the test that represents the layer
* It treats layers as tests to provide a place to put layer
setUp/tearDown errors
* It would be nicer for testr to not know about layers, but rather to
achieve the same result with (not yet existing) subunit filtering
tools
jml