Acceptance Tests: TestSteps

TestSteps represent the application of an actual Terraform configuration file to a given state. Each step requires a configuration as input and provides developers several means of validating the behavior of the specific resource under test.

Test Modes

Terraform’s test framework facilitates three distinct modes of acceptance tests, Lifecycle, Import and Refresh.

Lifecycle mode is the most common mode, and is used for testing plugins by providing one or more configuration files with the same logic as would be used when running terraform apply.

Import mode is used for testing resource functionality to import existing infrastructure into a Terraform statefile, using the same logic as would be used when running terraform import.

Refresh mode is used for testing resource functionality to refresh existing infrastructure, using the same logic as would be used when running terraform refresh.

An acceptance test’s mode is implicitly determined by the fields provided in the TestStep definition. The applicable fields are defined in the TestStep Reference API.

Steps

Steps is a field within TestCase, the struct used to construct acceptance tests. Each step represents a full terraform apply of a given configuration language, followed by zero or more checks (defined later) to verify the application. Each Step is applied in order, and require its own configuration and optional check functions.

Below is a code example of a lifecycle test that provides two TestStep structs:

package example // example.Widget represents a concrete Go type that represents an API resourcefunc TestAccExampleWidget_basic(t *testing.T) {  var widgetBefore, widgetAfter example.Widget  rName := acctest.RandStringFromCharSet(10, acctest.CharSetAlphaNum)   resource.Test(t, resource.TestCase{    PreCheck:     func() { testAccPreCheck(t) },    Providers:    testAccProviders,    CheckDestroy: testAccCheckExampleResourceDestroy,    Steps: []resource.TestStep{      {        Config: testAccExampleResource(rName),        Check: resource.ComposeTestCheckFunc(          testAccCheckExampleResourceExists("example_widget.foo", &widgetBefore),        ),      },      {        Config: testAccExampleResource_removedPolicy(rName),        Check: resource.ComposeTestCheckFunc(          testAccCheckExampleResourceExists("example_widget.foo", &widgetAfter),        ),      },    },  })}

In the above example each TestCase invokes a function to retrieve it’s desired configuration, based on a randomized name provided, however an in-line string or constant string would work as well, so long as they contain valid Terraform configuration for the plugin or resource under test. This pattern of first applying and checking a basic configuration, followed by applying a modified configuration with updated or additional checks is a common pattern used to test update functionality.

Check Functions

After the configuration for a TestStep is applied, Terraform’s testing framework provides developers an opportunity to check the results by providing a “Check” function. While possible to only supply a single function, it is recommended you use multiple functions to validate specific information about the results of the terraform apply ran in each TestStep. The Check attribute of TestStep is singular, so in order to include multiple checks developers should use either ComposeTestCheckFunc or ComposeAggregateTestCheckFunc (defined below) to group multiple check functions, defined below:

ComposeTestCheckFunc

ComposeTestCheckFunc lets you compose multiple TestCheckFunc functions into a single check. As a user testing their provider, this lets you decompose your checks into smaller pieces more easily, with individual methods for checking specific attributes. Each check is ran in the order provided, and on failure the entire TestCase is stopped, and Terraform attempts to destroy any resources created.

Example:

