d00528918e
This adds a conformance test checking we can use map keys like "MY_KEY" and maintain their casing through program gen. For Python we need to simplify the type passed to genObjectConsExpression so that we can reliably determine the target type and check if it's a `TypedDict` or not, otherwise we might treat it as a plain object and preserve the keys, instead of `PyName`ing them. This deletes the "typeddict" test from the codegen tests. Firstly this is now covered by these conformance tests, secondly it wasn't actually valid because the schema it was testing against wasn't a valid schema, and the program snapshot was only how it was because of a bug in programgen. That bug is now fixed in this change which fixes https://github.com/pulumi/pulumi/issues/17294. --------- Co-authored-by: Julien Poissonnier <julien@caffeine.lu> |
||
---|---|---|
.. | ||
README.md | ||
dotnet.go | ||
generate.go | ||
go.go | ||
helpers.go | ||
nodejs.go | ||
program_driver.go | ||
program_driver_test.go | ||
python.go | ||
sdk_driver.go | ||
testdata | ||
type_driver.go |
README.md
SDK Codegen Tests
TestSDKCodegen runs the complete set of SDK code generation tests against a particular language's code generator. It also verifies that the generated code is structurally sound.
The test files live in pkg/codegen/testing/test/testdata
and
are registered in the following globals in pkg/codegen/testing/test.
- sdk_driver.go:
PulumiPulumiSDKTests
- program_driver.go:
PulumiPulumiProgramTests
- program_driver.go:
PulumiPulumiYAMLProgramTests
An SDK code generation test files consists of a schema and a set of expected outputs for each language. Each test is structured as a directory that contains that information:
testdata/
my-simple-schema/ # i.e. `simple-enum-schema`
schema.(json|yaml)
go/
python/
nodejs/
dotnet/
...
The schema is the only piece that must be manually authored.
Once the schema has been written, the actual codegen outputs can be
generated by running the following in pkg/codegen
directory:
PULUMI_ACCEPT=true go test ./...
This will rebuild subfolders such as go/
from scratch and store
the set of code-generated file names in go/codegen-manifest.json
.
To generate the code for a specific directory in testdata,
run the following instead:
PULUMI_ACCEPT=true go test ./... -run TestGenerate/$dirName
If these outputs look correct, they need to be checked into git and will then serve as the expected values for the normal test runs:
$ go test ./...
That is, the normal test runs will fail if changes to codegen or
schema lead to a diff in the generated file set. If the diff is
intentional, it can be accepted again via PULUMI_ACCEPT=true
.
Writing Program Tests on Generated Code
To support running unit tests over the generated code, the tests
also support mixing in manually written $lang-extras
files into
the generated tree. For example, given the following input:
testdata/
my-simple-schema/
schema.json
go/
go-extras/
tests/
go_test.go
The system will copy go-extras/tests/go_test.go
into
go/tests/go_test.go
before performing compilation and unit test
checks over the project generated in go
.