> **Experimental**
>
> `@aws-cdk/integ-tests-alpha` is an [**experimental**](/stability) (alpha) package: its API may change in any release, without a major version bump.
# IntegTestCaseStackProps

Properties of an integration test case stack.

Extends: IntegTestCaseStackProps
Extends: TestOptions, StackProps
Used as props by: IntegTestCaseStack

- Stability: [Experimental](/cdk/api/stability.html)
- Source: [`lib/test-case.ts`](https://github.com/aws/aws-cdk/blob/v2.274.0-alpha.0/packages/@aws-cdk/integ-tests-alpha/lib/test-case.ts#L75)

## Example

```ts
declare const app: App;
declare const stackUnderTest: Stack;
const testCaseWithAssets = new IntegTestCaseStack(app, 'TestCaseAssets', {
  diffAssets: true,
});

new IntegTest(app, 'Integ', { testCases: [stackUnderTest, testCaseWithAssets] });
```

## Properties

- `allowDeleteFailures`: boolean = 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.

- `allowDestroy`: string[] = do not allow destruction of any resources on update — List of CloudFormation resource types in this stack that can be destroyed as part of an update without failing the test.

  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

- `analyticsReporting`: boolean = `analyticsReporting` setting of containing `App`, or value of 'aws:cdk:version-reporting' context key — Include runtime versioning information in this Stack.

  **Default:** `analyticsReporting` setting of containing `App`, or value of 'aws:cdk:version-reporting' context key

- `cdkCommandOptions`: [CdkCommands](/cdk/api/v2/docs/aws-cdk-lib.cloud_assembly_schema.CdkCommands.html) = runner default options — Additional options to use for each CDK command.

- `crossRegionReferences`: boolean = false — Enable this flag to allow native cross region stack references.

  Enabling this will create a CloudFormation custom resource
  in both the producing stack and consuming stack in order to perform the export/import

  This feature is currently experimental

- `description`: string = No description. — A description of the stack.

- `diffAssets`: boolean = 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

- `env`: [Environment](/cdk/api/v2/docs/aws-cdk-lib.Environment.html) = The environment of the containing `Stage` if available, otherwise create the stack will be environment-agnostic. — The AWS environment (account/region) where this stack will be deployed.

  Set the `region`/`account` fields of `env` to either a concrete value to
  select the indicated environment (recommended for production stacks), or to
  the values of environment variables
  `CDK_DEFAULT_REGION`/`CDK_DEFAULT_ACCOUNT` to let the target environment
  depend on the AWS credentials/configuration that the CDK CLI is executed
  under (recommended for development stacks).

  If the `Stack` is instantiated inside a `Stage`, any undefined
  `region`/`account` fields from `env` will default to the same field on the
  encompassing `Stage`, if configured there.

  If either `region` or `account` are not set nor inherited from `Stage`, the
  Stack will be considered "*environment-agnostic*"". Environment-agnostic
  stacks can be deployed to any environment but may not be able to take
  advantage of all features of the CDK. For example, they will not be able to
  use environmental context lookups such as `ec2.Vpc.fromLookup` and will not
  automatically translate Service Principals to the right format based on the
  environment's AWS partition, and other such enhancements.

  **Default:** The environment of the containing `Stage` if available, otherwise create the stack will be environment-agnostic.

  ```ts
  // Use a concrete account and region to deploy this stack to:
  // `.account` and `.region` will simply return these values.
  new Stack(app, 'Stack1', {
    env: {
      account: '123456789012',
      region: 'us-east-1'
    },
  });

  // Use the CLI's current credentials to determine the target environment:
  // `.account` and `.region` will reflect the account+region the CLI
  // is configured to use (based on the user CLI credentials)
  new Stack(app, 'Stack2', {
    env: {
      account: process.env.CDK_DEFAULT_ACCOUNT,
      region: process.env.CDK_DEFAULT_REGION
    },
  });

  // Define multiple stacks stage associated with an environment
  const myStage = new Stage(app, 'MyStage', {
    env: {
      account: '123456789012',
      region: 'us-east-1'
    }
  });

  // both of these stacks will use the stage's account/region:
  // `.account` and `.region` will resolve to the concrete values as above
  new MyStack(myStage, 'Stack1');
  new YourStack(myStage, 'Stack2');

  // Define an environment-agnostic stack:
  // `.account` and `.region` will resolve to `{ "Ref": "AWS::AccountId" }` and `{ "Ref": "AWS::Region" }` respectively.
  // which will only resolve to actual values by CloudFormation during deployment.
  new MyStack(app, 'Stack1');
  ```

- `hooks`: [Hooks](/cdk/api/v2/docs/aws-cdk-lib.cloud_assembly_schema.Hooks.html) = no hooks — Additional commands to run at predefined points in the test workflow.

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

- `notificationArns`: string[] = no notification arns. — SNS Topic ARNs that will receive stack events.

- `permissionsBoundary`: [PermissionsBoundary](/cdk/api/v2/docs/aws-cdk-lib.PermissionsBoundary.html) = no permissions boundary is applied — Options for applying a permissions boundary to all IAM Roles and Users created within this Stage.

  **Default:** no permissions boundary is applied

- `propertyInjectors`: [IPropertyInjector](/cdk/api/v2/docs/aws-cdk-lib.IPropertyInjector.html)[] = no PropertyInjectors — A list of IPropertyInjector attached to this Stack.

- `regions`: string[] = can run in any region — Limit deployment to these regions.

- `stackName`: string = Derived from construct path. — Name to deploy the stack with.

- `stackUpdateWorkflow`: boolean = 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.

- `suppressTemplateIndentation`: boolean = the value of `@aws-cdk/core:suppressTemplateIndentation`, or `false` if that is not set. — Enable this flag to suppress indentation in generated CloudFormation templates.

  If not specified, the value of the `@aws-cdk/core:suppressTemplateIndentation`
  context key will be used. If that is not specified, then the
  default value `false` will be used.

  **Default:** the value of `@aws-cdk/core:suppressTemplateIndentation`, or `false` if that is not set.

- `synthesizer`: [IStackSynthesizer](/cdk/api/v2/docs/aws-cdk-lib.IStackSynthesizer.html) = The synthesizer specified on `App`, or `DefaultStackSynthesizer` otherwise. — Synthesis method to use while deploying this stack.

  The Stack Synthesizer controls aspects of synthesis and deployment,
  like how assets are referenced and what IAM roles to use. For more
  information, see the README of the main CDK package.

  If not specified, the `defaultStackSynthesizer` from `App` will be used.
  If that is not specified, `DefaultStackSynthesizer` is used if
  `@aws-cdk/core:newStyleStackSynthesis` is set to `true` or the CDK major
  version is v2. In CDK v1 `LegacyStackSynthesizer` is the default if no
  other synthesizer is specified.

  **Default:** The synthesizer specified on `App`, or `DefaultStackSynthesizer` otherwise.

- `tags`: { [key: string]: string } = {} — Tags that will be applied to the Stack.

  These tags are applied to the CloudFormation Stack itself. They will not
  appear in the CloudFormation template.

  However, at deployment time, CloudFormation will apply these tags to all
  resources in the stack that support tagging. You will not be able to exempt
  resources from tagging (using the `excludeResourceTypes` property of
  `Tags.of(...).add()`) for tags applied in this way.

- `terminationProtection`: boolean = false — Whether to enable termination protection for this stack.