ccea866721
Multiple conformance tests can use the same provider. When a provider gets used for a test we install all its dependencies. Then in subsequent runs, when the provider is re-used those dependencies are already in the directory, and we complain that those newly installed dependencies don't exist in the original snapshot. Fix this by cleaning up the sdks directory after each run, so we get a clean slate each time we codegen a provider. We could potentially consider getting a list of providers when preparing the language tests, and just generating their code once, but that's a little bit more involved. Fixes https://github.com/pulumi/pulumi/issues/15603 |
||
|---|---|---|
| .. | ||
| testdata | ||
| README.md | ||
| bad_provider.go | ||
| go.mod | ||
| go.sum | ||
| interface.go | ||
| interface_test.go | ||
| internal_test.go | ||
| l1empty_test.go | ||
| l1main_test.go | ||
| l2destroy_test.go | ||
| l2resourcesimple_test.go | ||
| main.go | ||
| runtime_options_test.go | ||
| simple_provider.go | ||
| testing.go | ||
| tests.go | ||
README.md
pulumi-language-test runs a gRPC interface that language plugins can use to run a suite of standard tests.
Architecture
pulumi-language-test is used to run a standard suite of tests against any compliant language plugin.
The diagram below shows the main interactions and data flows for how this system works.
There are three main actors involved. Firstly test which is a test function coordinating the language plugin and pulumi-language-test. Secondly ptl which is the pulumi-language-test process. Finally uut which is the language plugin actually being tested. This will generally be a grpc server running in the same process as the test method.
sequenceDiagram
test->>ptl: Start ptl process
ptl-->>test: Read stdout for ptl address to connect to
Note right of test: All future calls to ptl are via grpc
test->>+ptl: GetLanguageTests()
ptl-->>-test: Returns list of test names
test->>+uut: Serve
uut-->>-test: Returns uut server address
test->>+ptl: PrepareLanguageTests(uut)
ptl->>+uut: Pack(core)
uut-->>-ptl: Returns name of core artifact
ptl-->>-test: Returns `token`
loop for each test
test->>+ptl: RunLanguageTest(token, test)
loop for each sdk used in test
ptl->>+uut: GeneratePackage(sdk)
uut-->>-ptl: Write package code to temporary directory
ptl->>ptl: Verify sdk snapshot
ptl->>+uut: Pack(sdk)
uut-->>-ptl: Returns name of sdk artifact
end
ptl->>+uut: GenerateProject(test)
uut-->>-ptl: Write project code to temporary directory
ptl->>ptl: Verify project snapshot
ptl->>+uut: InstallDependencies(project)
uut-->>-ptl:
note right of ptl: Execute test with engine
activate ptl
ptl->>+uut: Run(project)
uut-->>-ptl: Return run result
ptl->>ptl: Run test asserts against run result and snapshot
deactivate ptl
ptl-->>-test: Returns test result from asserts
end
test->>ptl: sigkill
Meta tests
This module contains a number of _test.go files. These are tests of the conformance test system itself. The actual conformance tests are all defined in tests.go.