The document discusses strategies for maintaining acceptance tests over time beyond just writing them once. It suggests treating acceptance tests like production code by revising and refactoring them as the system evolves. Tests should describe what is being tested in a declarative style rather than specifying implementation details so their implementation can change. As a project and domain maturity, acceptance tests may move from end-to-end implementations to using the domain model directly to run faster. The test suite should also be periodically evaluated to determine if restructuring or new tests are needed.