You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-18Lines changed: 3 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,9 +27,8 @@ Integration tests are used to verify the behaviour of the root module,
27
27
submodules, and example modules. Additions, changes, and fixes should
28
28
be accompanied with tests.
29
29
30
-
The integration tests are run using [Kitchen][kitchen],
31
-
[Kitchen-Terraform][kitchen-terraform], and [InSpec][inspec]. These
32
-
tools are packaged within a Docker image for convenience.
30
+
The integration tests are run using Golang and
31
+
are packaged within a Docker image for convenience.
33
32
34
33
The general strategy for these tests is to verify the behaviour of the
35
34
[example modules](./examples/), thus ensuring that the root module,
@@ -63,18 +62,7 @@ noninteractively, using the prepared test project.
63
62
64
63
### Interactive Execution
65
64
66
-
1. Run `make docker_run` to start the testing Docker container in
67
-
interactive mode.
68
-
69
-
1. Run `kitchen_do create <EXAMPLE_NAME>` to initialize the working
70
-
directory for an example module.
71
-
72
-
1. Run `kitchen_do converge <EXAMPLE_NAME>` to apply the example module.
73
-
74
-
1. Run `kitchen_do verify <EXAMPLE_NAME>` to test the example module.
75
-
76
-
1. Run `kitchen_do destroy <EXAMPLE_NAME>` to destroy the example module
77
-
state.
65
+
Review the [framework documentation](https://pkg.go.dev/github.com/GoogleCloudPlatform/cloud-foundation-toolkit/infra/blueprint-test#readme-4-test-execution) to learn how to execute tests.
0 commit comments