The following spec fails with a timeout but should fail with a message that explains that a promise was expected to be resolved:

  it('should fail with something other than a timeout', function() {
    var p = new Promise(function() {});
    return expectAsync(p).toBeResolved();
  });

Most of the async matchers have this problem, with the notable exception of toBePending.

Describe the bug
When TEMPLATE_LIST_TEST_CASE and TEMPLATE_LIST_TEST_CASE_METHOD were added, the corresponding versions with the CATCH_ prefix were missed.

Expected behavior
CATCH_TEMPLATE_LIST_TEST_CASE and CATCH_TEMPLATE_LIST_TEST_CASE_METHOD should be available.

Additional context

The commit that added TEMPLATE_LIST_TEST_CASE and `TEMPLATE_LIST_TEST_CASE_MET

@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

Is your feature request related to a problem? Please describe.
Reading through what a fake can and can not do is not clear from the documentation.

Describe the solution you'd like
Exact methods that are available to a Fake need to be documented.

First of all thank you for Sinon, I believe the library is powerful and has helped me write a lot of tests. What I'm requesting here is

1. General summary of the issue

When running Pester, it now includes all the discovered tests even when you specify a -Tag, the tests that fall outside the tag filter, get deposited in the xml file.

2. Describe Your Environment

Pester version : 5.0.3 C:\Program Files\WindowsPowerShell\Modules\Pester\5.0.3\Pester.psd1
PowerShell version : 5.1.14409.1018
OS version : Micr

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

Describe the problem

InSpec has disabled built_in:tag_docker_images as it no longer exists in expeditor. We need to replace this functionality.

Possible Solution

Expeditor now has built_in:promote_docker_images which we can use to accomplish this. However, it is not a drop-in replacement and needs a dobi.yml to describe how things need to be tagged.

When we get here, might n

When running build.ps1 -t Test, the following output describes the failing tests:

1. Failed : NUnit.Framework.Api.FrameworkControllerTests.ExploreTestsAction_FileNotFound_ReturnsNonRunnableSuite
   Expected: String containing "The system cannot find the file specified."
   But was: "Le fichier sp├®cifi├® est introuvable. (Exception from HRESULT: 0x80070002)"
   at NUnit.Framework.Api.Framew

Hi,

When I run my tests using the neovim strategy, it opens a new terminal but auto focus on the buffer. Then I have to press <C-o> to not close the buffer and go back to my split pane.

Is there a way to have it open but not switch my focus to the newly opened pane automatically?

💡 Idea

Today, we do not have a type for WebUrlContraints. Intead of hardcoding the typings in the function webUrl itself:

{ authoritySettings?: WebAuthorityConstraints; validSchemes?: string[]; withFragments?: undefined | false | true; withQueryParameters?: undefined | false | true }

We should extract it into a clear type called WebUrlContraints (see `WebAuthorityConstr

Hi, when implementing http4k/http4k#435 I noticed the codebase does not have a linter set up - e.g. some files end with new lines and some don't.

I am not sure whether this is desired, I would be happy to participate if wanted.

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