[Pytest-commit] Issue #541: Can't use pytest.mark.parametrize inside unittest class (hpk42/pytest)

2014-07-16 Thread d3ph
New issue 541: Can't use pytest.mark.parametrize inside unittest class https://bitbucket.org/hpk42/pytest/issue/541/cant-use-pytestmarkparametrize-inside d3ph: ``` #!python def test_parametrize_unittest(testdir): testpath = testdir.makepyfile(""" import unittest import pytes

[Pytest-commit] commit/pytest: gutworth: avoid importing old assertion interpretation code by default (fixes #537)

2014-07-16 Thread commits-noreply
1 new commit in pytest: https://bitbucket.org/hpk42/pytest/commits/18e7ceb385f8/ Changeset: 18e7ceb385f8 User:gutworth Date:2014-07-17 02:21:18 Summary: avoid importing old assertion interpretation code by default (fixes #537) Affected #: 2 files diff -r bc61fe662fa32521ea

[Pytest-commit] Issue #542: Doesn't appear to be a supported way for plugins to detect test failures at teardown (hpk42/pytest)

2014-07-16 Thread virtuald
New issue 542: Doesn't appear to be a supported way for plugins to detect test failures at teardown https://bitbucket.org/hpk42/pytest/issue/542/doesnt-appear-to-be-a-supported-way-for virtuald: What I'd like to be able to do is write a pytest plugin that would check proper usage of a fixture a