Run uptest Update tests for most resources #1151
Comments
|
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as |
|
/fresh |
|
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as |
|
/fresh |
|
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as |
|
/fresh |
What problem are you facing?
From time to time, we encounter bugs in provider-aws that are not caught by our e2e test suite, uptest, because they only occur when a resource is being updated.
For some of these bugs, only a particular, resource-specific type of update triggers these bugs. To effectively write a test for them requires domain-specific knowledge related to the resource. The only solution I can think of for improvement here is to provide better documentation and examples of how to test updates using uptest.
For other bugs, any update at all will work. Given that many/most aws resources have a
spec.forProvider.tagsfield, which can contain arbitrary data, this seems like a "better than nothing" good starting place, to validate that in addition to creating, importing, and deleting a resource, provider-aws can also update the resource's tags.How could Official AWS Provider help solve your problem?
For all resources which have a
spec.forProvider.tagsfield, make a change to it during the Update step of uptest, rather than skipping the Update step.The text was updated successfully, but these errors were encountered: