Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Update community/testing.rst #9

Merged
merged 1 commit into from

2 participants

@stevepiercy
Collaborator

typos and grammar

@blaflamme blaflamme merged commit 26bd829 into Pylons:master
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Aug 6, 2012
  1. @stevepiercy

    Update community/testing.rst

    stevepiercy authored
    typos and grammar
This page is out of date. Refresh to see the latest.
Showing with 3 additions and 3 deletions.
  1. +3 −3 community/testing.rst
View
6 community/testing.rst
@@ -104,7 +104,7 @@ both poor tests and poor documentation.
- Doctests expose too many implementation details of the interpreter (such as
the representation format of a class when printed). Often doctests break
when interpreter versions change, and the ameliorations that allow doctests
- to straddle representations between versions them cause the doctest to
+ to straddle representations between versions then cause the doctest to
become ugly and fragile.
- Doctests have an execution model that makes it difficult to follow many of
@@ -430,10 +430,10 @@ The rationale for this prohibition is simplicity: unit tests need to exercise
the AUT, while remaining as clear and simple as possible.
* Because they are not in the module which uses them, shared mock objects and
- fixtures makes impose a lookup burden on the reader.
+ fixtures imposes a lookup burden on the reader.
* Because they have to support APIs used by multiple clients, shared fixtures
- tend grow to grow APIs / data structures needed only by one client: in the
+ tend to grow APIs / data structures needed only by one client: in the
degenerate case, become as complicated as the application they are supposed
to stand in for!
Something went wrong with that request. Please try again.