Tracking: [Integration Tests]

Tracking issue for integ-tests and integ-runner

Experimental

[ ] Add HttpApiCall similar to AwsApiCall (in progress)
[ ] Add the ability to have the assertions "wait" for something to occur (in progress)
- [ ] Move assertion into the *ApiCall resources (in progress)
[x] Access to addPolicyStatementFromSdkCall on AssertionsProvider (turns out there are a lot of permissions it can't figure out)

[ ] Automatically remove assets above a certain size (e.g. 20KB) - [high]
[ ] Add a tests remaining log (maybe only if # of tests is > something) - [low]
[ ] Allow filter by package name (or glob filter, etc) e.g. yarn integ 'aws-lambda/*' - [low]
[ ] Add flag to integ manifest to skip during automation - [low]
[ ] Add mass bootstrap of accounts/regions that are used - [low]
[ ] Add flag to disable snapshot creation
[ ] Add a flag to disable snapshots altogether (don't create or diff snapshots)
[ ] Report failed status on individual test cases/stacks

[X] Array options should take a list (i.e. --parallel-regions a,b,c) - [medium] https://github.com/aws/aws-cdk/pull/21763
[ ] Git error message should be cleaner, don't need the entire stack trace - [medium]
[X] Nested stack diff is not working (nested stacks are treated as assets - [medium] https://github.com/aws/aws-cdk/pull/21856
[ ] Rework snapshot git checkout. Ideally this should pull from the last release, but this only works for construct use cases
[ ] Store metadata (destructive changes, dry-run, etc) in a separate file
[x] Don't throw error if tests succeed https://github.com/aws/aws-cdk/pull/20511

aws / aws-cdk