I'm getting bit with failing documentation builds because I'm writing docstrings that JSDoc doesn't like (specifically, TS-style). But there's no linting happening before getting to Netlify.

We may be able to make JSDoc just check the syntax and exit (and make it part of the lint scripts).

This is moot if we want to move forward with maintaining our own TS types (for which there is an op

Spurred by conversation in avajs/ava#2449 and avajs/ava#1485 we'd like for our assertions to return booleans. true when they pass, false when they fail. This does not apply to the throws() and throwsAsync() assertions.

Failing assertions will fail the test, but do not throw exceptions. This means your test does not stop executing. Usua

Expected Behavior

const sym = Symbol('foo');
expect({}).toEqual({[sym]: 'foo'});

This test should fail. It currently passes.

Current Behavior

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

Is there any guide on writing a launcher? Looking over the current implementations there didn't seem to be much consistency. Looking for best practices.

In this section (which needs a little grammar tidying as well), the code . command is not enabled by default, so doesn't immediately work as a check that Visual Studio Code is installed correctly: https://quii.gitbook.io/learn-go-with-tests/go-fundamentals/install-go#go-editor

Visual Studio includes instructions for enabling this wonderful shortcut here: https://code.visualstudio.com/docs/set

Describe the bug
When the (string) representations of the expected outcome and the actual outcome of e.g. assert.calledWith() are equal, the resulting error message is very confusing and hinting at a bug in the display logic. Instead of <red>actual</red> <green>expected</green> (with <color>...</color> my attempt at showing the expected terminal output color), it displays `actual

The documentation for .above states:

The aliases .gt and .greaterThan can be used interchangeably with .above.

However, for .least:

The alias .gte can be used interchangeably with .least.

To my mind, there should be a .greaterThanOrEqual alias for .least in addition to

Hi,

I think I may have stumbled upon a bug.

With the value to set 'Cart' it shows 'Gear' in the drawer, this happens consistently throughout all other values
<img width="411" alt="image" src="https://user-images.githubusercontent.com/20213078/4796

This is meant as a discussion to follow up on #411. For those interested in getting more involved with goss, I am interested in the following:

1. Now that there is a CONTRIBUTING.md, issue/pr templates,

I couldn't find this in the documentation or the FAQ: Is it possible to obtain the current test case's name from within that testcase's code? I mean, it should be, but how do we do it? That should be either in the FAQ or in some other relevant documentation file, IMHO.

It would be nice to start building Pester on PowerShell 7 as well to see if it is compatible and keep it that way. To achieve that we need to research on which build servers v7 is already available. Right now we are building on TravisCI (Linux and MacOS), on AppVeyor (PowerShell 4+) and AzureDevOps (PowerShell 2&3).

Not sure if the build task needs to run on all three platforms, but it would be

Detailed Description

Update os_env documentation to state where variables should be set for controls using the os_env resource.

Context

Why is thi

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

Description

When comparing two identical dictionaries which use an object as the key, .Should().BeEquivalentTo() fails.

If I override .Equals() then it succeeds, which feels like it goes against the principle of equivalence expectations.

Whilst this may be my misunderstanding of the expectation, the docs don't seem to call this limitation out, so perhaps worth documenting if deemed

How can I mock a url that is used to download a file?
Is it possible to set a file into the body of register_uri?

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?

Hello!,

Just started working with this package and have to say is great!.

Was playing with the Supervisor class and would love to have an option specify the path where supervisorctl resides as well to be able to define where the configuration may reside.

There are some scenarios where the

I'd like to simplify Dependency Injection of Modules that fallback on each other, For instance, the Entity Framework is replaced by the [In Memory Fakes](https://github.com/ivanpaulovich/clean-architecture-manga/blob/master/src/WebApi/DependencyInjection/InMe

Pretty much as the title says - doesn't look like it's supported:

https://github.com/http4k/http4k/blob/59c9814cae8203857e30138501e979366f797817/http4k-testing-webdriver/src/main/kotlin/org/http4k/webdriver/JSoupWebElement.kt#L83

I'm taking a look and seeing if I can put together a PR

fast-check is a very nice library. It would be even better if we could use it with Facebook's ReasonML instead of Typescript!

It might be possible to use https://github.com/rrdelaney/ReasonablyTyped to make the conversion easier.

Describe the feature you'd like:

Jest-Extended has an assertion named the same as jest-extended's one:

-> https://github.com/jest-community/jest-extended#tobeempty
-> https://github.com/testing-library/jest-dom#tobeempty

When both libs are used in the same project, in my case the version of jest-extended overwrites the one from jest-dom. But this might vary depending on the order use

It would be great to have an introduction for each topic so I can understand why that topic is relevant e why I should spend time studying it.