@aws-cdk-testing/cli-integ 0.0.0

package/resources/cloud-assemblies/1.10.0-lookup-default-vpc/manifest.json.js

@@ -0,0 +1,37 @@
+process.stdout.write(JSON.stringify({
+  "version": "1.10.0",
+  "artifacts": {
+    "InitStack": {
+      "type": "aws:cloudformation:stack",
+      "environment": `aws://${process.env.TEST_ACCOUNT}/${process.env.TEST_REGION}`,
+      "properties": {
+        "templateFile": "InitStack.template.json"
+      }
+    }
+  },
+  "runtime": {
+    "libraries": {
+      "@aws-cdk/core": "1.14.0",
+      "@aws-cdk/cx-api": "1.14.0",
+      "@aws-cdk/aws-ec2": "1.14.0",
+      "@aws-cdk/aws-iam": "1.14.0",
+      "@aws-cdk/region-info": "1.14.0",
+      "@aws-cdk/aws-ssm": "1.14.0",
+      "@aws-cdk/aws-cloudwatch": "1.14.0",
+      "jsii-runtime": "node.js/v8.11.4"
+    }
+  },
+  "missing": [
+    {
+      "key": `vpc-provider:account=${process.env.TEST_ACCOUNT}:filter.isDefault=true:region=${process.env.TEST_REGION}`,
+      "props": {
+        "account": process.env.TEST_ACCOUNT,
+        "region": process.env.TEST_REGION,
+        "filter": {
+          "isDefault": "true"
+        }
+      },
+      "provider": "vpc-provider"
+    }
+  ]
+}, undefined, 2));

package/resources/cloud-assemblies/1.10.0-request-azs/InitStack.template.json

@@ -0,0 +1,2 @@
+{
+}

package/resources/cloud-assemblies/1.10.0-request-azs/cdk.out

@@ -0,0 +1 @@
+{"version":"1.10.0"}

package/resources/cloud-assemblies/1.10.0-request-azs/manifest.json.js

@@ -0,0 +1,34 @@
+process.stdout.write(JSON.stringify({
+  "version": "1.10.0",
+  "artifacts": {
+    "InitStack": {
+      "type": "aws:cloudformation:stack",
+      "environment": `aws://${process.env.TEST_ACCOUNT}/${process.env.TEST_REGION}`,
+      "properties": {
+        "templateFile": "InitStack.template.json"
+      }
+    }
+  },
+  "runtime": {
+    "libraries": {
+      "@aws-cdk/core": "1.14.0",
+      "@aws-cdk/cx-api": "1.14.0",
+      "@aws-cdk/aws-ec2": "1.14.0",
+      "@aws-cdk/aws-iam": "1.14.0",
+      "@aws-cdk/region-info": "1.14.0",
+      "@aws-cdk/aws-ssm": "1.14.0",
+      "@aws-cdk/aws-cloudwatch": "1.14.0",
+      "jsii-runtime": "node.js/v8.11.4"
+    }
+  },
+  "missing": [
+    {
+      "key": `availability-zones:account=${process.env.TEST_ACCOUNT}:region=${process.env.TEST_REGION}`,
+      "props": {
+        "account": process.env.TEST_ACCOUNT,
+        "region": process.env.TEST_REGION,
+      },
+      "provider": "availability-zones"
+    }
+  ]
+}, undefined, 2));

package/resources/integ.jest.config.js

@@ -0,0 +1,25 @@
+const path = require('path');
+
+const rootDir = path.resolve(__dirname, '..', 'tests', process.env.TEST_SUITE_NAME);
+
+if (rootDir.includes('node_modules')) {
+  // Jest < 28 under no circumstances supports loading test if there's node_modules anywhere in the path,
+  // and Jest >= 28 requires a newer TypeScript version than the one we support.
+  throw new Error(`This package must not be 'npm install'ed (found node_modules in dir: ${rootDir})`);
+}
+
+module.exports = {
+  rootDir,
+  testMatch: [`**/*.integtest.js`],
+  moduleFileExtensions: ["js"],
+
+  testEnvironment: "node",
+  testTimeout: 300000,
+
+  // Affects test.concurrent(), these are self-limiting anyway
+  maxConcurrency: 10,
+  reporters: [
+    "default",
+    [ "jest-junit", { suiteName: "jest tests", outputDirectory: "coverage" } ]
+  ]
+};

package/resources/templates/sqs-template.json

@@ -0,0 +1,36 @@
+{
+  "AWSTemplateFormatVersion": "2010-09-09",
+  "Description": "AWS CloudFormation Sample Template SQS_With_CloudWatch_Alarms: Sample template showing how to create an SQS queue with AWS CloudWatch alarms on queue depth.",
+  "Resources": {
+    "MyQueue": {
+      "Type": "AWS::SQS::Queue",
+      "Properties": {}
+    }
+  },
+  "Outputs": {
+    "QueueURL": {
+      "Description": "URL of newly created SQS Queue",
+      "Value": {
+        "Ref": "MyQueue"
+      }
+    },
+    "QueueARN": {
+      "Description": "ARN of newly created SQS Queue",
+      "Value": {
+        "Fn::GetAtt": [
+          "MyQueue",
+          "Arn"
+        ]
+      }
+    },
+    "QueueName": {
+      "Description": "Name newly created SQS Queue",
+      "Value": {
+        "Fn::GetAtt": [
+          "MyQueue",
+          "QueueName"
+        ]
+      }
+    }
+  }
+}

package/skip-tests.txt

@@ -0,0 +1,8 @@
+# This file is empty on purpose. Leave it here as documentation
+# and an example.
+#
+# Copy this file to resources/cli-regression-patches/vX.Y.Z/skip-tests.txt
+# and edit it there if you want to exclude certain tests from running
+# when performing a certain version's regression tests.
+#
+# Put a test name on a line by itself to skip it.

package/tests/cli-integ-tests/README.md

@@ -0,0 +1,47 @@
+# CDK CLI Integration Tests
+
+These tests require AWS credentials, and exercise various aspects of the
+CLI on a simple JavaScript CDK app (stored in `app/`).
+
+## Entry point
+
+```
+../run-against-repo ./test.sh
+```
+
+Running against a failing dist build:
+
+```
+# Download and unpack the zip
+.../CMkBR4V$ tar xzvf js/aws-cdk-[0-9]*.tgz
+.../CMkBR4V$ package/test/integ/run-against-dist package/test/integ/cli/test.sh
+```
+
+## Adding tests
+
+Even though tests are now written in TypeScript, this does not
+conceptually change their SUT! They are still testing the CLI via
+running it as a subprocess, they are NOT reaching directly into the CLI
+code to test its private methods. It's just that setup/teardown/error
+handling/assertions/AWS calls are much more convenient to do in a real
+programming language.
+
+Compilation of the tests is done as part of the normal package build, at
+which point it is using the dependencies brought in by the containing
+`aws-cdk` package's `package.json`.
+
+When run in a non-development repo (as done during integ tests or canary runs),
+the required dependencies are brought in just-in-time via `test.sh`. Any
+new dependencies added for the tests should be added there as well. But, better
+yet, don't add any dependencies at all. You shouldn't need to, these tests
+are simple.
+
+## Configuration
+
+AWS credentials must be configured.
+
+Optional configuration:
+
+* `AWS_DEFAULT_REGION`, what region to deploy the stacks in.
+* `IS_CANARY`, true or false. Affects the default stack name prefix to make
+  integration test and canary runs unique.

package/tests/cli-integ-tests/bootstrapping.integtest.d.ts

@@ -0,0 +1 @@
+export {};