Closed RLRabinowitz closed 3 years ago
Hi @RLRabinowitz
Thank you very much for the fix
Thank you very much for the fix
Sure, no problem! @rddimon could you merge this for me?
Sure,
We are also working on a new feature for the plugin and planning to release it by the end of next week So be ready for that
Most of the unit tests are not run correctly, since they return a
Promise
and never wait for thatPromise
to resolve, so most of the expectations are not run at all. If you addexpect(true).to.equal(false)
to thethen
of tests usinggetFuncVPC
, the test will wrongfully pass.This is fixed by adding
await
where relevant. However, this has revealed that some tests' inputs and expected outputs are wrong, and some tests are not mocked correctly.initResources
is called.describe("Given invalid input...
, the input data does not match AWS mockdescribe("Given valid inputs...
, the test wrongfully assumes that the plugin filters outsubnetNames
by the input (or this is simply a wrong input)