[Checkins] SVN: z3c.testsetup/branches/new_markers/src/z3c/testsetup/HOWTO_UPGRADE.txt Add an upgrade explanation.

Uli Fouquet uli at gnufix.de
Wed Jan 7 11:02:50 EST 2009


Log message for revision 94593:
  Add an upgrade explanation.

Changed:
  A   z3c.testsetup/branches/new_markers/src/z3c/testsetup/HOWTO_UPGRADE.txt

-=-
Added: z3c.testsetup/branches/new_markers/src/z3c/testsetup/HOWTO_UPGRADE.txt
===================================================================
--- z3c.testsetup/branches/new_markers/src/z3c/testsetup/HOWTO_UPGRADE.txt	                        (rev 0)
+++ z3c.testsetup/branches/new_markers/src/z3c/testsetup/HOWTO_UPGRADE.txt	2009-01-07 16:02:49 UTC (rev 94593)
@@ -0,0 +1,34 @@
+How to upgrade from `z3c.testsetup` < 0.3
+=========================================
+
+With the 0.3 release of `z3c.testsetup` the set of valid marker
+strings changed, introducing support for file-dependent setups,
+layers, etc.
+
+If you still mark your testfiles with the ``:Test-Layer:`` marker,
+update your testfiles as follows:
+
+- ``:Test-Layer: unit``
+
+  Change to: ``:doctest:``
+
+- ``:Test-Layer: python``
+
+  Change to: ``:unittest:``
+
+- ``:Test-Layer: functional``
+
+  Change to: ``:functional-zcml-layer: <ZCML-FILE>``
+
+  The ZCML file must explicitly be given.
+
+If you used custom setups passed to ``register_all_tests``, consider
+declaring those setup/teardown functions in the appropriate doctest
+files using ``:setup:`` and ``:teardown:``.
+
+You might also get better structured test suites when using the new
+layer markers ``:layer:``, ``:zcml-layer:`` and
+``functional-zcml-layer:``.
+
+Try to get rid of all parameters passed to ``register_all_tests``
+except those, mentioned in ``README.txt``.



More information about the Checkins mailing list