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

cdktf/testing: Add shouldTerraformApplyAndDestroy #3703

Open
1 task
so0k opened this issue Aug 17, 2024 · 1 comment
Open
1 task

cdktf/testing: Add shouldTerraformApplyAndDestroy #3703

so0k opened this issue Aug 17, 2024 · 1 comment
Labels
enhancement New feature or request new Un-triaged issue

Comments

@so0k
Copy link

so0k commented Aug 17, 2024

Description

Comparing cdktf/testing library to terratest, would it make sense to add full end to end testing helpers?

For example, a complex VPC Construct may want to confirm connectivity works once everything is provisioned... what is the recommended integration testing for CDKTF?

Suggestion:

  • Add shouldTerraformApplyAndDestroy matcher with optional Validate function argument called in between apply and destroy

Alternatively, rely fully on terraform test for full integration testing and add support for test command in cdktf-cli.

References

Help Wanted

  • I'm interested in contributing a fix myself

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@so0k so0k added enhancement New feature or request new Un-triaged issue labels Aug 17, 2024
@so0k so0k changed the title cdktf/testing: shouldTerraformApply cdktf/testing: Add shouldTerraformApplyAndDestroy Aug 17, 2024
@vincenthsh
Copy link

ideally also add to cdktf-vitest for those using vitest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request new Un-triaged issue
Projects
None yet
Development

No branches or pull requests

2 participants