capture a concrete idea for easing platform-specific testing.
--HG-- branch : trunk
This commit is contained in:
parent
64388832d9
commit
6231bb0da3
17
ISSUES.txt
17
ISSUES.txt
|
@ -21,6 +21,23 @@ maybe also introduce a py.test.mark.test to explicitely
|
||||||
mark a function to become a tested one. Lookup JUnit
|
mark a function to become a tested one. Lookup JUnit
|
||||||
ways of tagging tests.
|
ways of tagging tests.
|
||||||
|
|
||||||
|
introduce py.test.mark.platform
|
||||||
|
-------------------------------------------------------
|
||||||
|
tags: feature 1.4
|
||||||
|
|
||||||
|
Introduce nice-to-spell platform-skipping, examples:
|
||||||
|
|
||||||
|
@py.test.mark.platform("python3")
|
||||||
|
@py.test.mark.platform("not python3")
|
||||||
|
@py.test.mark.platform("win32 and not python3")
|
||||||
|
@py.test.mark.platform("darwin")
|
||||||
|
@py.test.mark.platform("not (jython and win32)")
|
||||||
|
@py.test.mark.platform("not (jython and win32)", xfail=True)
|
||||||
|
|
||||||
|
etc. Idea is to allow Python expressions which can operate
|
||||||
|
on common spellings for operating systems and python
|
||||||
|
interpreter versions.
|
||||||
|
|
||||||
introduce py.test.mark registration
|
introduce py.test.mark registration
|
||||||
-----------------------------------------
|
-----------------------------------------
|
||||||
tags: feature 1.3
|
tags: feature 1.3
|
||||||
|
|
Loading…
Reference in New Issue