DevOps Bootcamp · Lesson

Integration Testing Cloud Resources

Implement integration tests to verify the correct deployment and functionality of actual cloud resources provisioned by Terraform.

Integration Testing Cloud Resources is a free DevOps Bootcamp lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the DevOps Bootcamp learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

What is Integration Testing?

Welcome! In this lesson, we'll explore integration testing for your Terraform configurations. Unlike unit tests, which check individual components in isolation, integration tests verify that multiple parts of your infrastructure work together correctly.

For Terraform, this means deploying actual cloud resources and then checking their behavior and interactions.

Why Integration Test Terraform?

Integration tests are crucial for Terraform because they give you confidence that your code:

Deploys correctly: Verifies resources are created as expected.
Works as intended: Checks functionality, not just syntax.
Handles dependencies: Ensures interconnected resources communicate.
Prevents regressions: Catches issues when changes are made.

It's about testing the 'real deal' in a controlled environment.

Introducing Terratest

While you could write custom scripts, the most popular tool for integration testing Terraform is Terratest. It's an open-source Go library developed by HashiCorp.

Terratest allows you to:

Write Go code to deploy Terraform.
Run assertions against deployed resources.
Destroy resources after tests.

It provides helpers for interacting with Terraform, cloud APIs, and more.

Setting Up Terratest

To use Terratest, you'll need Go installed on your machine. Once Go is ready, you'll create a new Go module for your tests:

1. Create a directory for your tests (e.g., test/).

2. Initialize a Go module inside it:

cd test
go mod init my_tf_tests

Add Terratest Dependency

After initializing your Go module, you need to add Terratest as a dependency. This command fetches the library and updates your go.mod file:

go get github.com/gruntwork-io/terratest/modules/terraform

Our Test Terraform Module

Let's create a simple Terraform configuration we want to test. This will be a basic S3 bucket. Save this as s3-module/main.tf:

resource "aws_s3_bucket" "example" {
  bucket = "my-unique-test-bucket-12345"
  tags = {
    Environment = "test"
    ManagedBy   = "Terraform"
  }
}

Writing Your First Terratest

Now, let's write our Go test file. Create a file like test/s3_test.go. The core steps are:

Define Terraform options (path to config).
Initialize and apply Terraform.
Run assertions.
Destroy resources.

This ensures a clean state after each test run.

Terratest: Init, Apply & Assert

Here's the Go code for our S3 bucket test. Notice how we use terraform.InitAndApply to provision the infrastructure, and then retrieve outputs or call AWS APIs for assertions.

package test

import (
  "testing"
  "github.com/gruntwork-io/terratest/modules/aws"
  "github.com/gruntwork-io/terratest/modules/terraform"
  "github.com/stretchr/testify/assert"
)

func TestS3BucketCreation(t *testing.T) {
  t.Parallel()

  terraformOptions := &terraform.Options{
    TerraformDir: "../s3-module",
  }

  // Defer destroy to ensure cleanup
  defer terraform.Destroy(t, terraformOptions)

  // Init and apply Terraform
  terraform.InitAndApply(t, terraformOptions)

  // Get the bucket name directly from the config or outputs
  bucketName := "my-unique-test-bucket-12345"

  // Assertions
  aws.AssertS3BucketExists(t, "us-east-1", bucketName)
  tags := aws.GetS3BucketTags(t, "us-east-1", bucketName)
  assert.Equal(t, "test", tags["Environment"])
}

Running Your Integration Test

To run your Terratest, navigate to your test/ directory in the terminal and execute the Go test command. The -v flag shows verbose output.

Terratest will:

Initialize Terraform.
Apply the configuration.
Perform assertions.
Destroy the created resources.

cd test
go test -v

Best Practices for Integration Tests

Keep these tips in mind for effective integration testing:

Isolation: Use unique names or random suffixes for resources to avoid conflicts.
Cleanup: Always destroy resources after tests (defer terraform.Destroy).
Cost: Be mindful of resource costs. Use small, cheap resources.
Speed: Integration tests are slower than unit tests. Run them less frequently, perhaps in CI/CD.
Realism: Test against the same cloud environment (or a dedicated test account) you'll deploy to.

Check Your Understanding

Which of the following is a primary benefit of using integration tests for Terraform configurations?

Recap: Integration Testing

You've learned about integration testing for Terraform! We covered:

What integration tests are and why they're vital for Terraform.
How Terratest, a Go library, helps in writing these tests.
The basic workflow: setup, apply, assert, and destroy.
Key best practices for writing effective and cost-efficient integration tests.

Integration tests provide confidence that your infrastructure behaves correctly in the real world.

Frequently asked questions

Is the “Integration Testing Cloud Resources” lesson free?

Yes — the full text of “Integration Testing Cloud Resources” is free to read here on the web, and the DevOps Bootcamp course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the DevOps Bootcamp course, upgrade to CoddyKit PRO.

What will I learn in “Integration Testing Cloud Resources”?

Implement integration tests to verify the correct deployment and functionality of actual cloud resources provisioned by Terraform. You practise DevOps Bootcamp with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start DevOps Bootcamp?

No prior experience is required. DevOps Bootcamp on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Integration Testing Cloud Resources” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this DevOps Bootcamp lesson?

Yes. Every DevOps Bootcamp lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to DevOps Bootcamp