2009-11-26 02:50:39 +08:00
|
|
|
|
2009-12-21 05:11:36 +08:00
|
|
|
introduce py.test.mark.nocollect
|
2009-11-26 02:50:39 +08:00
|
|
|
-------------------------------------------------------
|
2009-12-30 18:37:46 +08:00
|
|
|
tags: feature 1.2
|
2009-11-26 02:50:39 +08:00
|
|
|
|
|
|
|
|
for not considering a function for test collection at all.
|
|
|
|
|
maybe also introduce a py.test.mark.test to explicitely
|
2009-12-30 18:37:46 +08:00
|
|
|
mark a function to become a tested one. Lookup JUnit
|
|
|
|
|
ways of tagging tests.
|
2009-12-21 05:11:36 +08:00
|
|
|
|
|
|
|
|
have imported module mismatch honour relative paths
|
|
|
|
|
--------------------------------------------------------
|
2009-12-30 18:37:46 +08:00
|
|
|
tags: bug 1.2
|
2009-12-21 05:11:36 +08:00
|
|
|
|
|
|
|
|
With 1.1.1 py.test fails at least on windows if an import
|
|
|
|
|
is relative and compared against an absolute conftest.py
|
|
|
|
|
path. Normalize.
|
|
|
|
|
|
2009-12-07 02:18:53 +08:00
|
|
|
make node._checkcollectable more robust
|
|
|
|
|
-------------------------------------------------
|
2009-12-30 18:37:46 +08:00
|
|
|
tags: bug 1.2
|
2009-12-07 02:18:53 +08:00
|
|
|
|
|
|
|
|
currently node._checkcollectable() can raise
|
|
|
|
|
exceptions for all kinds of reasons ('conftest.py' loading
|
|
|
|
|
problems, missing rsync-dirs, platform-skip-at-import-level
|
|
|
|
|
issues, ...). It should just return True/False and cause
|
|
|
|
|
a good error message.
|
|
|
|
|
|
|
|
|
|
call termination with small timeout
|
|
|
|
|
-------------------------------------------------
|
2009-12-30 18:37:46 +08:00
|
|
|
tags: feature 1.2
|
|
|
|
|
test: testing/pytest/dist/test_dsession.py - test_terminate_on_hanging_node
|
2009-12-07 02:18:53 +08:00
|
|
|
|
|
|
|
|
Call gateway group termination with a small timeout if available.
|
|
|
|
|
Should make dist-testing less likely to leave lost processes.
|
2009-12-07 20:27:24 +08:00
|
|
|
|
2009-12-30 18:37:46 +08:00
|
|
|
have --report=xfailed[-detail] report the actual tracebacks
|
|
|
|
|
------------------------------------------------------------------
|
|
|
|
|
tags: feature
|
|
|
|
|
|
|
|
|
|
there is no way to induce py.test to display the full tracebacks
|
|
|
|
|
of the expected failure. Introduce one.
|
2009-12-08 07:06:50 +08:00
|
|
|
|
2010-01-14 01:04:58 +08:00
|
|
|
consider globals: py.test.ensuretemp and config
|
2009-12-30 05:26:03 +08:00
|
|
|
--------------------------------------------------------------
|
2009-12-30 18:37:46 +08:00
|
|
|
tags: experimental-wish 1.2
|
2009-12-30 05:26:03 +08:00
|
|
|
|
2010-01-14 01:04:58 +08:00
|
|
|
consider deprecating py.test.ensuretemp and py.test.config
|
|
|
|
|
to further reduce py.test globality. Also consider
|
|
|
|
|
having py.test.config and ensuretemp coming from
|
|
|
|
|
a plugin rather than being there from the start.
|
|
|
|
|
|
|
|
|
|
consider allowing funcargs to setup methods
|
|
|
|
|
--------------------------------------------------------------
|
|
|
|
|
tags: experimental-wish 1.2
|
|
|
|
|
|
|
|
|
|
Users have expressed the wish to have funcargs available to setup
|
|
|
|
|
functions. Experiment with allowing funcargs there - it might
|
|
|
|
|
also help to make the py.test.ensuretemp and config deprecation.
|
|
|
|
|
|
2010-01-03 21:52:26 +08:00
|
|
|
consider pytest_addsyspath hook
|
|
|
|
|
-----------------------------------------
|
|
|
|
|
tags: 1.2
|
|
|
|
|
|
|
|
|
|
py.test could call a new pytest_addsyspath() in order to systematically
|
|
|
|
|
allow manipulation of sys.path and to inhibit it via --no-addsyspath
|
|
|
|
|
in order to more easily run against installed packages.
|
|
|
|
|
|
|
|
|
|
Alternatively it could also be done via the config object
|
|
|
|
|
and pytest_configure.
|
2010-01-14 01:17:24 +08:00
|
|
|
|
|
|
|
|
relax requirement to have tests/testing contain an __init__
|
|
|
|
|
----------------------------------------------------------------
|
|
|
|
|
tags: feature 1.2
|
|
|
|
|
bb: http://bitbucket.org/hpk42/py-trunk/issue/64
|
|
|
|
|
|
|
|
|
|
A local test run of a "tests" directory may work
|
|
|
|
|
but a remote one fail because the tests directory
|
|
|
|
|
does not contain an "__init__.py". Either give
|
|
|
|
|
an error or make it work without the __init__.py
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
show plugin information in test header
|
|
|
|
|
----------------------------------------------------------------
|
|
|
|
|
tags: feature 1.2
|
|
|
|
|
|
|
|
|
|
Now that external plugins are becoming more numerous
|
|
|
|
|
it would be useful to have external plugins along with
|
|
|
|
|
their versions displayed as a header line.
|
|
|
|
|
|
|
|
|
|
generate/deal with plugin docs
|
|
|
|
|
----------------------------------------------------------------
|
|
|
|
|
tags: feature 1.2
|
|
|
|
|
|
|
|
|
|
review and prepare docs for 1.2.0 release. Probably
|
|
|
|
|
have docs living with the plugin and require them to
|
|
|
|
|
be available on doc generation time, at least when
|
|
|
|
|
the target is the website? Or rather go for interactive help?
|
|
|
|
|
|
2010-01-14 01:20:38 +08:00
|
|
|
improved reporting on funcarg usage / name mismatches
|
|
|
|
|
----------------------------------------------------------------
|
|
|
|
|
tags: feature 1.2
|
|
|
|
|
|
|
|
|
|
see to improve help and support for funcarg usage,
|
|
|
|
|
i.e. when a funcarg does not match any provided one.
|
|
|
|
|
Also consider implementing py.test --funcargs to
|
|
|
|
|
show available funcargs - it should honour the
|
|
|
|
|
path::TestClass syntax so one can easily inspect
|
|
|
|
|
where funcargs come from or which are available.
|
