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
+7-18
Original file line number
Diff line number
Diff line change
@@ -41,25 +41,14 @@ Integration tests are used to verify the behaviour of the root module,
41
41
submodules, and example modules. Additions, changes, and fixes should
42
42
be accompanied with tests.
43
43
44
-
The integration tests are run using[Kitchen][kitchen],
45
-
[Kitchen-Terraform][kitchen-terraform], and [InSpec][inspec]. These
46
-
tools are packaged within a Docker image for convenience.
44
+
The integration tests are run using[Cloud Foundation Toolkit CLI (CFT CLI)][https://github.com/GoogleCloudPlatform/cloud-foundation-toolkit/tree/main/cli],
45
+
and [Blueprint Test][https://github.com/GoogleCloudPlatform/cloud-foundation-toolkit/tree/main/infra/blueprint-test]. The CFT CLI
46
+
is packaged within a Docker image for convenience.
47
47
48
48
The general strategy for these tests is to verify the behaviour of the
49
49
[example modules](./examples/), thus ensuring that the root module,
50
50
submodules, and example modules are all functionally correct.
51
51
52
-
Six test-kitchen instances are defined:
53
-
54
-
-`deploy-service`
55
-
-`node-pool`
56
-
-`shared-vpc`
57
-
-`simple-regional`
58
-
-`simple-zonal`
59
-
-`stub-domains`
60
-
61
-
The test-kitchen instances in `test/fixtures/` wrap identically-named examples in the `examples/` directory.`
62
-
63
52
### Test Environment
64
53
The easiest way to test the module is in an isolated test project. The
65
54
setup for such a project is defined in [test/setup](./test/setup/)
@@ -101,14 +90,14 @@ noninteractively, using the prepared test project.
101
90
1. Run `make docker_run` to start the testing Docker container in
102
91
interactive mode.
103
92
104
-
1. Run `kitchen_do create <EXAMPLE_NAME>` to initialize the working
93
+
1. Run `cft test run <EXAMPLE_NAME> --stage init` to initialize the working
105
94
directory for an example module.
106
95
107
-
1. Run `kitchen_do converge <EXAMPLE_NAME>` to apply the example module.
96
+
1. Run `cft test run <EXAMPLE_NAME> --stage apply` to apply the example module.
108
97
109
-
1. Run `kitchen_do verify <EXAMPLE_NAME>` to test the example module.
98
+
1. Run `cft test run <EXAMPLE_NAME> --stage verify` to test the example module.
110
99
111
-
1. Run `kitchen_do destroy <EXAMPLE_NAME>` to destroy the example module
100
+
1. Run `cft test run <EXAMPLE_NAME> --stage destroy` to destroy the example module
0 commit comments