Overview

Tracking issue for integ-tests and integ-runner

Link to the service’s CDK Construct Library API reference page.

https://docs.aws.amazon.com/cdk/api/v2/docs/integ-tests-alpha-readme.html

Maturity: CloudFormation Resources Only

Experimental

Implementation

Integ Tests

Features

• 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)
• Access to addPolicyStatementFromSdkCall on AssertionsProvider (turns out there are a lot of permissions it can't figure out)

Integ Runner

Features

• 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

Bugs/Refactor

• Array options should take a list (i.e. --parallel-regions a,b,c) - [medium] fix(integ-runner): array arguments aren't recognizing multiple options #21763
• Git error message should be cleaner, don't need the entire stack trace - [medium]
• Nested stack diff is not working (nested stacks are treated as assets - [medium] chore(integ-runner): use newStyleSynthesis by default #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
• Don't throw error if tests succeed fix(integ-runner): don't throw error if tests pass #20511

Issue list

• [ ]
• [ ]