docs: update INTEGRATION_TESTS.md #27632
Conversation
| status: 'SUCCEEDED', | ||
| })); | ||
| ``` | ||
|
|
||
| Not every test requires an assertion. We typically do not need to assert CloudFormation behavior. For example, if we create an S3 Bucket | ||
| If we want to pick out certain values from the api call response, we can use the `assertAtPath()` method, as in the [integ.pipeline-with-additional-inputs.ts](https://github.com/aws/aws-cdk/blob/main/packages/%40aws-cdk-testing/framework-integ/test/pipelines/test/integ.pipeline-with-additional-inputs.ts) integ test. Note that using the `outputPaths` optional parameter on the `awsApiCall()` function often interacts poorly with the `expect()` function. |
There was a problem hiding this comment.
Note that using the
outputPathsoptional parameter on theawsApiCall()function often interacts poorly with theexpect()function.
Why is this the case?
There was a problem hiding this comment.
No idea, but it did not work for me, and I have heard from others that it has not worked smoothly for them.
There was a problem hiding this comment.
Ok, it may be better to deprecate this if it is inconsistent. But not blocking this PR :)
vinayak-kukreja
changed the title
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
This updates our docs surrounding integ tests:
assertAtPath()outputPathsinawsApiCall()By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license