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

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

Add a list of all current javascript pact repos for developers to documentation somewhere. This would help new contributors get up to speed with the landscape of pact-js.

If you use the jar with dependencies, the spring boot version needs to match (usually you get errors if the version is too apart of each other). We should document that

TravisCI (org) is dropping support for OSS builds at the end of this month, meaning they must be transferred to travis-ci.com, which uses a credit system. Builds may fail (and already are) if the number of credits is exhausted within th emonth.

We are recommending switching to GH Actions, but the choice of CI provider is up to the project maintainer.

See also:

• https://mailchi.mp/3d439ee

Feature request

Is your feature request related to a problem? Please describe

The analysis.py script provides just one confidence interval: 95%. While that is related to the 2-sigma interval of normal distribution, so in theory allows for easy estimation of bigger confidence intervals (like 3, 4, 5-sigma), it assumes a normal distribution, which the differences don't follow, and may be