From 04aec935bd132a4c75e610145d4b35f066c7cb68 Mon Sep 17 00:00:00 2001 From: holger krekel Date: Tue, 14 Apr 2009 00:05:23 +0200 Subject: [PATCH] fix note on funcargs --HG-- branch : trunk --- doc/test/xunit_setup.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/test/xunit_setup.txt b/doc/test/xunit_setup.txt index d8d8756df..aec020cb0 100644 --- a/doc/test/xunit_setup.txt +++ b/doc/test/xunit_setup.txt @@ -5,12 +5,12 @@ xUnit style setup .. _`funcargs`: funcargs.html .. _`xUnit`: http://en.wikipedia.org/wiki/XUnit -** Note that since version 1.0 py.test offers `funcargs`_ -for simple and complex test setup needs. Especially -if you want to do functional and integration testing, -but also fo runittesting, it is highly recommended -that you consider using `funcargs`_ for keeping -a clean and maintenable test suite. ** +Note: + + Since version 1.0 py.test offers funcargs_ for both + simple and complex test setup needs. Especially + for functional and integration, but also for unit testing, it is + highly recommended that you use this new method. Python, Java and other languages have a tradition of using xUnit_ style testing. This typically