Mock providers in tests in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a mock provider block in Terraform.

Terraform

provider "mock" {
  [1] = true
}

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

Atest_mode

Benabled

Cmock_enabled

Dsimulate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'enabled' instead of 'test_mode'

Using 'mock_enabled' which is not a valid argument

Using 'simulate' which is not recognized

The test_mode argument enables the mock provider behavior in Terraform tests.

2fill in blank

medium

Complete the code to declare a mock resource in Terraform test configuration.

Terraform

resource "mock_resource" "example" {
  name = "test"
  [1] = "mock_value"
}

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

Aid

Bmock_id

Cresource_id

Dtest_id

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'id' which is reserved for real resources

Using 'resource_id' which is not recognized

Using 'test_id' which is invalid

The mock_id attribute is used in mock resources to simulate resource IDs during tests.

3fill in blank

hard

Fix the error in the mock provider block to enable testing.

Terraform

provider "mock" {
  test_mode = [1]
}

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

Atrue

B"true"

C1

Dyes

Attempts:

3 left

💡 Hint

Common Mistakes

Using quoted strings like "true" instead of boolean true

Using numeric or string values like 1 or 'yes'

The test_mode argument expects a boolean value true without quotes.

4fill in blank

hard

Fill both blanks to create a mock data source with a test attribute.

Terraform

data "mock_data" "example" {
  [1] = "test"
  [2] = true
}

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

Aname

Btest_mode

Cenabled

Dmock_enabled

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'enabled' or 'mock_enabled' instead of 'test_mode'

Confusing the order of attributes

The name attribute sets the data source name, and test_mode enables mock testing.

5fill in blank

hard

Fill all three blanks to define a mock provider with a resource and enable test mode.

Terraform

provider "mock" {
  [1] = true
}

resource "mock_resource" "example" {
  [2] = "mock_value"
  [3] = "active"
}

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

Atest_mode

Bmock_id

Cstatus

Denabled

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'enabled' instead of 'test_mode' for the provider

Using incorrect attribute names for the resource

The provider uses test_mode to enable mocks. The resource uses mock_id as its identifier and status to indicate state.

Practice

1. What is the main purpose of using a mock provider in Terraform tests?

easy

A. To deploy resources faster in production

B. To speed up Terraform apply by skipping resource creation

C. To simulate cloud resources without creating real ones

D. To automatically fix errors in Terraform code

Solution

1. Step 1: Understand what mock providers do

   Mock providers simulate cloud resources so tests can run without real resource creation.

2. Step 2: Compare options

   Only To simulate cloud resources without creating real ones correctly describes this purpose. Others describe unrelated or incorrect uses.

3. Final Answer:

   To simulate cloud resources without creating real ones -> Option C

4. Quick Check:

   Mock provider purpose = simulate resources [OK]

Hint: Mock providers simulate resources without real creation [OK]

Common Mistakes:

• Thinking mock providers speed up production deploys
• Believing mock providers fix code automatically
• Confusing mock providers with real cloud providers

2. Which of the following is the correct way to declare a mock provider in Terraform test configuration?

easy

A. provider "mock" {}

B. mock_provider {}

C. provider mock {}

D. mock "provider" {}

Solution

1. Step 1: Recall Terraform provider syntax

   Providers are declared with provider "name" {} syntax.

2. Step 2: Identify correct syntax for mock provider

   provider "mock" {} matches this syntax exactly. Others are invalid Terraform syntax.

3. Final Answer:

   provider "mock" {} -> Option A

4. Quick Check:

   Provider declaration = provider "name" {} [OK]

Hint: Provider blocks use provider "name" {} syntax [OK]

Common Mistakes:

• Using underscores instead of quotes
• Omitting the provider keyword
• Swapping provider and name order

3. Given this Terraform test snippet using a mock provider:

resource "mock_resource" "test" {
  name = "example"
}

output "resource_name" {
  value = mock_resource.test.name
}

What will the output value be when running the test?

medium

A. null

B. "mock_resource.test.name"

C. Error: resource not found

D. "example"

Solution

1. Step 1: Understand mock resource behavior

   The mock provider returns the values set in the resource block during tests.

2. Step 2: Check the output value

   The output references mock_resource.test.name which is set to "example".

3. Final Answer:

   "example" -> Option D

4. Quick Check:

   Output value = resource attribute value [OK]

Hint: Mock resources return set attribute values in tests [OK]

Common Mistakes:

• Expecting null because no real resource exists
• Assuming an error occurs without real cloud
• Confusing output with resource address string

4. You wrote this Terraform test using a mock provider but get an error:

provider "mock" {
  version = "1.0"
}

resource "mock_resource" "test" {
  name = "test"
}

The error says: Unsupported argument: version. What is the likely cause?

medium

A. The provider block is missing required credentials

B. Mock providers do not support the 'version' argument in provider block

C. The resource name 'mock_resource' is invalid

D. Terraform version is incompatible with mock providers

Solution

1. Step 1: Analyze the error message

   The error says 'Unsupported argument: version' inside the provider block.

2. Step 2: Understand mock provider limitations

   Mock providers usually do not accept 'version' argument in provider blocks; it's for real providers.

3. Final Answer:

   Mock providers do not support the 'version' argument in provider block -> Option B

4. Quick Check:

   Provider block args must match provider capabilities [OK]

Hint: Mock providers have minimal config, no version arg [OK]

Common Mistakes:

• Adding version argument to mock provider block
• Assuming resource name causes this error
• Thinking credentials are required for mock providers

5. You want to test a Terraform module that creates multiple resources using a mock provider. Which approach best ensures your tests catch errors without creating real resources?

hard

A. Configure a mock provider and write tests that check resource attributes and dependencies

B. Run Terraform apply with real provider but in a separate test account

C. Use mock provider only for outputs, but real provider for resources

D. Skip provider configuration and test only variable inputs

Solution

1. Step 1: Understand testing goals with mock providers

   Mock providers simulate resource creation so tests can verify attributes and dependencies safely.

2. Step 2: Evaluate options for safe and effective testing

   Configure a mock provider and write tests that check resource attributes and dependencies uses mock provider fully and tests resource details, which is best practice.

3. Step 3: Eliminate unsafe or incomplete options

   Options B and C involve real resources risking cost and side effects; D skips important tests.

4. Final Answer:

   Configure a mock provider and write tests that check resource attributes and dependencies -> Option A

5. Quick Check:

   Mock provider + attribute tests = safe, thorough testing [OK]

Hint: Use mock provider to test resource attributes and dependencies [OK]

Common Mistakes:

• Testing with real providers risking cost
• Mixing mock and real providers in tests
• Ignoring resource attribute checks