Terraform test framework (1.6+) - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a basic Terraform test block.

Terraform

test "example" {
  [1] = "."
}

Drag options to blanks, or click blank then click option'

Asource

Bframework

Cprovider

Dmodule

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'framework' instead of 'source' causes an error.

Confusing 'provider' with 'source' attribute.

The source attribute specifies the location of the Terraform module or configuration to test.

2fill in blank

medium

Complete the code to run a Terraform plan in the test block.

Terraform

test "plan_test" {
  source = "./module"
  [1] {
    run = "terraform plan"
  }
}

Drag options to blanks, or click blank then click option'

Aactions

Bsteps

Csetup

Dexecute

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'setup' instead of 'steps' will not run commands.

Using 'actions' or 'execute' are not valid block names.

The steps block defines commands to run during the test, like 'terraform plan'.

3fill in blank

hard

Fix the error in the test assertion syntax.

Terraform

test "assert_test" {
  source = "./module"
  steps {
    run = "terraform apply -auto-approve"
  }
  [1] {
    condition = "length(terraform_output.ids) > 0"
  }
}

Drag options to blanks, or click blank then click option'

Aassertion

Basserts

Ccheck

Dassert

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'assertion' or 'asserts' causes syntax errors.

Using 'check' is not recognized by Terraform test framework.

The correct block name for assertions is assert.

4fill in blank

hard

Fill both blanks to define a test with setup and teardown steps.

Terraform

test "full_test" {
  source = "./module"
  [1] {
    run = "terraform init"
  }
  [2] {
    run = "terraform destroy -auto-approve"
  }
}

Drag options to blanks, or click blank then click option'

Asetup

Bsteps

Cteardown

Dcleanup

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'steps' instead of 'setup' for initialization.

Using 'cleanup' instead of 'teardown' is invalid.

The setup block runs before tests, and teardown runs after to clean resources.

5fill in blank

hard

Fill all three blanks to assert output values correctly.

Terraform

test "output_assert" {
  source = "./module"
  steps {
    run = "terraform apply -auto-approve"
  }
  assert {
    condition = "terraform_output.[1] == '[2]'"
    message = "Output value should be [3]"
  }
}

Drag options to blanks, or click blank then click option'

Aname

Bid

Cexpected_value

Dmy_output

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'name' or 'id' instead of the actual output name.

Not matching the message with the expected value.

The output name is 'my_output'. The condition compares it to the expected value. The message repeats the expected value.

Practice

1. What is the main purpose of the Terraform test framework introduced in version 1.6+?

easy

A. To monitor cloud resources for performance issues

B. To deploy infrastructure faster without manual approval

C. To write automated tests that check your infrastructure code works as expected

D. To replace Terraform CLI commands with a graphical interface

Solution

1. Step 1: Understand Terraform test framework purpose

   The framework is designed to let you write tests that run your Terraform code and verify resource attributes automatically.

2. Step 2: Compare options with framework purpose

   Only To write automated tests that check your infrastructure code works as expected correctly describes writing automated tests for infrastructure code. Other options describe unrelated features.

3. Final Answer:

   To write automated tests that check your infrastructure code works as expected -> Option C

4. Quick Check:

   Test framework purpose = automated infrastructure tests [OK]

Hint: Focus on testing infrastructure code correctness [OK]

Common Mistakes:

• Confusing testing with deployment speed
• Thinking it replaces CLI commands
• Mixing testing with monitoring

2. Which of the following is the correct syntax to define a Terraform test block in version 1.6+?

easy

A. module "test" { ... }

B. terraform_test "example" { ... }

C. resource "test" "example" { ... }

D. test "example" { ... }

Solution

1. Step 1: Recall Terraform test block syntax

   Terraform 1.6+ uses the test "name" { ... } block to define tests.

2. Step 2: Eliminate incorrect syntax options

   Options B, C, and D use incorrect block types or resource/module keywords not related to tests.

