Skip to content
#

contract-testing

Here are 101 public repositories matching this topic...

bethesque
bethesque commented Jun 26, 2020

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

joelrosario
joelrosario commented Sep 15, 2020

Description
When the file passed to the stub does not exist, the stub neither displays an error nor exits.

Steps to reproduce

  1. Run the command qontract stub nonexistent.qontract
  2. 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

PactSwift
surpher
surpher commented Oct 29, 2020

Problem Statement

GitHub Actions always run on a clean virtual machine. This means that each job re-builds the Rust binaries in ./Submodules/pact-reference/pact/target which takes a long time. Especially when building for multiple architectures (looking at you iOS device and simulator!). GitHub workflows already have a cache step but it seems that the built artefacts are not cached. Solvi

Improve this page

Add a description, image, and links to the contract-testing topic page so that developers can more easily learn about it.

Curate this topic

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."

Learn more

You can’t perform that action at this time.