chore: migrate aws-cdk from nodeunit to jest #5659
Merged
+2,714
−3,056
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is some interesting magic happening around the runtime-info
module:
jest
replaces the standardrequire
function so it can honormodule mocking requirements, however this does (intentionally) not
implement
require.cache
, which is used to determine which CDKlibraries are loaded during a particular execution (in order to populate
the
AWS::CDK::Metadata
resource as needed).In order to work around this, the
require.cache
reading was indirectedthrough a proxy module, so it can be stubbed, too, with a pretend cache
content, in order to make the test still workable.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license