pact-foundation / pact-foundation/pact-ruby
Verify Pact-Ruby against pact-compatibility-suite
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2.2k
- Forks
- 218
- Avg merge
- 1h 34m
- Merged PRs (30d)
- 1
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)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- ruby, rust
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100