terraform-test

Terraform testing with .tftest.hcl files prevents infrastructure regressions by validating configurations before deployment. You define test scenarios using run blocks and assert blocks to verify logic, outputs, and dependencies safely.

A mock provider simulates provider behavior to enable fast, reproducible Terraform unit tests. It allows you to validate configuration logic and run assertions without creating real cloud resources.

Yes, you can test Terraform configurations without applying changes using plan-mode run blocks. This validates module logic and assertions without creating real resources, offering a safe unit testing approach.

You use assert blocks within run blocks in .tftest.hcl files to verify specific conditions. Assertions check Terraform outputs, configuration logic, and dependencies to ensure your module behaves as expected.

Plan mode runs unit tests to validate configuration logic without creating resources, while apply mode runs integration tests that create real resources. Both modes support variable blocks and provider configurations.

Terraform test files should be located under a tests/ directory. These .tftest.hcl or .tftest.json files can include frontmatter with a name and description, alongside variable blocks and module references.