Acceptance tests are an essential part of the provider - they provide confidence in the functionality and consistency of resources and data sources as they are introduced and over time.
Whilst we can't test every use-case or permutation of fields - each data source/resource gets a common set of tests to ensure the core use-cases are covered.
As a general rule, the more complex the resource the more tests there are - for example AKS, App Service and Virtual Machines all have a large number of end-to-end tests.
Note: Acceptance Tests provision real resources within Azure - which may have an associated charge for each resource.
When selecting SKUs for testing, pick the lowest/cheapest SKU which covers the test - unless there's good reason to otherwise (e.g. some configurations can provision more quickly using one SKU over another).
See Running the Tests.
While tests reside in the same folder as resource and data source .go files, they need to be in a separate test package to prevent circuler references. ie for the file ./internal/services/aab2c/aadb2c_directory_data_source_test.go the package should be:
package aadb2c_test
import ...This is checked by make test during CI.
During acceptance tests it is important to validate that the resource in Azure matches what Terraform expects and has saved into state. This can be done by adding a data.ImportStep() after every step. This will import the resource into Terraform and compare that the Terraform state matches the Azure Resource.
As some properties (such as sensitive data like passwords) are not returned from Azure you can ignore these properties by passing them into the import step: data.ImportStep("password", "database_primary_key").
Test names should follow the convention TestAcc + ResourceName + _ + test -> TestAccExampleResource_basic, or to group tests:
func TestAccExampleResource_category_test1(t *testing.T) { ... }
func TestAccExampleResource_category_test2(t *testing.T) { ... }The Acceptance Tests for both Data Sources and Resources within this Provider use a Go struct for each test, in the form {Name}{DataSource|Resource}Test, for example:
// for a data source named Example:
type ExampleDataSourceTest struct {}
// for a resource named Example:
type ExampleResourceTest struct {}This allows the test configurations to be scoped (and not used unintentionally across different resources), for example a Resource may use:
type ExampleResourceTest struct {}
func (ExampleResourceTest) basic(data acceptance.TestData) string {
return fmt.Sprintf(`
provider "azurerm" {
features {}
}
resource "azurerm_example_resource" "example" {
name = "my_example_resource"
location = "%s"
example_property = "bar"
}
`, data.Locations.Primary)
}This allows the Acceptance Test for each Data Source/Resource to reference that struct and obtain the associated Terraform Configuration as a part of the test e.g.:
func TestAccExampleResource_basic(t *testing.T) {
data := acceptance.BuildTestData(t, "azurerm_example_resource", "test")
r := ExampleResourceTest{}
data.ResourceTest(t, r, []acceptance.TestStep{
{
Config: r.basic(data),
Check: acceptance.ComposeTestCheckFunc(
check.That(data.ResourceName).ExistsInAzure(r),
),
},
data.ImportStep(),
})
}At a minimum, a Data Source requires:
- A
basictest (Example) - this tests the minimum fields (e.g. all Required fields) for this Data Source.
However more complex Data Sources can warrant additional acceptance tests - consideration should be given during the development of each Data Source to what's important to be tested.
At a minimum, a Resource requires:
-
A
basictest (Example) - this tests the minimum fields (e.g. all Required fields) for this Resource. -
A
requiresImporttest (Example) - this test exercises the logic in thecreatefunction of a resource that checks for the prior existence of the resource and being created and expects an error. The acceptance test package provides a helper function is provided to be used in the test, calledRequiresImportErrorStepfor this purpose. -
A
completetest (Example) - this tests all possible fields (e.g. all Required/Optional fields) for this Resource. -
A
updatetest (Example) - This test exercises a change of values for any properties that can be updated by executing consecutive configurations to change a resource in a predictable manner. Properties which areForceNewshould not be tested in this way.
However more complex Resource generally warrant additional acceptance tests - consideration should be given during the development of each Resource to what's important to be tested.
A Data Source generally has one or two Required properties and a number of Computed properties - as such it's typical for this test to reuse the Terraform Configuration from the Complete test for the associated Resource (as this exercises all options on the resource).
Since the Data Source primarily exposes Computed-only fields which aren't specified in the Terraform Configuration, we typically assert that these computed fields have a/an expected value - which differs from the Acceptance Tests for the Resource where we'll use an Import step to confirm that the Terraform Configuration matches the imported state.
func TestAccExampleDataSource_complete(t *testing.T) {
data := acceptance.BuildTestData(t, "data.azurerm_example_resource", "test")
r := ExampleDataSourceTest{}
data.ResourceTest(t, r, []acceptance.TestStep{
{
Config: r.complete(data),
Check: acceptance.ComposeTestCheckFunc(
check.That(data.ResourceName).Key("example_property").HasValue("bar")
check.That(data.ResourceName).Key("example_optional_bool").HasValue("false")
check.That(data.ResourceName).Key("example_optional_string").HasValue("foo")
),
},
})
}
func (ExampleDataSourceTest) complete(data acceptance.TestData) string {
template := ExampleResourceTest{}.basic(data)
return fmt.Sprintf(`
%[1]s
data "azurerm_example_resource" "test" {
name = azurerm_example_resource.test.name
}
`, template)
}This test provisions the resource using the minimum configuration possible (e.g. only the Required fields), which is intended to test the happy path (of creating, reading and then destroying a resource).
As we're testing the Resource, we make use of an ImportStep as a part of the Acceptance Test to ensure that each of the fields specified as a part of the Terraform Configuration are set into the state.
func TestAccExampleResource_basic(t *testing.T) {
data := acceptance.BuildTestData(t, "azurerm_example_resource", "test")
r := ExampleResourceTest{}
data.ResourceTest(t, r, []acceptance.TestStep{
{
Config: r.basic(data),
Check: acceptance.ComposeTestCheckFunc(
check.That(data.ResourceName).ExistsInAzure(r),
),
},
data.ImportStep(),
})
}
func (ExampleResourceTest) basic(data acceptance.TestData) string {
return fmt.Sprintf(`
provider "azurerm" {
features {}
}
resource "azurerm_example_resource" "example" {
name = "my_example_resource"
location = "%s"
example_property = "bar"
}
`, data.Locations.Primary)
}This test provisions the resource using the maximum configuration possible (e.g. all Required and Optional fields which can be set together), which is intended to test the more complex scenario for this resource.
As we're testing the Resource, we make use of an ImportStep as a part of the Acceptance Test to ensure that each of the fields specified as a part of the Terraform Configuration are set into the state.
func TestAccExampleResource_complete(t *testing.T) {
data := acceptance.BuildTestData(t, "azurerm_example_resource", "test")
r := ExampleResourceTest{}
data.ResourceTest(t, r, []acceptance.TestStep{
{
Config: r.complete(data),
Check: acceptance.ComposeTestCheckFunc(
check.That(data.ResourceName).ExistsInAzure(r),
),
},
data.ImportStep(),
})
}
func (ExampleResourceTest) complete(data acceptance.TestData) string {
return fmt.Sprintf(`
provider "azurerm" {
features {}
}
resource "azurerm_example_resource" "example" {
name = "my_example_resource"
location = "%s"
example_property = "bar"
example_optional_bool = false
example_optional_string = "foo"
tags = {
"Hello" = "World"
}
}
`, data.Locations.Primary)
}This test is intended to confirm that the logic within the create function (to check for the presence of an existing resource) works as intended - as the Azure Resource Manager API's are Upserts, meaning that without this check it's possible to unintentionally "adopt" existing resources.
Since this test is attempting to provision the same resource, with the same identifier, twice - this test typically reuses the Basic test as a part of it - interpolating it's values as required.
func TestAccExampleResource_basic(t *testing.T) {
data := acceptance.BuildTestData(t, "azurerm_example_resource", "test")
r := ExampleResourceTest{}
data.ResourceTest(t, r, []acceptance.TestStep{
{
Config: r.basic(data),
Check: acceptance.ComposeTestCheckFunc(
check.That(data.ResourceName).ExistsInAzure(r),
),
},
data.RequiresImportErrorStep(r.requiresImport),
})
}
func (r ExampleResourceTest) requiresImport(data acceptance.TestData) string {
template := r.basic(data)
return fmt.Sprintf(`
%[1]s
resource "azurerm_example_resource" "import" {
name = azurerm_example_resource.example.name
location = azurerm_example_resource.example.location
example_property = azurerm_example_resource.example.example_property
}
`, template)
}This test is used to confirm that the Update function of the Resource works - as such only Required/Optional fields which are not ForceNew can be updated.
The bare-minimum example for this is provisioning the basic configuration and then updating it using the complete test configuration above, for example:
func TestAccExampleResource_update(t *testing.T) {
data := acceptance.BuildTestData(t, "azurerm_example_resource", "test")
r := ExampleResourceTest{}
data.ResourceTest(t, r, []acceptance.TestStep{
{ // first provision the resource
Config: r.basic(data),
Check: acceptance.ComposeTestCheckFunc(
check.That(data.ResourceName).ExistsInAzure(r),
),
},
data.ImportStep(),
{ // then perform the update
Config: r.complete(data),
Check: acceptance.ComposeTestCheckFunc(
check.That(data.ResourceName).ExistsInAzure(r),
),
},
data.ImportStep(),
})
}However this doesn't necessarily cover all of the use-cases for this resource - or may be too broad depending on the resource, as such it's also common to have tests covering a subset of the fields, for example:
Note: This is a simplified example for testing purposes, we'd generally recommend a test covering a related subset of the resource (e.g. enabling/disabling a block within the resource), rather than a single field - but it depends on the resource.
func TestAccExampleResource_someSetting(t *testing.T) {
data := acceptance.BuildTestData(t, "azurerm_example_resource", "test")
r := ExampleResourceTest{}
data.ResourceTest(t, r, []acceptance.TestStep{
{ // first provision the resource
Config: r.someSetting(data, true),
Check: acceptance.ComposeTestCheckFunc(
check.That(data.ResourceName).ExistsInAzure(r),
),
},
data.ImportStep(),
{ // then perform the update to disable this setting
Config: r.someSetting(data, false),
Check: acceptance.ComposeTestCheckFunc(
check.That(data.ResourceName).ExistsInAzure(r),
),
},
data.ImportStep(),
{ // finally, check we can re-enable this once it's been disabled
Config: r.someSetting(data, true),
Check: acceptance.ComposeTestCheckFunc(
check.That(data.ResourceName).ExistsInAzure(r),
),
},
data.ImportStep(),
})
}
func (ExampleResourceTest) someSettingEnabled(data acceptance.TestData) string {
return fmt.Sprintf(`
provider "azurerm" {
features {}
}
resource "azurerm_example_resource" "example" {
name = "my_example_resource"
location = "%s"
}
`, data.Locations.Primary)
}