[py-svn] r62073 - py/branch/pytestplugin

[hpk at codespeak.net]

Author: hpk
Date: Sat Feb 21 13:08:41 2009
New Revision: 62073

Modified:
   py/branch/pytestplugin/TODO.txt
Log:
move out py.test TODOs to "freemap" (not committed at this point) 



Modified: py/branch/pytestplugin/TODO.txt
==============================================================================
--- py/branch/pytestplugin/TODO.txt	(original)
+++ py/branch/pytestplugin/TODO.txt	Sat Feb 21 13:08:41 2009
@@ -12,115 +12,6 @@
   - small things: --nomagic -> --no-reassert
   - deprecate py.magic 
 
-py.test 
---------------
-
-- compatilibity: honour/warn item.run() method of test items (so far
-  probably only execute() is warned about or the other way round)
-
-- introduce plugin arch, port existing things to plugins:
-  - OK filelog 
-  - OK tmpdir / chtmpdir per method 
-  - OK xfail 
-  - OK unittest plugin 
-  - OK in "pytest_plugins" specs allow for missing pytest prefix
-  - OK allow specifying pytest plugins from the environment 
-  - OK/MOSTLY streamline assert_lines_contains_lines / result handling 
-  - construct Argument object for sending/receiving of args to
-    test methods 
-  - py.plugin: make subscriptions weakref'ed 
-  - Pytest functiona arguments: provide the test function
-    source / head when reporting a "could not find test function argument" 
-  - plugins: additionally initialize from $HOME/.py/pylib file? 
-    extend or add another method to PluginManager.consider_env()? 
-  - have plugins/hook cause log events / and have a debug plugin 
-  - implement doctest plugin 
-  - apigen 
-  - plugin for more information about test environment 
-  - plugin ordering? 
-  - --traceconfig presenting info about conftests, plugins, ... 
-  - consider porting py/doc/confrest to a plugin (mostly, also
-    consider pypy dependencies)
-  - ask guido to look at apigen & port javascript tests 
-  - plugin for ReST reporting? 
-  - put assert reinterpretation into plugin 
-  - port py/test/web to py/test/plugin/pytest_webcheck.py
-  - cross-platform testing (testing from osx/linux to windows and vice versa?)
-  - deprecated_call and importorskip(), allow plugin-provided "py.test.*" hooks?  
-  - acceptance/assertlines 
-  - dist-testing? 
-
-  - normalize/use linecomp/assert_lines_...
-  - statt "fstester, pytester" etc. ein "testdir" plugin:
-        def test_something(testdir):
-            path = testdir.file.py = makefile(...) # will use test method name a a filename 
-            #testdir.makefile(...) would raise an Exception becaue a file was created already
-            result = testdir.subprocess_runpytest(*args) 
-            result.stdout.contains(...)
-            result.stdout.assert_contains_lines(...)
-            result.stderr.assert_contains_lines(...)
-
-- Testdir 
-
-- DONE remove need for usefilters by directly checking if the
-  "to-be-filtered" file is an command line arg 
-  (seems liek the original purpose for usefilters is exactly that) 
-
-- consider py lib plugins: 
-
-      py_path_svn 
-      py_path_execnet 
-
-  and generalize pytest plugin calling, for example:
-
-      py.plugins.callfirst(...)
-      py.plugins.calleach(...)
-
-  and also consider a command line tool: 
-
-     py.plugin list|ls
-     etc. 
-
-
-- introduce setuptools-style version checking, at least
-  for py lib itself, maybe also for other packages: 
-
-     py.checkversion("py>=1.0")
-
-- review/simplify py/doc/conftest.py 
-
-- generative tests: it is somewhat misleading for 
-  the classical htmlviews that generated tests are identified 
-  by numbers rather than by its parameters.  unclear how
-  to fix this because we may not always be able to assume
-  that we can identify a generated tests by using its parameters
-  (it might not be hashable, doesn't have a sensical repr ...?)
-
-- turn deprecation / apiwarnings into events, report them at the end? 
-
-- get APIGEN back to work 
-
-- get web reporter back to work 
-
-- introduce decorator "shouldfail" or "xfail" 
-  as to mark a test as "expected to fail", 
-  report specially if it surprisingly passes 
-
-- nightly test runs on multiple platforms 
-
-- review and refactor architecture of py.test with particular
-  respect to: 
-  - writing (stacked) extensions / plugins (compared to Nose) 
-  - porting existing extensions (htmlconftest / buildbot / PyPy's conftest's ...) 
-  - fast and stable distributed testing 
-  - reliable cross-platform testing 
-
-- improve py.test documentation to reflect new
-  event architecture 
-
-- review and optimize skip-handling (it can be quite slow in
-  certain situations because e.g. setup/teardown is fully performed 
-  although we have "skip by keyword" and could detect this early)
 
 py.execnet
 --------------