Steps: []resource.TestStep{  {    Config: testAccExampleResource(rName),    Check: resource.ComposeTestCheckFunc(      // if testAccCheckExampleResourceExists fails to find the resource,       // the parent TestStep and TestCase fail      testAccCheckExampleResourceExists("example_widget.foo", &widgetBefore),       resource.TestCheckResourceAttr("example_widget.foo", "size", "expected size"),    ),  },},

ComposeAggregateTestCheckFunc

ComposeAggregateTestCheckFunc lets you compose multiple TestCheckFunc functions into a single check. It’s purpose and usage is identical to ComposeTestCheckFunc, however each check is ran in order even if a previous check failed, collecting the errors returned from any checks and returning a single aggregate error. The entire TestCase is still stopped, and Terraform attempts to destroy any resources created.

Example:

Steps: []resource.TestStep{  {    Config: testAccExampleResource(rName),    Check: resource.ComposeAggregateTestCheckFunc(      // if testAccCheckExampleResourceExists fails to find the resource,       // the following TestCheckResourceAttr is still run, with any errors aggregated      testAccCheckExampleResourceExists("example_widget.foo", &widgetBefore),      resource.TestCheckResourceAttr("example_widget.foo", "active", "true"),    ),  },},

Builtin check functions

Terraform has several TestCheckFunc functions built in for developers to use for common checks, such as verifying the status and value of a specific attribute in the resulting state. Developers are encouraged to use as many as reasonable to verify the behavior of the plugin/resource, and should combine them with the above mentioned ComposeTestCheckFunc or ComposeAggregateTestCheckFunc functions.

Most builtin functions accept name, key, and/or value fields, derived from the typical Terraform configuration stanzas:

resource "example_widget" "foo" {  active = true}

Here the name represents the resource name in state (example_widget.foo), the key represents the attribute to check (active), and value represents the desired value to check against (true). In this case, an equality check would be:

resource.TestCheckResourceAttr("example_widget.foo", "active", "true"),

The full list of functions can be seen in the helper/resource package. Names for these begin with TestCheck... and TestMatch.... The most common checks for non-TypeSet attributes are below.

For TypeSet attributes, there are some additional functions that accept a * placeholder in attribute keys for indexing into the set.

All of these functions also accept the below syntax in attribute keys to enable additional behaviors.

Custom check functions

The Check field of TestStep accepts any function of type TestCheckFunc. Developers are free to write their own check functions to create customized validation functions for their plugin. Any function that matches the TestCheckFunc function signature of func(*terraform.State) error can be used individually, or with other TestCheckFunc functions with one of the above Aggregate functions.

It's common to write custom TestCheckFunc functions to validate resources were created correctly by using SDKs directly to verify identity and properties of resources. These functions can retrieve information by SDKs and provide the results to other TestCheckFunc methods. The below example uses ComposeTestCheckFunc to group a set of TestCheckFunc functions together. The first function testAccCheckExampleWidgetExists uses the Example service SDK directly, and queries it for the ID of the widget we have in state. Once found, the result is stored into the widget struct declared at the beginning of the test function. The next check function testAccCheckExampleWidgetAttributes receives the updated widget and checks its attributes. The final check TestCheckResourceAttr verifies that the same value is stored in state.

func TestAccExampleWidget_basic(t *testing.T) {  var widget example.WidgetDescription   resource.Test(t, resource.TestCase{    PreCheck:     func() { testAccPreCheck(t) },    Providers:    testAccProviders,    CheckDestroy: testAccCheckExampleWidgetDestroy,    Steps: []resource.TestStep{            {        Config: testAccExampleWidgetConfig,        Check: resource.ComposeTestCheckFunc(          testAccCheckExampleWidgetExists("example_widget.bar", &widget),          testAccCheckExampleWidgetAttributes(&widget),          resource.TestCheckResourceAttr("example_widget.bar", "active", "true"),        ),      },    },  })} // testAccCheckExampleWidgetAttributes verifies attributes are set correctly by // Terraformfunc testAccCheckExampleWidgetAttributes(widget *example.WidgetDescription) resource.TestCheckFunc {  return func(s *terraform.State) error {    if *widget.active != true {      return fmt.Errorf("widget is not active")    }     return nil  }} // testAccCheckExampleWidgetExists uses the Example SDK directly to retrieve // the Widget description, and stores it in the provided // *example.WidgetDescriptionfunc testAccCheckExampleWidgetExists(resourceName string, widget *example.WidgetDescription) resource.TestCheckFunc {  return func(s *terraform.State) error {    // retrieve the resource by name from state    rs, ok := s.RootModule().Resources[resourceName]    if !ok {      return fmt.Errorf("Not found: %s", resourceName)    }     if rs.Primary.ID == "" {      return fmt.Errorf("Widget ID is not set")    }     // retrieve the client from the test provider    client := testAccProvider.Meta().(*ExampleClient)     response, err := client.DescribeWidgets(&example.DescribeWidgetsInput{      WidgetIDs: []string{rs.Primary.ID},    })     if err != nil {      return err    }     // we expect only a single widget by this ID. If we find zero, or many,     // then we consider this an error    if len(response.WidgetDescriptions) != 1 ||      *response.WidgetDescriptions[0].WidgetID != rs.Primary.ID {      return fmt.Errorf("Widget not found")    }     // store the resulting widget in the *example.WidgetDescription pointer    *widget = *response.WidgetDescriptions[0]    return nil  }}

Caveats

for_each syntax is not supported in the Config field.

Next Steps

Acceptance Testing is an essential approach to validating the implementation of a Terraform Provider. Using actual APIs to provision resources for testing can leave behind real infrastructure that costs money between tests. The reasons for these leaks can vary, regardless Terraform provides a mechanism known as Sweepers to help keep the testing account clean.