terraform-test-coverage

You can find Terraform test coverage gaps by evaluating .tftest.hcl files against expected scenarios like happy paths, variable validations, feature toggles, edge cases, and CIDR math to produce a list of missing tests and recommended additions.

The native Terraform test coverage assessment checks for strong plan-only assertions, proper mock_provider or override_resource usage, and explicit expect_failures coverage for validation blocks across your .tftest.hcl files.

Testing Terraform variable validations requires explicit expect_failures blocks within your .tftest.hcl files. The coverage assessment verifies that these expect_failures statements are present and properly mapped to your validation rules.

Yes, the Terraform test coverage assessment specifically checks for mock_provider and override_resource patterns in your .tftest.hcl files to ensure resources are properly mocked and plan-only assertions are used without requiring real infrastructure provisioning.

You should review Terraform test coverage before a release, or when adding new variables, resources, or feature flags, to ensure your .tftest.hcl files adequately cover critical infrastructure behavior and reduce blind spots before changes ship.

Yes, the Terraform coverage assessment explicitly evaluates whether your .tftest.hcl files include tests for edge cases, CIDR math, feature toggles, and naming conventions alongside standard happy paths and variable validations.