Integration testing strategies in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Integration Testing in Terraform

What is the main purpose of integration testing when using Terraform for infrastructure?

A To check that multiple Terraform modules work together as expected when combined.

B To verify that individual Terraform modules work correctly in isolation.

C To test the performance of cloud resources created by Terraform.

D To validate the syntax of Terraform configuration files.

💡 Hint

Think about testing how parts connect rather than testing parts alone.

Integration testing ensures that multiple Terraform modules or resources work together correctly, not just individually.

❓ Configuration

intermediate

Terraform Integration Test Setup

Which Terraform testing tool is designed to run integration tests by applying real infrastructure changes in a safe environment?

A Terratest

B terraform validate

C terraform fmt

D terraform graph

💡 Hint

This tool uses Go language to test Terraform code by deploying real resources.

Terratest is a Go library that helps write automated tests for Terraform by deploying real infrastructure and verifying it.

❓ Architecture

advanced

Isolating Integration Tests in Terraform

Which approach best isolates integration tests to avoid affecting production infrastructure?

A Run tests directly on the production environment with live data.

B Run tests only on local Terraform plan outputs without applying.

C Manually delete resources after testing in production.

D Use separate Terraform workspaces or isolated cloud accounts for testing.

💡 Hint

Think about creating a safe, separate place for testing.

Using separate workspaces or accounts isolates test resources, preventing interference with production.

❓ security

advanced

Security Considerations in Terraform Integration Testing

What is a key security best practice when running integration tests that deploy cloud resources with Terraform?

A Disable all logging during tests to prevent sensitive data exposure.

B Store sensitive test credentials in plain text files within the Terraform code repository.

C Use temporary, least-privilege credentials and rotate them regularly for testing.

D Use permanent high-privilege credentials for all tests to avoid permission errors.

💡 Hint

Think about minimizing risk if credentials are exposed.

Using temporary credentials with minimal permissions reduces risk and follows security best practices during testing.

❓ service_behavior

expert

Terraform Integration Test Result Behavior

After running an integration test that applies Terraform code to create resources, what is the expected state of the Terraform state file if the test completes successfully and resources are destroyed at the end?

A The state file contains all created resources with their IDs and attributes.

B The state file is empty or does not contain any resources after destruction.

C The state file is deleted automatically by Terraform after test completion.

D The state file contains only the planned resources but not the applied ones.

💡 Hint

Consider what happens to the state after resources are destroyed.

When resources are destroyed, the Terraform state file no longer tracks those resources and is effectively empty of them.

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