mocha-param icon indicating copy to clipboard operation
mocha-param copied to clipboard

Parameterized tests for Mocha

Results 7 mocha-param issues
Sort by recently updated
recently updated
newest added

Trying to run a partiulat itparam inside the describe but itparam.only is not valid . Please guide how to run a particular testcase using itparams when we have more it...

Allows backticks in template string.

I find myself often writing tests like this: ```js describe(*name*, function() { itParam(*name*, [ data ], function() { // ... }) // no other tests }) ``` I'd propose to...

It's great that we can use `${value}` inside test names, but sometimes `value` isn't a very descriptive name for a test. To get around this, I often write tests like...

Title says it all, fixes #6. This branch is based on #13, meaning it shouldn't be merged until that one's merged. I did this to avoid regressing the this-context shenanigans....

After about 4 hours of comparing `this` values, getting confused, trying *a lot* of things and more confusion, I **finally** found the (real) solution for #5. Of course, in hindsight...

If you try to run `mocha-param` tests in the Test Explorer VS Code extension, the test runner can't determine whether the tests passed or failed.