terraform-testing

Run Terraform unit tests for Power Platform without external API calls by defining mock_provider blocks in .tftest.hcl files and executing terraform test. Mock providers enable deterministic, isolated testing by verifying input validation and conditional logic locally without hitting live environments.

Terraform 1.6+ is required to use the native terraform test command, and mock_provider blocks specifically require Terraform 1.7 or later. You need this version baseline to write deterministic unit tests with run blocks, mock_provider blocks, and assertion blocks for Power Platform modules.

Structure Terraform tests for CI pipelines by organizing .tftest.hcl files into unit and integration directories, using clear assertion blocks for module behavior validation. Keep unit tests using mock providers separate from integration tests using real providers in isolated environments to scale with module complexity.

Validate Terraform module variables and conditional logic locally by writing run blocks with assertion blocks inside .tftest.hcl files. Using mock_provider blocks allows you to test input validation and conditional behavior deterministically without needing network connectivity or live Power Platform APIs.

Yes, you can run integration tests with real providers in isolated environments alongside mock provider unit tests. The testing pattern supports both end-to-end validation of module behavior using real providers and fast, isolated unit tests using mock_provider blocks within the same module structure.

Your terraform test command fails when using mock_provider blocks if you are running a Terraform version below 1.7. Mock providers were introduced in Terraform 1.7, so ensure your environment is updated to at least version 1.7 to properly execute deterministic unit tests with mock_provider blocks.