What problem does it solve? Writing automated tests for Terraform modules requires knowing the .tftest.hcl syntax, run block semantics, plan versus apply modes, and mock provider configuration, which many practitioners get wrong or skip entirely. ## Core Features & Use Cases - Test File Authoring: Create .tftest.hcl files with run blocks, assert blocks, variables, and expect_failures for validating module behavior. - Unit and Integration Testing: Use command = plan for fast logic validation or command = apply for real infrastructure testing with automatic cleanup in reverse run order. - Mock Providers: Simulate provider behavior without cloud credentials or costs using mock_provider blocks (Terraform 1.7.0+). - Use Case: A module author needs to verify that a VPC module creates the correct subnets and rejects invalid CIDR blocks; this Skill guides writing plan-mode unit tests, apply-mode integration tests, and negative tests with expect_failures. ## Quick Start Write a Terraform test file that validates my VPC module creates two private subnets and rejects an invalid CIDR block.