3. Final Answer:

   test "example" { ... } -> Option D

4. Quick Check:

   Test block syntax = test "name" [OK]

Hint: Look for the exact 'test' block keyword [OK]

Common Mistakes:

• Using resource or module instead of test block
• Adding extra prefixes like terraform_test
• Confusing test block with resource block

3. Given this Terraform test snippet, what will the test check?

test "check_instance" {
  config = {
    resource "aws_instance" "example" {
      ami           = "ami-123456"
      instance_type = "t2.micro"
    }
  }
  check { 
    resource = "aws_instance.example"
    attribute = "instance_type"
    equals = "t2.micro"
  }
}

medium

A. It checks if the AMI ID is 't2.micro'

B. It checks if the instance type of aws_instance.example is 't2.micro'

C. It verifies the instance is running

D. It validates the resource name is 'aws_instance.example'

Solution

1. Step 1: Analyze the check block

   The check block specifies resource "aws_instance.example", attribute "instance_type", and expects it to equal "t2.micro".

2. Step 2: Match check with options

   It checks if the instance type of aws_instance.example is 't2.micro' correctly states the test checks the instance_type attribute equals "t2.micro". Other options misunderstand attribute or resource checks.

3. Final Answer:

   It checks if the instance type of aws_instance.example is 't2.micro' -> Option B

4. Quick Check:

   Check attribute equals instance_type = t2.micro [OK]

Hint: Focus on attribute and equals fields in check block [OK]

Common Mistakes:

• Confusing AMI ID with instance type
• Assuming runtime status is checked
• Misreading resource name as attribute

4. This Terraform test code fails to run. What is the most likely error?

test "fail_test" {
  config = {
    resource "aws_s3_bucket" "bucket" {
      bucket = "my-bucket"
    }
  }
  check {
    resource = "aws_s3_bucket.bucket"
    attribute = "name"
    equals = "my-bucket"
  }
}

medium

A. The attribute 'name' does not exist for aws_s3_bucket resource

B. The resource block is missing required 'region' argument

C. The test block name cannot contain underscores

D. The equals value must be a number, not a string

Solution

1. Step 1: Check attribute correctness

   The aws_s3_bucket resource uses 'bucket' as the attribute for bucket name, not 'name'. Using 'name' causes the test to fail.

2. Step 2: Verify other options

   Region is usually set in provider, not required here. Test names can have underscores. Equals can be string. So only attribute error is valid.

3. Final Answer:

   The attribute 'name' does not exist for aws_s3_bucket resource -> Option A

4. Quick Check:

   Attribute must match resource schema [OK]

Hint: Check attribute names match resource documentation [OK]

Common Mistakes:

• Using wrong attribute names
• Assuming region is required in resource block
• Thinking test names have naming restrictions
• Confusing data types in equals

5. You want to write a Terraform test that verifies multiple attributes of an AWS EC2 instance, including instance_type and tags. Which approach correctly uses the Terraform test framework to check both attributes in one test?

hard

A. Use multiple check blocks inside one test block, each checking one attribute

B. Create separate test blocks for each attribute check

C. Combine attributes in one check block using a list for attribute and equals

D. Use a single check block with a map for attribute and equals

Solution

1. Step 1: Understand multiple attribute checks in Terraform tests

   The Terraform test framework allows multiple check blocks inside one test block to verify different attributes separately.

2. Step 2: Evaluate options for correctness

   Using multiple check blocks inside one test block, each checking one attribute, correctly verifies different attributes separately. Combining attributes into a single check block using a list or map is not supported. Creating separate test blocks for each attribute check works but is less efficient.

3. Final Answer:

   Use multiple check blocks inside one test block, each checking one attribute -> Option A

4. Quick Check:

   Multiple checks = multiple check blocks [OK]

Hint: Use one check block per attribute inside test [OK]

Common Mistakes:

• Trying to check multiple attributes in one check block
• Splitting checks into many test blocks unnecessarily
• Using unsupported data structures in check block