chai | TDD assertion framework for node.js and the browser | Unit Testing library

I encountered the same problem.

Apparently, the csv-writer package contains tests, like array.test.ts specified in your stack trace.

This is your script used for running the mocha tests:

Coming from documentation for zip

Make an iterator that aggregates elements from each of the iterables. Returns an iterator of tuples, where the i-th tuple contains the i-th element from each of the argument sequences or iterables.

Yes that is completely normal because zip returns an iterator and iterators are evaluated only once, so when you uncomment your print statement, the iterator is evaluated at that time, and later when you try to form dictionary out of the zip object, the iterator has nothing at all, all the values are already yielded by that time.

The code snippet from documentation:

I know is a pretty old question but if someone else find themself in the situation I've managed to find a solutions:

Add this line before RUN npm install:

Mocha doesn't invoke the Serverless Framework, so those variables are never parsed from the ENV file (because the serverless.yml file is never read/interpolated).

Instead you should use something like dotenv to parse that file and set variables in your test environment. Or just manually set a few directly on process.env in a beforeAll() function.

Change: $ref: '#components/schemas/Flashcard' to: $ref: '#/components/schemas/Flashcard' (you missed the /)

Also add this into the first get (/flashcard/{id}:) to return the correct type:

the solution is:

This is an example to how to stub ioredis Redis.prototype.connect.

before I try, I would like to suggest to drop the try/catch blocks everywhere, I will assume you're using expressJs in your Node application, and for such, take a look at express-promise-router as using that Router (instead the default one) will automatically catch anything it was thrown and you just need to focus on the code...

taking your example, you would write: