test-driven-development

Is your feature request related to a problem? Please describe.

If you want to use sinon with mocha, you shouldn't forget to restore the sinon sandbox after each test. This is documented here in general setup.

Since version 7.2, mocha supports root hooks. It is a way to export mocha root hooks (beforeEach, afterEach etc) fr

I have two setups, in one the -parallel option works just fine in vscode - it generates parallel test cases as it should. In the other it doesn't do anything (not reporting errors in custom flags is a problem in the vscode go plugin, which is not the issue here).

Both were installed with go get -u github.com/cweill/gotests/... when in the $HOME directory within 15 minutes of each other.

This is a corner case that I only ran into in due to work on the analyzers in nunit/nunit.analyzers#54, and my guess is that very few will run into this problem. Nevertheless, I think we could improve the error message, and fix seems simple and safe.

Given a generic test method with no parameters we get a failure that is difficult to interpret for the users (see last example below for more deta

The xterm terminal does not fit to the parent container on load because of the hidden prop used in the tab component for the terminal which initializes the parent component with a width and height of 0, therefore fitaddon does not initialize according to the bounds and only works when switching back and forth to the terminal.

What do you want to add to the docs? (please state reasons if any)

Add a GitPod badge to the readme.

For example : https://img.shields.io/badge/Gitpod-ready--to--code-FFB45B?logo=gitpod

Where is this stated?

Currently, we're using Gitpod of a quick demonstration of Keploy with a sample application. Adding a badge would be easier navigation for visitors.