From 2a72f75d58c0b801fb3e443e0daccd12be0e1347 Mon Sep 17 00:00:00 2001
From: holger krekel <holger@merlinux.eu>
Date: Mon, 13 Apr 2009 16:35:23 +0200
Subject: [PATCH] refining formulations

--HG--
branch : trunk
---
 doc/test/features.txt | 15 +++++++--------
 doc/test/funcargs.txt |  3 +++
 2 files changed, 10 insertions(+), 8 deletions(-)

diff --git a/doc/test/features.txt b/doc/test/features.txt
index 1a535d162..fafd333ed 100644
--- a/doc/test/features.txt
+++ b/doc/test/features.txt
@@ -38,17 +38,16 @@ Rapidly write integration, functional, unit tests
 
 XXX 
 
-Unique test state setup/fixture methods 
+funcargs and xUnit style setups 
 ===================================================
 
-py.test provides the `unique funcargs mechanism`_ 
-for constructing test fixtures and handling 
-complex test scenarios.  You can also 
-use `traditional xUnit style setup`_ for
-existing code bases or if you prefer 
-it for your unit tests. 
+py.test provides powerful means for managing test
+state and fixtures.  Apart from the `traditional 
+xUnit style setup`_ for unittests it features the 
+simple and powerful `funcargs mechanism`_ for handling
+both complex and simple test scenarious. 
 
-.. _`unique funcargs mechanism`: funcargs.html
+.. _`funcargs mechanism`: funcargs.html
 .. _`traditional xUnit style setup`: xunit_setup.html
 
 load-balance tests to multiple CPUs
diff --git a/doc/test/funcargs.txt b/doc/test/funcargs.txt
index 07b9ada03..70d1c9aeb 100644
--- a/doc/test/funcargs.txt
+++ b/doc/test/funcargs.txt
@@ -11,6 +11,9 @@ Using funcargs you can:
 * cleanly encapsulate glue code between your app and your tests 
 * do test scenario setup dependent on command line opts or environment
 
+Using the funcargs mechanism will keep your test suite clean
+and allow for easier refactoring of your applications. 
+
 The basic funcarg request/provide mechanism 
 =============================================