@benoittgt very kindly submitted a PR to fix some spacing issues in the markdown using gofmtmd.

It should be possible to automate this as part of the build script

Expected Behavior

The test case passes, and ? isn't treated as the regex char

Current Behavior

The raw ? gets treated as a regex char instead of a literal ?

Possible Solution

Some sort of regex escaper?

Suite that reproduces the behavior (for bugs)

<

Description

I have a hardware abstraction layer interface, as well as a driver interface. I have multiple drivers utilizing the HAL interface, while implementing the driver interface. This plugin approach causes me to have identically named tests across multiple test files.

For example:

TEST_CASE("init() returns `E_HAL_INIT`, when HardwareAbstractionLayer::init() returns an er

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

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

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 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

Feature Request

Description:
API for Date matchers. Some matchers are inspired by Jasmine Matchers.

Possible solution:

Jasmine-like matchers:

expect(date).toBeDate(); // Matcher added
expect(date).toBeValidDate();  // Matcher added

expect(date).toBeAfter(otherDate); // Matcher added
expect(date).toBeBefore(otherDa