You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
data: 'cron: If you don\'t pass \'minute\', by default the event runs every minute. Pass \'minute: \'*\'\' if that\'s what you intend, or \'minute: 0\' to run once per hour instead.',
trace: undefined,
}]);
And many more places in the CDK. The problem is that they assert on a specific node.metadataentry, but if we ever add a different message to the node metadata, this test will fail.
This happens many times when we add warnings around the CDK, see #19464.
Does this for everything except the tests in core that are specifically testing `Aspects`. There's less of a chance that those tests are disturbed by adding annotations elsewhere in the CDK.
Closes#19544
----
*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Does this for everything except the tests in core that are specifically testing `Aspects`. There's less of a chance that those tests are disturbed by adding annotations elsewhere in the CDK.
Closesaws#19544
----
*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
What is the problem?
See:
aws-cdk/packages/@aws-cdk/aws-applicationautoscaling/test/scalable-target.test.ts
Lines 98 to 102 in a349666
And many more places in the CDK. The problem is that they assert on a specific
node.metadataentry
, but if we ever add a different message to the node metadata, this test will fail.This happens many times when we add warnings around the CDK, see #19464.
Reproduction Steps
see linked file.
What did you expect to happen?
These tests should be changed to:
also:
This will be more robust as it does not depend on the existence/non-existence of other messages on the node.
What actually happened?
Possible failing tests in the future.
CDK CLI Version
latest
Framework Version
No response
Node.js Version
latest
OS
Mac
Language
Typescript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: