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:

Description
Similarly to how Catch2 reads the BAZEL_TEST and XML_OUTPUT_FILE environment variables to support JUnit XML for Bazel, it should configure sharding based on the TEST_TOTAL_SHARDS and TEST_SHARD_INDEX environment variables, and indicate support for sharding by touching the file named in the

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.

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

Checklist

• Feature request has a meaningful title
• I have searched the existing issues. See all issues
• I have tested using the latest version of Pester. See Installation and update guide.

Summary of the feature request

Hi,

we are internally using Gitlab

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

Most of NUnit's numeric-related work (comparisons, differences, equality) is exposed via constraints or the classic assertion model, but the work itself is done by a helper class: Numerics.

This helper class has public visibility, which means API changes to it require extra caution to ensure we do