Verify Pact-Ruby against pact-compatibility-suite

Open
#321 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby, rust
Domain
testing

Research direction

Start by reviewing the pact-compatibility-suite and the existing compatibility-suite examples in pact-rust, pact-jvm, pact-php, pact-python, and pact-ruby-ffi. Determine how the suite should be integrated with pact-ruby and run it against the current implementation. Done means pact-ruby has compatibility-suite coverage that can be rerun as pact v3, pact v4, and pact_ffi support evolves.

Written by the indexing model from the issue text.

Description

A Set of BDD style tests to check compatibility between Pact implementations has been created in the pact-compatibility-suite

In order to validate pact-ruby and it's adherence to the pact-specification, it would be great to implement the suite against the current pact-ruby as it stands, and future iterations as we move towards pact v3 spec compliance, and pact v4 spec compliance.

It would also be useful in validating behaviour pre and post migrating to the pact_ffi shared core built in rust.

Current examples

Related Issue(s)

Dominant language
Ruby
Stars
2.2k
Forks
220
Avg merge
5h 22m
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pact-foundation/pact-ruby

All issues in pact-foundation/pact-ruby

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.