Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define "Update" test scenario implementation details #15

Open
ezgidemirel opened this issue Jun 8, 2022 · 0 comments
Open

Define "Update" test scenario implementation details #15

ezgidemirel opened this issue Jun 8, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@ezgidemirel
Copy link
Member

Update scenario is harder to test due to some conditions we need to satisfy. To update a resource, we need to find a
mutable field and set a proper value. Terraform provider metadata has mutable fields and we may use this information to generate a second example manifest to test update scenarios. Please note that, while generating a second example manifest, we may hit some input validation issues. For these kinds of issues, we may use a configuration framework that allows developers to set some mutable field values.

Another alternative we can use is updating fields like tags and labels whenever a resource has them. As stated in
this Tagging Convention Issue, roughly half of the resources have one of these fields. Even though it prevents the input validation issues and the work that needs to be done to generate a second manifest, the number of resources we can test may not be worth integrating into the testing pipeline.

@ezgidemirel ezgidemirel added the enhancement New feature or request label Jun 8, 2022
@jeanduplessis jeanduplessis transferred this issue from another repository Oct 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant