diff options
| author | Chris McDonough <chrism@plope.com> | 2010-12-19 14:00:21 -0500 |
|---|---|---|
| committer | Chris McDonough <chrism@plope.com> | 2010-12-19 14:00:21 -0500 |
| commit | bfd8d565cfbc994aa3b0e5dadd386227c02f5d18 (patch) | |
| tree | a4b199e3977111b822ec30721c42b99a5712a355 /docs | |
| parent | f3ec7ad5bf41ee34de8fd8a2d64e2f1a4b01c102 (diff) | |
| download | pyramid-bfd8d565cfbc994aa3b0e5dadd386227c02f5d18.tar.gz pyramid-bfd8d565cfbc994aa3b0e5dadd386227c02f5d18.tar.bz2 pyramid-bfd8d565cfbc994aa3b0e5dadd386227c02f5d18.zip | |
typo
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/narr/testing.rst | 2 |
1 files changed, 1 insertions, 1 deletions
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. |
