Skip to content

Conversation

@nija-at
Copy link
Contributor

@nija-at nija-at commented Feb 23, 2021

Move codepipeline-actions from nodeunit to jest. Most tests
now use nodeunit-shim but some tests have been migrated
entirely to pure jest.

Move cluster.test.ts and instance.test.ts in the rds module
from nodeunit-shim to native jest.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

@nija-at nija-at requested review from a team, njlynch and rix0rrr February 23, 2021 10:39
@nija-at nija-at self-assigned this Feb 23, 2021
@gitpod-io
Copy link

gitpod-io bot commented Feb 23, 2021

@github-actions github-actions bot added the @aws-cdk/aws-rds Related to Amazon Relational Database label Feb 23, 2021
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Feb 23, 2021
});

"assigns the Action's Role with read-write permissions to the Bucket if it has both inputs and outputs"(test: Test) {
testFutureBehavior("assigns the Action's Role with read-write permissions to the Bucket if it has both inputs and outputs", s3GrantWriteCtx, App, (app) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

General comment. What's your strategy here with testFutureBehavior on v1? Are we proactively dropping tests for "legacy" behavior already, or supposed to have tests for both behaviors, or some other mix? Feels like by converting this test to testFutureBehavior, we are no longer testing the "legacy" (read: default) behavior.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have a general strategy. It's more applying discretion case-by-case.

In this specific case, the feature flag is changing policy action from s3:PutObject* to s3:PutObject.
This is quite well tested in the s3 module, so in consuming modules (such as the ones in this PR), I'm only testing the future behaviour. Feels redundant to test the legacy behaviour.

@nija-at nija-at requested a review from njlynch February 23, 2021 11:05
@mergify
Copy link
Contributor

mergify bot commented Feb 23, 2021

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@mergify
Copy link
Contributor

mergify bot commented Feb 23, 2021

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@mergify mergify bot merged commit d0d74f2 into master Feb 23, 2021
@mergify mergify bot deleted the nija-at/cpipeline-rds-jest branch February 23, 2021 13:39
@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject89A8053A-LhjRyN9kxr8o
  • Commit ID: 40d5b46
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

@aws-cdk/aws-codepipeline-actions @aws-cdk/aws-rds Related to Amazon Relational Database contribution/core This is a PR that came from AWS.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants