-
Updated
Sep 22, 2021 - JavaScript
contract-testing
Here are 143 public repositories matching this topic...
-
Updated
Sep 26, 2021 - Java
As part of the process of making the Pact docs more user friendly, we'd like to start writing feature documentation once, and providing code examples for each of the languages, rather than everyone having to write the same docs over and over again in each language.
The documentation for the consumer version selectors can be our first opportunity to give this approach a try. I have written the beh
-
Updated
Sep 21, 2021 - Elixir
Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:
{ "deployedOrReleased": true }
{ "deployed": true }
{ "released": true }
{ "environment": "<env name>" }
{ "consumer": "<name>" } // this may already be supported, please add it if not
These keys can be used in various combinations ( eg. `{ "envir
-
Updated
Aug 2, 2021 - TypeScript
-
Updated
Sep 27, 2021 - TypeScript
-
Updated
Sep 26, 2021 - Java
Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:
{ "deployedOrReleased": true }
{ "deployed": true }
{ "released": true }
{ "environment": "<env name>" }
{ "consumer": "<name>" } // this may already be supported, please add it if not
These keys can be used in various combinations ( eg. `{ "envir
-
Updated
Sep 20, 2021 - Java
-
Updated
Sep 6, 2021 - Swift
Describe the bug
Most expect methods print the request and response when the assertion fails.
However, the custom expect handler does not show these objects.
To Reproduce
Steps to reproduce the behavior:
const spec = pactum.spec();
spec.get(url);
await spec.toss();
await spec.response().to.have._((ctx) => {
assert.fail('error');
});
*Expected behavior
-
Updated
Nov 28, 2019 - Java
-
Updated
Oct 27, 2020 - Kotlin
-
Updated
May 14, 2021 - Crystal
-
Updated
Apr 10, 2018 - TypeScript
Description
When the file passed to the stub does not exist, the stub neither displays an error nor exits.
Steps to reproduce
- Run the command qontract stub nonexistent.qontract
- Qontract runs, but prints nothing, nor does it exit.
Expected behavior
If any of the files or directories provided do not exist, Qontract should highlight this, but it should not die if there is
-
Updated
Sep 23, 2021 - Java
-
Updated
Feb 19, 2019 - JavaScript
-
Updated
Feb 25, 2020 - Java
❕ Problem Statement
Provide resources to help new users become proficient in Pact and PactSwift
💬 Task Description
Create an end-to-end workshop based on the canonical pact one (https://github.com/pact-foundation/pact-workshop-js).
👩🔧 Technical Design Notes
Suggest using the JS provider as the "backend" for the workshop, to both reduce the effort required in this workshop and
-
Updated
Jan 3, 2018 - JavaScript
-
Updated
Apr 26, 2021 - Java
XPath Pathing
In order to test soap like api's (using XML for their body) a gandalf.pathing.Extractor that supports XPath is required.
-
Updated
Sep 21, 2021 - JavaScript
-
Updated
Sep 21, 2021 - TypeScript
Improve this page
Add a description, image, and links to the contract-testing topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the contract-testing topic, visit your repo's landing page and select "manage topics."
Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:
These keys can be used in various combinations ( eg. `{ "envir