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:

Describe the bug
when I turn on CATCH_CONFIG_DISABLE, all CAPTURE(i,j) , i.e. more than one arg will err.

Expected behavior
No such error

Reproduction steps
Build below code with -DCATCH_CONFIG_DISABLE

#include "catch.hpp"

TEST_CASE("generators") {
    auto i = GENERATE(as<std::string>(), "a", "b", "c");
    SECTION("one") {
        auto j = GENERATE(range(8, 11

Is your feature request related to a problem? Please describe.
Today we silently ignore stubbing issues, such as trying to use sinon.stub(obj, 'prop'), when obj.prop is a synthetic getter. From a user perspective, it is probably more user friendly to be explicitly told immediately that this Object.descriptor is non-configurable (perhaps even with a link to a Sinon doc page!) and cannot be

They are all currently written in groovy; I'd like to migrate them to the build.gradle.kts format to make the whole project Kotlin-based.

I think this can be done in steps, migrating one build.gradle file at a time - not sure about it though.

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

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

Before you file a bug, have you:

• Tried upgrading to newest version of Fluent Assertions, to see if your issue has already been resolved and released?
• Checked existing open and closed issues, to see if the issue has already been reported?
• Tried reproducing your problem in a new isolated proje

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

The NUnitEqualityComparer contains an optional parameter in the public API to specify if the comparison is top-level or not.
https://github.com/nunit/nunit/blob/8de9af1d695d42d2d85604a100ff9f6c00e5728f/src/NUnitFramework/framework/Constraints/NUnitEqualityComparer.cs#L157

This has been converted to separate overloads in a subsequent PR. nunit/nunit#3406

That PR also

The OpenApi specification allows top-level servers object to be specified:

Field Name	Type	Description
servers	[Server Object]	An array of Server Objects, which provide connectivity information to a target server. If the servers