Add initial version of a plugin-framework provider config test, move code between packages to allow tests #6180
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR begins to add tests that match equivalent tests created for the SDK version of the provider config code. The motivation of adding these tests is to ensure parity between the SDK and plugin framework versions of the provider config code, as muxing the provider resulted in bugs like: hashicorp/terraform-provider-google#14255
Currently there isn't parity in how the two bits of code handle empty strings (see commented out test cases) and I will address that in a separate PR to this one.
To allow the tests to be created I needed to move code between packages to allow reuse of test-related functions and to avoid circular dependencies.
If this PR is for Terraform, I acknowledge that I have:
make test
andmake lint
in the generated providers to ensure it passes unit and linter tests.Release Note Template for Downstream PRs (will be copied)
Derived from GoogleCloudPlatform/magic-modules#8797