A test suite is a collection of tests maintained and run together to check software behavior. For a Terraform module, it provides a repeatable way to catch bugs and check that changes preserve existing behavior. section 9.0 section 9.5
Organize tests around the infrastructure configurations they need. Several checks can share one configuration, avoiding a separate create-and-destroy cycle for each check. Tests that need contradictory configurations require separate setups. section 9.2.1
Two uses for an S3 module
A private S3 configuration intended for logging and a public-facing static website need different configuration values. Give each its own group of tests rather than forcing both through one setup. section 9.2.1
Treat the suite as production code: use clear variable names, comment what each test is meant to accomplish, review test changes in pull requests, and refactor tests when that makes future tests easier to write. Add a test when a bug is found to guard against its return. section 9.2.7 section 9.0
A CI system such as GitHub Actions can run the suite automatically on a pull request and prevent a failing change from being merged. The suite must exist before CI can automate it; CI is not a substitute for writing and maintaining tests. section 7.1
