update issues
This commit is contained in:
parent
f1e3dde2ec
commit
14b2b128c2
66
ISSUES.txt
66
ISSUES.txt
|
@ -1,32 +1,16 @@
|
|||
checks / deprecations for next release
|
||||
---------------------------------------------------------------
|
||||
tags: bug 1.4 core xdist
|
||||
tags: bug 2.4 core xdist
|
||||
|
||||
* reportinfo -> location in hooks and items
|
||||
* check oejskit plugin compatibility
|
||||
* terminal reporting - dot-printing
|
||||
* some simple profiling
|
||||
* move pytest_nose out of pylib because it implicitely extends
|
||||
the protocol now - setup/teardown is called at module level.
|
||||
consider making calling of setup/teardown configurable
|
||||
|
||||
refine session initialization / fix custom collect crash
|
||||
---------------------------------------------------------------
|
||||
tags: bug 1.4 core xdist
|
||||
|
||||
When calling "py.test path/X" py.test can crash if the collection
|
||||
of that directory is skipped. Calling "py.test path" will give
|
||||
proper output. The reason is that for the very first colitems
|
||||
getinitialnodes() and a collection is done before the fully
|
||||
controlled session and pytest_make_collect_report protocol takes over.
|
||||
Try to remove the redundant getinitialnodes related logic and amend
|
||||
the session collect logic to care for this "initial" case as well.
|
||||
Apart from simplification a side effect the dsession's session
|
||||
and the core session probably converge some more.
|
||||
|
||||
do early-teardown of test modules
|
||||
-----------------------------------------
|
||||
tags: feature 1.3
|
||||
tags: feature 2.1
|
||||
|
||||
currently teardowns are called when the next tests is setup
|
||||
except for the function/method level where interally
|
||||
|
@ -38,7 +22,7 @@ prints of teardown-code appear in the setup of the next test.
|
|||
|
||||
consider and document __init__ file usage in test directories
|
||||
---------------------------------------------------------------
|
||||
tags: bug 1.4 core
|
||||
tags: bug 2.1 core
|
||||
|
||||
Currently, a test module is imported with its fully qualified
|
||||
package path, determined by checking __init__ files upwards.
|
||||
|
@ -53,7 +37,7 @@ certain scenarios makes sense.
|
|||
|
||||
relax requirement to have tests/testing contain an __init__
|
||||
----------------------------------------------------------------
|
||||
tags: feature 1.4
|
||||
tags: feature 2.1
|
||||
bb: http://bitbucket.org/hpk42/py-trunk/issue/64
|
||||
|
||||
A local test run of a "tests" directory may work
|
||||
|
@ -64,7 +48,7 @@ i.e. port the nose-logic of unloading a test module.
|
|||
|
||||
customize test function collection
|
||||
-------------------------------------------------------
|
||||
tags: feature 1.4
|
||||
tags: feature 2.1
|
||||
|
||||
- introduce py.test.mark.nocollect for not considering a function for
|
||||
test collection at all. maybe also introduce a py.test.mark.test to
|
||||
|
@ -82,7 +66,7 @@ tags: feature 1.4
|
|||
|
||||
introduce py.test.mark.platform
|
||||
-------------------------------------------------------
|
||||
tags: feature 1.4
|
||||
tags: feature 2.1
|
||||
|
||||
Introduce nice-to-spell platform-skipping, examples:
|
||||
|
||||
|
@ -99,7 +83,7 @@ interpreter versions.
|
|||
|
||||
introduce py.test.mark registration
|
||||
-----------------------------------------
|
||||
tags: feature 1.4
|
||||
tags: feature 2.1
|
||||
|
||||
introduce a hook that allows to register a named mark decorator
|
||||
with documentation and add "py.test --marks" to get
|
||||
|
@ -108,7 +92,7 @@ definitions.
|
|||
|
||||
allow to non-intrusively apply skipfs/xfail/marks
|
||||
---------------------------------------------------
|
||||
tags: feature 1.4
|
||||
tags: feature 2.1
|
||||
|
||||
use case: mark a module or directory structures
|
||||
to be skipped on certain platforms (i.e. no import
|
||||
|
@ -119,14 +103,14 @@ from conftests or plugins.
|
|||
|
||||
explicit referencing of conftest.py files
|
||||
-----------------------------------------
|
||||
tags: feature 1.4
|
||||
tags: feature 2.1
|
||||
|
||||
allow to name conftest.py files (in sub directories) that should
|
||||
be imported early, as to include command line options.
|
||||
|
||||
a central py.test ini/yml file
|
||||
----------------------------------
|
||||
tags: feature 1.4
|
||||
tags: feature 2.1
|
||||
|
||||
introduce a declarative configuration file that allows:
|
||||
- default options
|
||||
|
@ -138,7 +122,7 @@ introduce a declarative configuration file that allows:
|
|||
|
||||
new documentation
|
||||
----------------------------------
|
||||
tags: feature 1.4
|
||||
tags: feature 2.1
|
||||
|
||||
- logo py.test
|
||||
- reference / customization
|
||||
|
@ -152,7 +136,7 @@ tags: feature 1.4
|
|||
|
||||
generalize parametrized testing to generate combinations
|
||||
-------------------------------------------------------------
|
||||
tags: feature 1.4
|
||||
tags: feature 2.1
|
||||
|
||||
think about extending metafunc.addcall or add a new method to allow to
|
||||
generate tests with combinations of all generated versions - what to do
|
||||
|
@ -167,25 +151,15 @@ of values for a given function argument.
|
|||
|
||||
have imported module mismatch honour relative paths
|
||||
--------------------------------------------------------
|
||||
tags: bug 1.4
|
||||
tags: bug 2.1
|
||||
|
||||
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.
|
||||
|
||||
make node._checkcollectable more robust
|
||||
-------------------------------------------------
|
||||
tags: bug 1.4
|
||||
|
||||
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
|
||||
-------------------------------------------------
|
||||
tags: feature 1.4
|
||||
tags: feature 2.1
|
||||
test: testing/pytest/dist/test_dsession.py - test_terminate_on_hanging_node
|
||||
|
||||
Call gateway group termination with a small timeout if available.
|
||||
|
@ -193,7 +167,7 @@ Should make dist-testing less likely to leave lost processes.
|
|||
|
||||
consider globals: py.test.ensuretemp and config
|
||||
--------------------------------------------------------------
|
||||
tags: experimental-wish 1.4
|
||||
tags: experimental-wish 2.1
|
||||
|
||||
consider deprecating py.test.ensuretemp and py.test.config
|
||||
to further reduce py.test globality. Also consider
|
||||
|
@ -202,7 +176,7 @@ a plugin rather than being there from the start.
|
|||
|
||||
consider allowing funcargs for setup methods
|
||||
--------------------------------------------------------------
|
||||
tags: experimental-wish 1.4
|
||||
tags: experimental-wish 2.1
|
||||
|
||||
Users have expressed the wish to have funcargs available to setup
|
||||
functions. Experiment with allowing funcargs there - it might
|
||||
|
@ -218,7 +192,7 @@ setup_module -> request has no request.cls
|
|||
|
||||
consider pytest_addsyspath hook
|
||||
-----------------------------------------
|
||||
tags: 1.4
|
||||
tags: 2.1
|
||||
|
||||
py.test could call a new pytest_addsyspath() in order to systematically
|
||||
allow manipulation of sys.path and to inhibit it via --no-addsyspath
|
||||
|
@ -230,7 +204,7 @@ and pytest_configure.
|
|||
|
||||
show plugin information in test header
|
||||
----------------------------------------------------------------
|
||||
tags: feature 1.4
|
||||
tags: feature 2.1
|
||||
|
||||
Now that external plugins are becoming more numerous
|
||||
it would be useful to have external plugins along with
|
||||
|
@ -238,7 +212,7 @@ their versions displayed as a header line.
|
|||
|
||||
deprecate global py.test.config usage
|
||||
----------------------------------------------------------------
|
||||
tags: feature 1.4
|
||||
tags: feature 2.1
|
||||
|
||||
py.test.ensuretemp and py.test.config are probably the last
|
||||
objects containing global state. Often using them is not
|
||||
|
@ -248,7 +222,7 @@ as others.
|
|||
|
||||
remove deprecated bits in collect.py
|
||||
-------------------------------------------------------------------
|
||||
tags: feature 1.4
|
||||
tags: feature 2.1
|
||||
|
||||
In an effort to further simplify code, review and remove deprecated bits
|
||||
in collect.py. Probably good:
|
||||
|
|
Loading…
Reference in New Issue