Skip to content
v2.274.0

TestCase Struct ​

Represents an integration test case.

Example ​

ts
// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
import { cloud_assembly_schema } from 'aws-cdk-lib';
const testCase: cloud_assembly_schema.TestCase = {
  stacks: ['stacks'],

  // the properties below are optional
  allowDeleteFailures: false,
  allowDestroy: ['allowDestroy'],
  assertionStack: 'assertionStack',
  assertionStackName: 'assertionStackName',
  cdkCommandOptions: {
    deploy: {
      args: {
        all: false,
        app: 'app',
        assetMetadata: false,
        caBundlePath: 'caBundlePath',
        changeSetName: 'changeSetName',
        ci: false,
        color: false,
        concurrency: 123,
        context: {
          contextKey: 'context',
        },
        debug: false,
        ec2Creds: false,
        exclusively: false,
        execute: false,
        force: false,
        ignoreErrors: false,
        json: false,
        lookups: false,
        notices: false,
        notificationArns: ['notificationArns'],
        output: 'output',
        outputsFile: 'outputsFile',
        parameters: {
          parametersKey: 'parameters',
        },
        pathMetadata: false,
        profile: 'profile',
        proxy: 'proxy',
        requireApproval: cloud_assembly_schema.RequireApproval.NEVER,
        reuseAssets: ['reuseAssets'],
        roleArn: 'roleArn',
        rollback: false,
        stacks: ['stacks'],
        staging: false,
        strict: false,
        toolkitStackName: 'toolkitStackName',
        trace: false,
        usePreviousParameters: false,
        verbose: false,
        versionReporting: false,
      },
      enabled: false,
      expectedMessage: 'expectedMessage',
      expectError: false,
    },
    destroy: {
      args: {
        all: false,
        app: 'app',
        assetMetadata: false,
        caBundlePath: 'caBundlePath',
        color: false,
        context: {
          contextKey: 'context',
        },
        debug: false,
        ec2Creds: false,
        exclusively: false,
        force: false,
        ignoreErrors: false,
        json: false,
        lookups: false,
        notices: false,
        output: 'output',
        pathMetadata: false,
        profile: 'profile',
        proxy: 'proxy',
        roleArn: 'roleArn',
        stacks: ['stacks'],
        staging: false,
        strict: false,
        trace: false,
        verbose: false,
        versionReporting: false,
      },
      enabled: false,
      expectedMessage: 'expectedMessage',
      expectError: false,
    },
  },
  diffAssets: false,
  hooks: {
    postDeploy: ['postDeploy'],
    postDestroy: ['postDestroy'],
    preDeploy: ['preDeploy'],
    preDestroy: ['preDestroy'],
  },
  regions: ['regions'],
  stackUpdateWorkflow: false,
};

Properties ​

allowDeleteFailuresbooleanallow_delete_failuresboolallowDeleteFailuresBooleanAllowDeleteFailuresboolAllowDeleteFailures*bool= false#
Whether to allow resources that fail to delete during a stack update.

When false, the test will fail if CloudFormation skips deleting a resource during a stack update. When true, only a warning is printed.

allowDestroystring[]allow_destroytyping.List[str]allowDestroyList<String>AllowDestroystring[]AllowDestroy*[]*string= do not allow destruction of any …#
List of CloudFormation resource types in this stack that can be destroyed as part of an update without failing the test.
notes · default

This list should only include resources that for this specific integration test we are sure will not cause errors or an outage if destroyed. For example, maybe we know that a new resource will be created first before the old resource is destroyed which prevents any outage.

e.g. ['AWS::IAM::Role']

Default: do not allow destruction of any resources on update

assertionStackstringassertion_stackstrassertionStackStringAssertionStackstringAssertionStack*string= no assertion stack#
The node id of the stack that contains assertions.

This is the value that can be used to deploy the stack with the CDK CLI

assertionStackNamestringassertion_stack_namestrassertionStackNameStringAssertionStackNamestringAssertionStackName*string= no assertion stack#
The name of the stack that contains assertions.
cdkCommandOptionsCdkCommandscdk_command_optionsCdkCommandscdkCommandOptionsCdkCommandsCdkCommandOptionsCdkCommandsCdkCommandOptionsCdkCommands= runner default options#
Additional options to use for each CDK command.
diffAssetsbooleandiff_assetsbooldiffAssetsBooleanDiffAssetsboolDiffAssets*bool= false#
Whether or not to include asset hashes in the diff Asset hashes can introduces a lot of unneccessary noise into tests, but there are some cases where asset hashes _should_ be included.

For example any tests involving custom resources or bundling

hooksHookshooksHookshooksHooksHooksHooksHooksHooks= no hooks#
Additional commands to run at predefined points in the test workflow.

e.g. { postDeploy: ['yarn', 'test'] }

regionsstring[]regionstyping.List[str]regionsList<String>Regionsstring[]Regions*[]*string= can run in any region#
Limit deployment to these regions.
stacksstring[]stackstyping.List[str]stacksList<String>Stacksstring[]Stacks*[]*stringrequired#
Stacks that should be tested as part of this test case The stackNames will be passed as args to the cdk commands so dependent stacks will be automatically deployed unless `exclusively` is passed.
stackUpdateWorkflowbooleanstack_update_workflowboolstackUpdateWorkflowBooleanStackUpdateWorkflowboolStackUpdateWorkflow*bool= true#
Run update workflow on this test case This should only be set to false to test scenarios that are not possible to test as part of the update workflow.