summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorTshepang Lekhonkhobe <tshepang@gmail.com>2013-04-24 02:13:52 +0300
committerTshepang Lekhonkhobe <tshepang@gmail.com>2013-04-24 02:13:52 +0300
commit7ecb2db0ca58cb93935c5005174d43f0507632df (patch)
tree8f315de7c4c841a39f5970e44e233ccdac86bc77 /docs
parent88fe7f3cb4c49f5a8dae8b2ad366e63d2da48cf4 (diff)
downloadwebtest-7ecb2db0ca58cb93935c5005174d43f0507632df.tar.gz
typo
Diffstat (limited to 'docs')
-rw-r--r--docs/index.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/index.txt b/docs/index.txt
index 7ffc8c6..d4942b9 100644
--- a/docs/index.txt
+++ b/docs/index.txt
@@ -54,7 +54,7 @@ WebTest testing model is sometimes called a *functional test*,
*integration test*, or *acceptance test* (though the latter two are
not particularly good descriptions). This is in contrast to a *unit
test* which tests a particular piece of functionality in your
-application. While complex programming tasks are often is suited to
+application. While complex programming tasks are often suited to
unit tests, template logic and simple web programming is often best
done with functional tests; and regardless of the presence of unit
tests, no testing strategy is complete without high-level tests to