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.

Currently the docs dont tell you how to execute runtimeassaults. Theyre only get executed either by a scheduled cron expression or by executing a POST REST call to /actuator/chaosmonkey/assaults/runtime/attack

Software versions

• OS: linux
• Consumer Pact library: Pact go v1.5.3
• Provider Pact library: Pact go v1.5.3
• Golang Version: 1.15

Expected behaviour

The pact go library should allow to exactly match multiple occurrences of the same query parameter as it is supported within pact files and by libraries for other platforms as shown e.g. [here](https://docs.pact.io

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