Are you creating an issue in the correct repository?

• When in doubt, create an issue here.
• If you have an issue with the Jasmine docs, file an issue in the docs repo
  here: https://github.com/jasmine/jasmine.github.io
• This repository is for the core Jasmine framework

• If you are using a test runner that wraps Jasmine, consider filing an issue with that library if appropriate:

CMake Warning at <hidden>/Catch2/v2.13.7/Catch2_Release/lib/cmake/Catch2/CatchAddTests.cmake:46 (message):
  Test executable
  '<hidden>'
  contains no tests!

Adding another test makes the error go away. 😄

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

The test suite is currently split between two organization models: some tests are organized by the component, or the feature, they test (like this), and a lot of tests are organized by the number of the GitHub issue they verify (like [this](https://github.com/mockk/mockk/blob/master/mockk/jvm/s

Let's add MinVer and on successful builds generate a release.

This PR contains the following updates:

Description

Nested AssertionScopes only report the outer-most scope reportables on failure. This is true regardless of whether the outer scope has any reportables -- i.e., if only the inner scope has reportables, nothing is reported.

Complete minimal example reproducing the issue

[TestMethod]
public void TestNestedAssertionScopes()
{
    using (var outerScope = new A

Summary of the feature request

As a contributor or maintainer of a project I'd like to be able to help other contributors to correctly mock functions by failing a test if a mock does not exist. This would be very useful in situations when there are very complex scripts that handle a lot of scenarios and using a lot of external helper functions.

The ask would be to add a new parameter to `Mo

The command exist test always returns true regardless of if the command is invalid.

Describe the problem

On Windows, we want to test if a command/cmdlet exists before running it. However, the 'command().exist?‘ test always returns true no matter what command t

For the longest time I was able to access the pry console while running tests using :TestNearest, but it hasn't been working of late. I am able to run tests using :TestNearest and the other vim-test commands. My issue is that if I throw in a binding.pry in the test, I don't see the pry console open up anymore in the test window. That used to work before, and I can't figure out why. I'm

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