[Pytest-commit] Issue #468: guaranteed print to stdout and stderr (hpk42/pytest)

2014-02-26 Thread m27315
New issue 468: guaranteed print to stdout and stderr https://bitbucket.org/hpk42/pytest/issue/468/guaranteed-print-to-stdout-and-stderr m27315: Occasionally, it is desirable to print directly to stdout and stderr, regardless of '-s' switch invocation. For example, one may want to print an occa

[Pytest-commit] Issue #470: Crashes when too many things fail? (hpk42/pytest)

2014-02-26 Thread kwpolska
New issue 470: Crashes when too many things fail? https://bitbucket.org/hpk42/pytest/issue/470/crashes-when-too-many-things-fail kwpolska: I’m testing [Nikola](http://getnikola.com/). I tried [this file](https://github.com/getnikola/nikola/blob/master/tests/test_integration.py): ``` $ py.test

[Pytest-commit] Issue #469: junitxml parses report.nodeid incorrectly (hpk42/pytest)

2014-02-26 Thread Andrei Baidarov
New issue 469: junitxml parses report.nodeid incorrectly https://bitbucket.org/hpk42/pytest/issue/469/junitxml-parses-reportnodeid-incorrectly Andrei Baidarov: If test param contains '::' junitxml parses report.nodeid incorrectly. For example, for test ``` #!python import pytest @pytest.mark.

[Pytest-commit] Issue #153: Support running tests on an existant virtual environment (hpk42/tox)

2014-02-26 Thread klmitch
New issue 153: Support running tests on an existant virtual environment https://bitbucket.org/hpk42/tox/issue/153/support-running-tests-on-an-existant klmitch: We have a situation where we need to build our own virtual environment, then run tests within that virtual environment to validate it fo