Assert failed after update assert module

I used Jest with AWS CDK Assert module to test against the CDK output just like example. It was fine when I have @aws/cdk/assert 1.13.1 or the lower version installed.

But after update @aws/cdk/assert to 1.14.0 or 1.15.0, all tests always failed with: None of 0 resources matches resource ....

If I reinstalled @aws/cdk/assert 1.13.1, the tests will pass again. The output of cdk synth & deployment is good though.

Is there a possibility of regression from upgrading 1.13.1 to 1.14.0?

Reproduction Steps

with @aws/cdk/assert 1.14.0 or 1.15.0

class SampleStack extends cdk.Stack {
  constructor(scope, id, props) {
    super(scope, id, props);
    new events.Rule(this, 'timer', {
      description: 'Execute every 5 min',
      schedule: events.Schedule.rate(cdk.Duration.minutes(5)),
    });
  }
}
module.exports = SampleStack;

const { expect: expectCDK, haveResource } = require('@aws-cdk/assert');
...

test('Event Created', () => {
  const app = new cdk.App();
  const stack = new SampleStack(app, 'testStack');

  expectCDK(stack).to(haveResource('AWS::Events::Rule'));
});

Error Log

None of 0 resources matches resource 'AWS::Events::Rule' with properties undefined.

 at HaveResourceAssertion.assertOrThrow (node_modules/@aws-cdk/assert/lib/assertions/have-resource.ts:83:13)
      at StackInspector._to (node_modules/@aws-cdk/assert/lib/inspector.ts:25:15)
      at StackInspector.to (node_modules/@aws-cdk/assert/lib/inspector.ts:15:25)
      at Object.to (test/stack.test.js:16:20)

Environment

• CLI Version : 1.15.0
• Framework Version: 1.15.0
• OS : macOS
• Language : Node.js 12.13.0

Other

---

This is 🐛 Bug Report

[kirintwn]

Hi @RomainMuller ,

After removing node_modules & package-lock.json, reinstalled all @aws-cdk packages with version 1.15.0, the assertion is working as expected again!

Yes, I think it is the case. somehow the upgrade procedure was messed up. Thanks for the heads up!

[RomainMuller]

I guess you may have been bit by having multiple different (possibly incompatible) versions of the @aws-cdk/* libraries in your closure, which can cause unexpected behavior.

Can you comment as to whether this could have been the case?