Integration testing strategies in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize Terraform before running tests.

Terraform

terraform [1]

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

Aapply

Binit

Cplan

Ddestroy

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'terraform apply' before initialization causes errors.

Confusing 'plan' with 'init' command.

Terraform must be initialized with terraform init to download providers and set up the working directory before testing.

2fill in blank

medium

Complete the code to create a Terraform plan file for integration testing.

Terraform

terraform [1] -out=tfplan

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

Aplan

Bapply

Cdestroy

Dvalidate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'apply' instead of 'plan' when creating a plan file.

Forgetting to specify the output file with '-out'.

The terraform plan command creates an execution plan and saves it to a file for review or testing.

3fill in blank

hard

Fix the error in the command to apply a saved Terraform plan during integration testing.

Terraform

terraform [1] tfplan

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

Aplan

Bvalidate

Capply

Dinit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'terraform plan tfplan' instead of 'apply'.

Trying to initialize with 'init' when applying.

To apply a saved plan file, use terraform apply tfplan. Using 'plan' or 'init' here is incorrect.

4fill in blank

hard

Fill both blanks to write a Terraform test block that checks if a resource attribute equals a value.

Terraform

test "resource_attribute" {
  check "state_check" {
    assert {
      condition = [1] == [2]
    }
  }
}

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

Aresource.aws_instance.example.id

B"running"

C"stopped"

Dresource.aws_instance.example.state

Attempts:

3 left

💡 Hint

Common Mistakes

Using the instance ID instead of state for comparison.

Comparing to the wrong string value.

The test checks if the instance state equals "running" using the correct resource attribute.

5fill in blank

hard

Fill all three blanks to create a Terraform output that shows the public IP of an instance after integration testing.

Terraform

output "instance_ip" {
  value = [1].[2].[3]
}

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

Aaws_instance

Bexample

Cpublic_ip

Dprivate_ip

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'private_ip' instead of 'public_ip'.

Mixing resource names or types.

The output accesses the public IP attribute of the example AWS instance resource.

Practice

1. What is the main goal of integration testing in Terraform?

easy

A. To create user interfaces for cloud services

B. To check if multiple cloud resources work together correctly

C. To deploy resources without any errors

D. To write Terraform code faster

Solution

1. Step 1: Understand integration testing purpose

   Integration testing focuses on verifying that different parts work together as expected.

2. Step 2: Apply this to Terraform

   In Terraform, it means checking if cloud resources connect and interact properly.

3. Final Answer:

   To check if multiple cloud resources work together correctly -> Option B

4. Quick Check:

   Integration testing = check resource cooperation [OK]

Hint: Integration testing checks resource cooperation, not code speed [OK]

Common Mistakes:

• Confusing integration testing with deployment
• Thinking it tests only single resources
• Assuming it improves coding speed

2. Which Terraform feature helps share data between resources during integration testing?

easy

A. Terraform variables

B. Terraform modules

C. Terraform providers

D. Terraform outputs

Solution

1. Step 1: Identify data sharing methods in Terraform

   Terraform outputs expose values from one resource to be used elsewhere.

2. Step 2: Match with integration testing needs

   Outputs allow tests to verify connections by passing resource info between them.

3. Final Answer:

   Terraform outputs -> Option D

4. Quick Check:

   Outputs share data between resources [OK]

Hint: Outputs expose resource data for testing connections [OK]

Common Mistakes:

• Confusing variables with outputs
• Thinking providers share data
• Assuming modules handle data passing

3. Given this Terraform snippet, what will output "db_endpoint" show after apply?

resource "aws_db_instance" "db" {
  identifier = "mydb"
  endpoint   = "mydb.example.com"
}

output "db_endpoint" {
  value = aws_db_instance.db.endpoint
}

medium

A. "mydb"

B. "aws_db_instance.db.endpoint"

C. An error because endpoint is not a valid attribute

D. "mydb.example.com"

Solution

1. Step 1: Understand resource attributes

   The resource aws_db_instance.db does not have a valid attribute named endpoint accessible directly; endpoint is an attribute returned by AWS after creation but is accessed differently.

2. Step 2: Check output value

   Since endpoint is not a valid attribute in this context, Terraform will raise an error when trying to output it.

3. Final Answer:

   An error because endpoint is not a valid attribute -> Option C

4. Quick Check:

   Outputting invalid attribute causes error [OK]

Hint: Not all resource attributes are directly accessible; check docs [OK]

Common Mistakes:

• Thinking output shows attribute value without validation
• Assuming endpoint is valid attribute
• Confusing identifier with endpoint

4. You wrote a Terraform test to check resource connections but it fails with a dependency error. What is the likely cause?

medium

A. Missing explicit resource dependency using depends_on

B. Using outputs instead of variables

C. Applying in the wrong cloud region

D. Incorrect provider version

Solution

1. Step 1: Identify cause of dependency errors

   Terraform needs explicit dependencies to know resource creation order.

2. Step 2: Check for missing depends_on

   If depends_on is missing, Terraform may try to create resources in wrong order causing errors.

3. Final Answer:

   Missing explicit resource dependency using depends_on -> Option A

4. Quick Check:

   Dependency errors = missing depends_on [OK]

Hint: Add depends_on to fix resource creation order errors [OK]

Common Mistakes:

• Blaming outputs for dependency errors
• Ignoring resource creation order
• Assuming provider version causes dependencies

5. You want to run integration tests on Terraform resources without affecting production. Which strategy is best?

hard

A. Use isolated test environments with separate state files

B. Run tests directly on production resources

C. Disable Terraform state locking during tests

D. Use the same state file but different workspaces

Solution

1. Step 1: Understand risk of testing on production

   Testing on production can cause unintended changes or downtime.

2. Step 2: Choose isolated environments

   Using separate environments and state files keeps tests safe and independent from production.

3. Final Answer:

   Use isolated test environments with separate state files -> Option A

4. Quick Check:

   Isolated environments prevent production impact [OK]

Hint: Always isolate test environments to protect production [OK]

Common Mistakes:

• Testing directly on production
• Disabling state locking unsafely
• Using same state file for tests and prod