From bfd8d565cfbc994aa3b0e5dadd386227c02f5d18 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Sun, 19 Dec 2010 14:00:21 -0500 Subject: typo --- docs/narr/testing.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/narr/testing.rst b/docs/narr/testing.rst index ab4296f6c..007b96c2a 100644 --- a/docs/narr/testing.rst +++ b/docs/narr/testing.rst @@ -44,7 +44,7 @@ given codebase. Unit testing often provides the opportunity to obtain better "coverage": it's usually possible to supply a unit under test with arguments and/or an environment which causes *all* of its potential codepaths to be executed. This is usually not as easy to do with a set of integration or -functinal tests, but integration and functional testing provides a measure of +functional tests, but integration and functional testing provides a measure of assurance that your "units" work together, as they will be expected to when your application is run in production. -- cgit v1.2.3