bethskurrie
2018-05-21 03:27
/github subscribe pact-foundation/pact-support issues pulls releases statuses
nabrosimova
2018-07-31 20:40
Hi, I am trying to figure out how to do file_upload in ruby. Both provider and consumer are written in ruby. I did see pact-jvm examples with scala. But really need examples of how i can set it up in ruby
nabrosimova
2018-07-31 22:14
hi, i have a file upload call that in place of body has payload something like this `multipart: true,
file: file,
name: name`
nabrosimova
2018-07-31 22:16
the whole problem is.. it first doesnt see the payload. second of all i need to pass in file for the call and i dont know how to do that in ruby. i saw this https://github.com/DiUS/pact-jvm/commit/3f9a03ef66d97f411d2b959527a693f2c2cd188a but couldnt find an example of how to use it in ruby
nabrosimova
2018-07-31 22:22
when i check how the call actually looks like it looks something like "headers": {
"Content-Type": "multipart/form-data; boundary=----WebKitFormBoundary1bvPHrYmtx0UNv2e"
},
"body": "------WebKitFormBoundary1bvPHrYmtx0UNv2e\r\nContent-Disposition: form-data; name=\"file\"; filename=\"476.csv\"\r\nContent-Type: text/csv\r\n\r\ndata\r\n------WebKitFormBoundary1bvPHrYmtx0UNv2e--\r\n"
}
nabrosimova
2018-07-31 22:24
but RubyFormBoundaryPs4ifEBhAkIzfpNe is autogenerated and is always different... so i cannot just make it up
nabrosimova
2018-07-31 23:24
@bethskurrie is there any way i can test upload file without having to worry about rubyForm boundary changing
bethskurrie
2018-08-01 00:11
@uglyog I'm sure I've seen an example for pact-jvm with this. How did you get around it?
bethskurrie
2018-08-01 00:14
It wouldn't be too hard to write a diff for multipart form, but I want to keep the functionality as similar as possible.
bethskurrie
2018-08-01 00:16
Oh, right, just read the groovy link. I'll see if I can work it out when I'm at my computer.
uglyog
2018-08-01 00:20
nabrosimova
2018-08-01 17:23
body: Pact.like('------RubyFormBoundary2AQPyCUtPGtlPQKQ\r\nContent-Disposition: form-data; name=\"file\"\r\n\r\n\r\n------RubyFormBoundary2AQPyCUtPGtlPQKQ\r\nContent-Disposition: form-data; name=\"name\"\r\n\r\nFish in a Pond!\r\n------RubyFormBoundary2AQPyCUtPGtlPQKQ--\r\n')
nabrosimova
2018-08-01 17:37
"headers": {
"Content-Type": "multipart/form-data; boundary=----RubyFormBoundary2AQPyCUtPGtlPQKQ",
"Content-Length": "235",
"Accept": "*/*",
"Accept-Encoding": "gzip, deflate",
"User-Agent": "rest-client/2.0.2 (linux-gnu x86_64) ruby/2.4.4p296",
"Authorization": "pact_notorious_secret",
"HOST": "localhost:2345"
},
"body": "------RubyFormBoundary2AQPyCUtPGtlPQKQ\\r\\nContent-Disposition: form-data; name=\\\"file\\\"\\r\\n\\r\\n\\r\\n------RubyFormBoundary2AQPyCUtPGtlPQKQ\\r\\nContent-Disposition: form-data; name=\\\"name\\\"\\r\\n\\r\\nFish in a Pond!\\r\\n------RubyFormBoundary2AQPyCUtPGtlPQKQ--\\r\\n",
bethskurrie
2018-08-02 07:12
@nabrosimova you won't be able to do it until I write a new feature for pact ruby.
nabrosimova
2018-08-02 17:19
i did raise an issue but also i got it to almost work.. though it gives me `Encoding::UndefinedConversionError - "\x9F" from ASCII-8BIT to UTF-8` error
nabrosimova
2018-08-02 17:34
also, i can try to make pact with empty mov file but it fails on returning me the wrong response, by saying that transcoding process failed
nabrosimova
2018-08-02 17:45
Also, i am just an intern and my time ends soon, so I was wondering if that feature will be added, how long it will take?
bethskurrie
2018-08-03 09:18
It shouldn't take too long, but my time is limited. I'll see if I can get it done this week. Is that fast enough?
bethskurrie
2018-08-09 21:54
Do you mean, can you set up multiple interactions on the mock service at the same time? Yes.
bethskurrie
2018-08-09 21:54
Do you mean, can you chain together a group of requests to replay together? No.
bethskurrie
2018-08-09 21:55
Do you mean, can you mock multiple requests to different providers at the same time? Yes.
lkingsley
2018-08-09 22:12
More specifically I want to upload a file but first need to send a post request telling the server about the size and file type so it can be ready for it. It will then return a unique key, a new url for me to send another post request to but Im unsure how to set up the test if I do not know the url or key value until the first test has run. Does this sound at all possible? @bethskurrie
bethskurrie
2018-08-09 22:14
Use provider states to set up the correct data so that when you do the file upload, it matches the file.
bethskurrie
2018-08-09 22:15
There is a section on provider states in http://docs.pact.io if you're unfamiliar with them.
lkingsley
2018-08-10 16:21
Yea the only issue is when setting this up in a provider state it doesn?t give me the necessary information to make the request.
nabrosimova
2018-08-24 18:04
hey, i am running into weird error trying to implement verification in jenkins...
tom397
2018-09-26 13:50
Hello! Quick question! Is there a way to consume `params` from a provider state listed in a pactfile while implementing the `provider_state` on the provider?
_Example:_
Pact file:
```
"interactions": [
{
"description": "/api/v3/animals/:id",
"providerStates": [
{
"name": "an animal named Spot",
"params": {
"name": "Spot"
}
}
],
```
Provider state:
```
provider_state "an animal named Spot", params do
Dog.new(params.name)
end
```
Apologies if any of this is unclear, I'm happy to clarify just let me know! Thanks!!
bethskurrie
2018-10-01 09:22
Not yet @tom397 because I haven't yet implemented v3 pact specification in Ruby.
bethskurrie
2018-10-01 09:23
If you're using param, your provider is v3, and ruby only implements v2 so far (just because I haven't had time to do it)
bethskurrie
2018-10-03 23:21
@tom397 I've added provider state params support to the ruby impl.
```
set_up do | params | do
Alligator.new(name: params.fetch('name')).save!
end
```
bethskurrie
2018-10-03 23:23
if you're verifying v3 pacts, you can now access the provider state params in the set up and tear down blocks. You'll need version 1.36.0 of the pact gem.
```
set_up do | params | do
Alligator.new(name: params.fetch('name')).save!
end
```
marco.dellolio
2018-11-05 19:40
@bethskurrie I found an old discussion https://github.com/pact-foundation/pact-ruby/issues/49, do we have any system in place generate a valid JWT:Token in the `Provider::Verify`?
I have a `before_action :ensure_signed_jwt!` in my controller with a JWT valid for 10 minutes.
marco.dellolio
2018-11-06 02:15
As a general question, how the provider proxy relates to the the actual provider?
bethskurrie
2018-11-06 02:26
Not yet, but you can use middleware to modify the request with a live token. Which language are you using @marco.dellolio?
bethskurrie
2018-11-06 02:27
Do you mean in the ruby? It's for performing verifications against a running provider, rather than a rack app.
marco.dellolio
2018-11-06 02:28
I was looking into the https://github.com/pact-foundation/pact-provider-verifier is it a standalone application? And more specifically how it relates to the real provider? I?m not quite sure about the workflow
bethskurrie
2018-11-06 02:28
With native ruby, make some rack middleware and wrap it around your app when you configure it on the provider side.
bethskurrie
2018-11-06 02:29
You'll find an example in the "verifying pacts" documentation on the Pact ruby wiki.
bethskurrie
2018-11-06 02:29
With the other languages, it's the same middleware, but you'll configure it differently. Look at the docs for the pact provider verifier cli.
bethskurrie
2018-11-06 02:31
Pact provider verifier is for use against running apps of any language. It's packaged as a cli, but if you're using ruby, you'd just use the native gem. It's much more elegant.
marco.dellolio
2018-11-06 02:32
Yeah I?ve been reading those today. If I understand correctly the flow is the following. I put my pact files in the proxy provider (locally or broker), the proxy provider is a standalone app (a docker container e.g) which hits the real provider end-point and verify the pact file?
bethskurrie
2018-11-06 02:36
The broker does not proxy, and it does not run any tests. It is a repository for pacts and verification results.
bethskurrie
2018-11-06 02:37
The pact is verified against a rack app, if you're using native ruby, or a running application if not.
bethskurrie
2018-11-06 02:39
The pact can be exchanged via a broker, or if you're just playing around, you can just point to the local file on your file system.
bethskurrie
2018-11-06 02:41
The pact provider verifier takes the pact, and behaves like a mock consumer, replaying the request against the provider, and checking the response matches the expected response.
marco.dellolio
2018-11-06 02:41
until this point it?s all clear. What I still not fully understand is : Where https://github.com/pact-foundation/pact-provider-proxy/ this should live? In my provider or it is an independent application?
bethskurrie
2018-11-06 02:42
But if you're verifying a ruby rack app, you just need the pact gem, nothing else.
marco.dellolio
2018-11-06 02:43
In a ruby app are you actually suggesting this option?
```
class ProxyApp
def initialize real_app
@real_app = real_app
end
def call env
@real_app.call(env.merge('HTTP_AUTHORIZATION' => '12345'))
end
end
Pact.service_provider "Some Provider" do
app do
ProxyApp.new(RealApp)
end
honours_pact_with "Some Consumer" do
#...
end
end
```
marco.dellolio
2018-11-06 04:23
I?m making my way through it! The problem is the new application doesn?t recognize my models. When I run this in the provider state
```
set_up do
raw_email = File.read("spec/fixtures/emails/email.eml")
RawEmail.create( tenant_id: 1,
message_id: "CAAWRWJD5Dvw64zAzYurfsfDB22UGakRBd=P0ZCmjV7_UZPuxDg@mail.gmail.com",
raw_email: raw_email
)
end
```
it errors out `NameError:uninitialized constant RawEmail`
bethskurrie
2018-11-06 04:29
What is the main entry point of your app if you were running it? The thing that requires all the other files? You'll need to require that in the pact helper.
marco.dellolio
2018-11-06 04:31
I?m already requiring `'config/application'` which already requires `require "rails/all"` and `config.autoload_paths += [Rails.root.join("app")]` which includes the models
bethskurrie
2018-11-06 04:32
I'm afraid I can't help you without seeing your code then. It sounds like it should work.
uglyog
2018-11-07 21:37
Start with https://github.com/pact-foundation/pact-specification/tree/version-3#allow-arrays-of-matchers-to-be-defined-against-a-matcher-path which describes the changes from V2
uglyog
2018-11-07 21:38
Then have a look at the existing implementations in Pact-JVM and in the Rust implementation
marco.dellolio
2018-11-08 14:01
Hey all, I?m having hard time parsing my provider verifier query params in a rails app
marco.dellolio
2018-11-08 14:01
this is how the request looks like in the controller
```
request
=> #<ActionDispatch::Request:0x00007fbb11d3cb50
@env=
{"rack.version"=>[1, 3],
"rack.input"=>#<StringIO:0x00007fbb133b93d8>,
"rack.errors"=>#<StringIO:0x00007fbb133b9568>,
"rack.multithread"=>true,
"rack.multiprocess"=>true,
"rack.run_once"=>false,
"REQUEST_METHOD"=>"GET",
"SERVER_NAME"=>"http://example.org",
"SERVER_PORT"=>"80",
"QUERY_STRING"=>"%7B%22tenant_id%22%3A1%2C%22message_id%22%3A%22CAAWRWJD5Dvw64zAzYurfsfDB22UGakRBd=P0ZCmjV7_UZPuxDg%40mail.gmail.com%22%7D",
```
marco.dellolio
2018-11-08 14:02
this is how params get parsed `<ActionController::Parameters {"{\"tenant_id\":1,\"message_id\":\"CAAWRWJD5Dvw64zAzYurfsfDB22UGakRBd"=>"\"}", "format"=>"json",`
marco.dellolio
2018-11-08 17:59
So the problem is PACT is building the query string out
```
"body": {
"tenant_id": 1,
"message_id": ""
}
```
marco.dellolio
2018-11-08 18:00
parsing the object and not the key values resulting in this
```
"%7B%22tenant_id%22%3A1%2C%22message_id%22%3A%22CAAWRWJD5Dvw64zAzYurfsfDB22UGakRBd=P0ZCmjV7_UZPuxDg%40mail.gmail.com%22%7D"
```
instead of
```
tenant_id=1&message_id=22CAAWRWJD5Dvw64zAzYurfsfDB22UGakRBd=http://P0ZCmjV7_UZPuxDg%40mail.gmail.com
```
simon.nizov
2018-11-26 11:58
Hey, I just stumbled upon the following scenario:
I started implementing pact on an existing project that currently uses VCR.
I was getting errors from VCR about unrecorded cassettes for requests that pact was trying to make to the mock service. Obviously I don?t want to record those. The solution was to add the following configuration to VCR to ignore requests made to the mock service:
```
VCR.configure do |c|
config.ignore_request do |request|
URI(request.uri).port == 1234 # Ignore requests to Pact mock service
end
end
```
I would like to add this little piece of information to the docs somewhere, to save some research time for future users. Where would be the best place for this? Is there a ?gotchas? section I can put this under?
rahul.neotech
2018-11-29 18:50
Hi :wave: I?m using pact-ruby to write a contract test for our consumer and provider service. Our services communicate via protos and the protos are encoded when sent over the wire.
When the protos are encoded, they contain certain characters that are not JSON serializable (pact throws; an error I received looks like this - "\xC8" from ASCII-8BIT to UTF-8).
I was able to overcome this by Base64 encoding the request and response - in the pact gem - before it is JSON serialized in the consumer - and then Base64 decoding it in the provider before it is used for verification.
I?m wondering if there?s a better solution for what I?m doing. Can someone help?
simon.nizov
2019-01-06 14:42
Hey guys, quick question, should I push the automatically created pact json file to the git repository?
simon.nizov
2019-03-03 09:39
While debugging my unit test on the consumer, is there a way to list all the interactions currently registered on the mock service?
krzysztof.stepniak
2019-03-07 14:37
Hey guys, are you going to resolve problem with encoding
https://stackoverflow.com/questions/51604866/pact-verifier-is-failing-with-encodingundefinedconversionerror-xe2-from-as https://github.com/pact-foundation/pact-python/issues/97 and https://github.com/pact-foundation/pact-ruby-standalone/issues/27
I have the same problem with encoding on pact js when im trying to post request to my mock. Returned ruby error stack with ` Error ocurred in mock service: Encoding::UndefinedConversionError - "\x89" from ASCII-8BIT to UTF-8`
000sps97
2019-04-03 12:31
Hey, I am currently working on a project that requires a lot of key values to be compared in response where response is a hash, i want to use something like `Pact.like(responseHash)` instead of `Pact.like(key1: "value1", Key2: "value2" ,...)`, but the finally created json `"matchingRules": {
"$.body": {
"match": "type"
}
}`
simon.nizov
2019-04-03 12:43
@000sps97 both snippets of code you mentioned will work the same.
The resulting matching rule will match each key value pair in the `responseHash` you provide as you want it to
000sps97
2019-04-03 12:53
@simon.nizov does ` matchingRules": {
"$.body": {
"match": "type"
}
} ` match to every key value in the response ?
shouldn't it be something like
` matchingRules": {
"$.body.key1":{"match":"type"}
"$.body.key2":{"match":"type"}
}
simon.nizov
2019-04-03 14:05
@000sps97 yup. You can test it easily by verifying the pact against your provider
bheemreddy181
2019-04-05 20:15
Is there a way i can use TEST_DB on provider side than using Development DB ?
bheemreddy181
2019-04-07 12:16
If you run rspec on test dB you can just do ?require rails_spec.rb? which fixes this
jon.pascoe
2019-04-09 11:20
Hello! I've looked online and can't find anybody mentioning this use-case, so was wondering if anybody here had any suggestions.
I'm building a collection of rails apps, which each have an internal API provided by a Rails Engine (gem) that I'm building. That API is both a consumer and provider, and is tested using Pact. I've got the consumer tests working fine, and verified on the provider (another rails app). However, I'm struggling to get the provider verification working in the Rails Engine.
jon.pascoe
2019-04-09 11:20
because it's not a full Rails app, there is no `http://config.ru` in the root of the project
jon.pascoe
2019-04-09 11:21
I get this when trying to verify the pacts:
```Failure/Error: raise "Could not find http://config.ru file at #{Pact.configuration.config_ru_path} Please configure the service provider app or create a http://config.ru file in the root directory of the project. See https://github.com/pact-foundation/pact-ruby/wiki/Verifying-pacts for more information."
```
jon.pascoe
2019-04-09 11:21
I tried setting up the verify task in the Rakefile for the dummy app, but that wasn't happy either
bethskurrie
2019-04-09 11:22
I don't know what a rails engine is, but if there is a rack interface, you can just set the app { RailsEngine.new } in the top level of the provider config.
jon.pascoe
2019-04-09 11:23
Rails Engine is basically a mini rails app that you can mount inside another rails app
bethskurrie
2019-04-09 11:40
BTW, @jon.pascoe I thought I'd fixed the interpolation in that error message you got. What version of the pact gem are you using?
jon.pascoe
2019-04-09 12:49
On the topic of `webmock` ? I have an issue with it interfering with uploading pact verification results ? and I can?t see where to hook in the command to disable webmock
jon.pascoe
2019-04-09 12:49
```WebMock::NetConnectNotAllowedError:
Real HTTP connections are disabled. Unregistered request: GET https://site.pact.dius.com.au/pacts/provider/.../diff/previous-distinct with headers {'Accept'=>'*/*', 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', 'User-Agent'=>'Ruby'}```
jon.pascoe
2019-04-09 12:51
this is using the `publish_verification_results` setting in the `Pact.service_provider` declaration to trigger uploading the results
jon.pascoe
2019-04-09 13:32
Instead I added this to my `rails_helper.rb`:
```WebMock.disable_net_connect!(allow_localhost: true, allow: "http://site.pact.dius.com.au")```
qatrera
2019-04-09 14:13
Well I use and old version of `Typhoeus` instead of `WebMock` so maybe what works for me it's not transferable to you. And we also have the pact broker hosted in house
bheemreddy181
2019-04-18 20:32
@bethskurrie @matt.fellows https://github.com/pact-foundation/pact-ruby-standalone this is to replace all the gems and use one for everything both on provider and consumer side
bheemreddy181
2019-04-20 03:59
Ruby folks here Do you people use Semantic versioning to version pacts or pass commit hash as input for pacts ?
matt.fellows
2019-04-20 04:01
have a read of https://github.com/pact-foundation/pact_broker/wiki/Pacticipant-version-numbers if you haven?t already
matt.fellows
2019-04-20 04:03
This might also be of use: https://docs.pact.io/getting_started/versioning_in_the_pact_broker
bheemreddy181
2019-04-20 04:24
I got this but the problem comes here is ho do we do it through the code like our semantic versioning only sits in the releases
bethskurrie
2019-04-20 05:57
If you know or can work out your sha at release time, I'd recommend using a git sha. If you use your semantic version, you'll tend to have multiple commits, and hence, builds and pacts per minor or patch version, and that means you're overwriting the previous pact version with that semantic version. You can do it, but things tend to work better when your data is immutable (ie one pact version per consumer version number).
bethskurrie
2019-04-20 05:58
You eliminate race conditions, and you get a more fine grained "matrix" of test results.
matt.fellows
2019-04-20 06:38
@bheemreddy181 when you say "sits in the release" do you mean you don't version things until you release? What's the process you use to version now?
matt.fellows
2019-04-20 12:46
You don?t have to give your published app version the exact tag you push to the broker (although it probably is more convenient).
bheemreddy181
2019-04-20 23:51
@bethskurrie Quick Question whenever i use the broker - do i need to give pact_uri in both these places ? https://github.com/pact-foundation/pact-ruby-e2e-example/blob/c54dd9da813c58261b9a83e6249b1d62920fb72b/provider/spec/pact_helper.rb#L11 , https://github.com/pact-foundation/pact-ruby-e2e-example/blob/c54dd9da813c58261b9a83e6249b1d62920fb72b/provider/Rakefile#L27 ?
bethskurrie
2019-04-21 00:23
You can add extra verification tasks if you want to do custom verifications (eg verify a pact on your local machine)
bethskurrie
2019-04-21 00:24
You should give the pact helper configuration the broker details though, and it will fetch all the pacts from the broker. You don't have to use the specific urls.
bheemreddy181
2019-04-22 14:57
@bethskurrie Here is another quick question - On this verification task, the version belongs to Consumer or Provider ? https://github.com/pact-foundation/pact-ruby-e2e-example/blob/c54dd9da813c58261b9a83e6249b1d62920fb72b/provider/Rakefile#L27
bethskurrie
2019-04-22 23:56
@bheemreddy181 this is the recommended configuration https://github.com/pact-foundation/pact-ruby/wiki/Verifying-pacts#fetching-pacts-from-a-pact-broker
bheemreddy181
2019-04-23 01:01
when you say consumer how will the provider know which version he has to verify with @matt.fellows
bethskurrie
2019-04-23 01:02
you dont' fix it to a particular version. But, it is recommended that you fix it to a particular tag. eg "the latest dev pact" or "the latest prod pact"
matt.fellows
2019-04-23 01:02
Beth, is there a way in Ruby to just point at the broker with the provider details and get all of the consumers for a given provider?
bethskurrie
2019-04-23 01:02
the docs are in the link I sent above, or you can use `pacts/provider/Bar/consumer/Foo/latest/TAG_NAME`
bheemreddy181
2019-04-23 01:04
what does this mean ? ``` But, it is recommended that you fix it to a particular tag. eg "the latest dev pact" or "the latest prod pact"```
matt.fellows
2019-04-23 01:04
@bheemreddy181 I?d 100% use the https://github.com/pact-foundation/pact-ruby/wiki/Verifying-pacts#fetching-pacts-from-a-pact-broker strategy. It?s by far the most straightforward way for anything but the most simplest pact setups
bethskurrie
2019-04-23 01:05
it doesn't care which version it is. it's just whatever the latest version of the pact is.
bethskurrie
2019-04-23 01:09
```
honours_pacts_from_pact_broker do
pact_broker_base_url 'http://...'
end
```
bethskurrie
2019-04-23 01:12
Please just read this page top to bottom, and then ask any questions you have.
joelbyler
2019-04-25 19:45
Hello there! I?m wondering if anyone?s using the standalone mock server as explained here? # standalone true
matt.fellows
2019-04-26 07:59
This gets used a lot: https://github.com/pact-foundation/pact-ruby-standalone/releases but might not be what you?re after
bheemreddy181
2019-05-04 00:56
Here are few more questions :
1. Parma type validations on the API - does required or optional param should happen on the controller of the API - As we are mocking everything underlying logic of the controller what if if you param validations happens inside the some where with in the logic ?
bheemreddy181
2019-05-05 01:22
@bethskurrie ^ similar to rspec https://relishapp.com/rspec/rspec-core/docs/helper-methods/let-and-let
bheemreddy181
2019-05-05 01:27
```Q: I felt like PACT does give a provision of breaking contracts if none of your consumers is using few fields from your API or not bothered if the type is changed? yet all? Is that true? which might also lead to having just one version of the API unless needed?
A: Exactly true, consumer contracts remove the need to version an API. API versioning is a "workaround" because you don't want to break backwards compatibility, and you don't know who is using your API. It's the best technique for a public API. When you know all your consumers, and you know exactly what they're using, you know the impact of change, and hence, you should be able to avoid versioning the API.
Q: Can I do a functional test of my provider using PACT?
A: You can, but you are not supposed to do that . Give a read from here: https://docs.pact.io/best_practices/consumer/contract_tests_not_functional_tests
Q: Do I need to write contracts tests for the complete response of an API?
A: No, That's a bad way of writing tests - From Consumer perspective you have to write tests for the fields only you worry about.
Q: Why can't I generate a schema from Provider Side and use that as a reference for all future changes?
A: Yes you can do that but when your API is public like PUBLIC API and you don't know how your consumers are using your API, else you are tightly coupling your changes to all the fields which are not generally required. Again, you are duplicating the functional tests with your contract tests from the provider side. which should always be consumer driven.
Q: Can I generate contract file from Swagger?
A: Give a read: https://docs.pact.io/faq#can-i-generate-my-pact-file-from-something-like-swagger
Q: Oh Wow, Who will write the Contracts test - which will generate the contract files?
A: Its the consumer duty to write the tests pretty much to specific to the fields what consumer bothers rather than writing for complete body validations. on the provider side just that you have to maintain the states of mocks - like Skip authentication so on.
Q: Oh This looks like VCR recording, how is it different from that?
A: Give a read: https://docs.pact.io/faq/convinceme#but-i-already-have-a-local-mock-server-e-g-vcr-mockserver
Q: who will own it, like who will own the contract files?
A: Consumer again, each provider can have n - number of consumers and each one might use a different one. So it's the consumer duty from what he uses to write the contract from a consumer perspective.
Q: What is PACT_BROKER? Is this a hosted service which should live somewhere and someone should own it?
A: Yes this is a hosted service and should be owned by someone. Currently, PACT developers provide a free hosted version of pact_borker with security attached if we want we use that. Else we can have a dedicated host where this service can live, they have a docker image which we can use to host this on our side and do upgrades. Sample free host here: https://pactflow.io/register/
Q: where will it run?
A: Our Aim is to run this each Pull-request on Travis/ANY CI TOOL.
Q: when will it run?
A: On Each Pull Request
Q: Do we have to write some code on the provider side?
A: StuB the internal functionality of the provider, because of FUNCTIONAL TESTING is the job of the provider to test than tested using consumer driver contracts. Make sure, if you stub, that you don't stub the code that actually parses the request and pulls the expected data out because otherwise, the consumer could be sending absolute rubbish, and the pact:verify won't fail because that code won't get executed ```
bheemreddy181
2019-05-05 01:28
@bethskurrie @matt.fellows are you people inline with the above questions and relative answers , correct me if i am wrong.
bethskurrie
2019-05-05 02:26
Looks good to me. I would say a flat "no" to "can I use pact for functional tests" though.
bheemreddy181
2019-05-05 03:13
@luchillo17 little notes what I prepared would help you understand more ^
qatrera
2019-05-06 09:58
in the first diagram I would say the deploy arrow in the provider is not needed right? I also don't get the Skip section in the second diagram
qatrera
2019-05-06 10:00
Maybe it's worthy to extend the FAQ (https://docs.pact.io/faq) with these Q&As. I found some of them really valid and eye-opening for Pact newbies :slightly_smiling_face:
qatrera
2019-05-06 10:01
Really nice diagram btw :slightly_smiling_face: I still need to find time to dig into the webhooks part to finally integrate the first contract tests in our company :slightly_smiling_face:
bheemreddy181
2019-05-06 20:01
here is a question : i have a rake task in my rake file as this : ```Pact::VerificationTask.new(:portfolio_using_remote_broker) do | pact |
pact.uri "#{REMOTE_PACT_BROKER_BASE_URL}/pacts/provider/PGS/consumer/Portfolio/latest", :pact_helper => 'spec/service_consumers/pact_helper.rb'
end```
bheemreddy181
2019-05-06 20:02
whereas in my pact helper : ```require_relative './provider_states'
Pact.configuration.reports_dir = "./provider/reports"
Pact.configure do | config |
config.diff_formatter = :embedded
end
Pact.service_provider "PGS" do
app_version '1.0.0'
publish_verification_results !!ENV['PUBLISH_VERIFICATIONS_RESULTS']
honours_pact_with 'Portfolio' do
# This example points to a local file, however, on a real project with a continuous
# integration box, you would use a [Pact Broker](https://github.com/bethesque/pact_broker) or publish your pacts as artifacts,
# and point the pact_uri to the pact published by the last successful build.
pact_uri 'https://remote:endpoint', {username: '...', password: '...'}
end
end```
bheemreddy181
2019-05-06 20:03
whenever i do run rake task ``` be rake pact:verify:portfolio_using_remote_broker
```
bheemreddy181
2019-05-06 20:09
it does work when i do append the pact_uri with /pacts/provider/PGS/consumer/Portfolio/latest on the pact help and just run the pact:verify task but that doesn't publish the results
bheemreddy181
2019-05-06 23:32
Skip section in the second diagram comes into picture when you publish the same contract every time
bethskurrie
2019-05-08 00:21
have you tried curling the URL and providing the basic auth username and password?
bethskurrie
2019-05-08 00:23
have you tried curling the URL and providing the basic auth username and password?
bheemreddy181
2019-05-08 00:26
that worked ```{"_links":{"self":{"href":"https://bheemreddy.pact.dius.com.au","title":"Index","templated":false},"pb:publish-pact":{"href":"https://bheemreddy.pact.dius.com.au/pacts/provider/{provider}/consumer/{consumer}/version/{consumerApplicationVersion}","title":"Publish a pact","templated":true},"pb:latest-pact-versions":{"href":"https://bheemreddy.pact.dius.com.au/pacts/latest","title":"Latest pact versions","templated":false},"pb:tagged-pact-versions":{"href":"https://bheemreddy.pact.dius.com.au/pacts/provider/{provider}/consumer/{consumer}/tag/{tag}","title":"All versions of a pact for a given consumer, provider and consumer version tag","templated":false},"pb:pacticipants":{"href":"https://bheemreddy.pact.dius.com.au/pacticipants","title":"Pacticipants","templated":false},"pb:latest-provider-pacts":{"href":"https://bheemreddy.pact.dius.com.au/pacts/provider/{provider}/latest","title":"Latest pacts by provider","templated":true},"pb:latest-provider-pacts-with-tag":{"href":"https://bheemreddy.pact.dius.com.au/pacts/provider/{provider}/latest/{tag}","title":"Latest pacts for provider with the specified tag","templated":true},"pb:provider-pacts-with-tag":{"href":"https://bheemreddy.pact.dius.com.au/pacts/provider/{provider}/tag/{tag}","title":"All pact versions for the provider with the specified consumer version tag","templated":true},"pb:provider-pacts":{"href":"https://bheemreddy.pact.dius.com.au/pacts/provider/{provider}","title":"All pact versions for the specified provider","templated":true},"pb:latest-version":{"href":"https://bheemreddy.pact.dius.com.au/pacticipants/{pacticipant}/latest-version","title":"Latest pacticipant version","templated":true},"pb:latest-tagged-version":{"href":"https://bheemreddy.pact.dius.com.au/pacticipants/{pacticipant}/latest-version/{tag}","title":"Latest pacticipant version with the specified tag","templated":true},"pb:webhooks":{"href":"https://bheemreddy.pact.dius.com.au/webhooks","title":"Webhooks","templated":false},"pb:integrations":{"href":"https://bheemreddy.pact.dius.com.au/integrations","title":"Integrations","templated":false},"beta:pending-provider-pacts":{"href":"https://bheemreddy.pact.dius.com.au/pacts/provider/{provider}/pending","title":"Pending pact versions for the specified provider","templated":true},"curies":[{"name":"pb","href":"https://bheemreddy.pact.dius.com.au/doc/{rel}?context=index","templated":true},{"name":"beta","href":"https://bheemreddy.pact.dius.com.au/doc/{rel}?context=index","templated":true}]}}```
bethskurrie
2019-05-08 00:26
you've either configured it incorrectly, or there's a bug in the ruby code.
bheemreddy181
2019-05-08 00:29
when i have my own rake task the credentails are shared from the pact helper ?
bheemreddy181
2019-05-08 00:30
```Pact::VerificationTask.new(:portfolio_using_remote_broker) do | pact |
pact.uri "#{REMOTE_PACT_BROKER_BASE_URL}/pacts/provider/PGS/consumer/Portfolio/latest", :pact_helper => 'spec/service_consumers/pact_helper.rb'
end```
bethskurrie
2019-05-08 00:30
the rake task is used when you want to override the default behaviour in the pact_helper.rb
bheemreddy181
2019-05-08 00:30
```require_relative './provider_states'
Pact.configuration.reports_dir = "./provider/reports"
Pact.configure do | config |
config.diff_formatter = :embedded
end
Pact.service_provider "PGS" do
app_version '1.0.0'
publish_verification_results !!ENV['PUBLISH_VERIFICATIONS_RESULTS']
honours_pact_with 'Portfolio' do
# This example points to a local file, however, on a real project with a continuous
# integration box, you would use a [Pact Broker](https://github.com/bethesque/pact_broker) or publish your pacts as artifacts,
# and point the pact_uri to the pact published by the last successful build.
pact_uri 'https://remote:endpoint', {username: '...', password: '...'}
end
end```
bethskurrie
2019-05-08 00:31
you'll need to give the task the credentials, because you're overriding where the pact comes from
bethskurrie
2019-05-08 00:31
`With basic auth, set the environment variables PACT_BROKER_USERNAME and PACT_BROKER_PASSWORD, or use the basic auth URL format, http://username:password@pactbroker.yourdomain/....
`
bheemreddy181
2019-05-08 00:34
So that I can add that to other rake task which I run as part of my CI build
bethskurrie
2019-05-08 00:35
when you run it locally, it's not set, so the results dont' get published
bethskurrie
2019-05-08 00:37
Is there something that needs improving in these docs, or did you just miss that bit?
bethskurrie
2019-05-08 00:43
I've updated that section - is it clearer? https://github.com/pact-foundation/pact-ruby/wiki/Verifying-pacts#publishing-verification-results-to-a-pact-broker
bheemreddy181
2019-05-08 00:53
One more thing when I say provider/consumer/latest does that verify all the pacts which say tags prod and Dev ?
bethskurrie
2019-05-08 07:05
@bheemreddy181 if you make a module that has helper method for creating or stubbing your data, you can include that module directly into the provider states code. I think it's something like `Pact.configuration.include YourHelperModule`
bethskurrie
2019-05-08 07:06
You want to push as much logic into the helper code, otherwise your provider state set up code will get very bloated
bethskurrie
2019-05-08 07:07
I personally like a "builder" pattern. Here's the provider state code for the pact between the Pact Broker and the Pact Broker Client (meta!) https://github.com/pact-foundation/pact_broker/blob/master/spec/service_consumers/provider_states_for_pact_broker_client.rb
bheemreddy181
2019-06-16 14:23
```...
parameters {
string(name: 'pactConsumerTags', defaultValue: 'master')
}
stage ('Build') {
...
sh "./mvnw clean verify ...
-Dpactbroker.tags=${params.pactConsumerTags}"
...
}
}```
bheemreddy181
2019-06-16 15:00
Does the consumer - triggered provider verification job should be different from provider driven verification should be different from each other ?
bheemreddy181
2019-06-17 00:45
I don?t see a way to set a default value in there do I need to write my own helpers for the same
bethskurrie
2019-06-17 00:48
I think what you're asking me to help you with is beyond the scope of what I can achieve over slack.
bethskurrie
2019-06-17 00:49
Ok, I can help you with usecases, but you seemed to be asking for ruby coding help.
bheemreddy181
2019-06-17 00:49
Why does provider need to same branch name as consumer when sends the branch names as a tag
bethskurrie
2019-06-17 00:50
some people like to make a matching branch name in the provider to implement the required features, but it's not mandatory.
bheemreddy181
2019-06-17 00:51
In that case too when the branch_name is considered I should fallback to master when not present
bheemreddy181
2019-06-17 00:53
And when consumertagname is present then I should fetch that else always master
bheemreddy181
2019-06-17 00:55
Consumer_tag_versions {Consumertagname || master , travis[?branch_name]}
bethskurrie
2019-06-17 00:55
if you're not using provider branches for feature development, you can ignore that part though.
bethskurrie
2019-06-17 00:59
```
consumer_version_tag = ENV['CONSUMER_VERSION_TAG'] || ENV['TRAVIS_BRANCH']
consumer_version_tags [{name: consumer_version_tag, fallback: 'master'}]
```
bethskurrie
2019-06-17 00:59
There. That will take the consumer tag name if it exists, or the travis branch, or fall back to master
bheemreddy181
2019-06-17 01:00
:clap::skin-tone-3::clap::skin-tone-3::clap::skin-tone-3::clap::skin-tone-3: Appreciate your help
bethskurrie
2019-06-17 01:00
You're obviously trying to do something in a language with which you're not familiar. I admire your perseverance, but I think you need to find someone in your company to help you out with the ruby stuff.
bheemreddy181
2019-06-17 02:55
I understand that makes sense. Appreciate your help on the same I think I am clear as of now
aniela.cole
2019-06-20 17:12
Hi everyone, I am not sure if this is correct channel to ask this question, I am trying to run some provider tests using docker compose -> image: dius/pact-provider-verifier-docker
My docker compose file looks like this:
``` pactverifier:
image: dius/pact-provider-verifier-docker
links:
- app:app
environment:
- pact_urls=https://myteamtbroker.pact.dius.com.au/pacts/provider/providername/consumer/consumername/latest
- provider_base_url=http://app:8000```
However, I am getting this error:
```pactverifier_1 | /usr/local/lib/ruby/2.6.0/rubygems.rb:283:in `find_spec_for_exe': Could not find 'bundler' (2.0.1) required by your /app/Gemfile.lock. (Gem::GemNotFoundException)
pactverifier_1 | To update to the latest version installed on your system, run `bundle update --bundler`.
pactverifier_1 | To install the missing version, run `gem install bundler:2.0.1`
pactverifier_1 | from /usr/local/lib/ruby/2.6.0/rubygems.rb:302:in `activate_bin_path'
pactverifier_1 | from /usr/local/bundle/bin/bundle:23:in `<main>'```
I am not familiar with ruby, am I missing something?
matt.fellows
2019-06-20 22:52
It should work just fine in Docker (that?s almost always how I run them)
bethskurrie
2019-06-20 23:12
@aniela.cole try this: https://github.com/pact-foundation/pact-ruby-cli#verify-pacts
bethskurrie
2019-06-20 23:13
Just seen Matt's chat though - yes the pact-js verifier should run on docker
aniela.cole
2019-06-20 23:27
```/bin/sh: ./standalone/linux-x64-1.68.0/bin/pact-provider-verifier: not found
at ChildProcess.<anonymous> (node_modules/@pact-foundation/pact-node/src/verifier.ts:161:55)```
aniela.cole
2019-06-20 23:32
hang on, I did not have this `&& apk add glibc-2.29-r0.apk ` let me add it
aniela.cole
2019-06-21 03:27
I am still getting the same error ```/bin/sh: ./standalone/linux-x64-1.68.0/bin/pact-provider-verifier: not found
lerna ERR!
lerna ERR! at ChildProcess.<anonymous> (node_modules/@pact-foundation/pact-node/src/verifier.ts:161:55)```
matt.fellows
2019-06-21 07:02
Can you run the example project linked in that issue? Something about the environment must be wrong
aniela.cole
2019-06-24 15:46
Matt, my issue was caused by having this volume on my docker-compose file ``` volumes:
- ./:/app
``` and having the node_modules locally.
matt.fellows
2019-06-24 22:19
Thanks for taking the time to respond - most people never come back to provide that feedback :thumbsup:
aniela.cole
2019-06-24 22:21
yes, I believe it was causing the problem. Thank you guys for helping out!
simon.nizov
2019-07-21 15:23
Is there a way to use the mocking service without writing to the pact file?
The idea is to use a feature flag in order to be able to write consumer code, test it and even merge it to master, but without changing the pact in the broker and breaking the provider build.
enrique
2019-07-29 16:04
:wave: Hi! A question, how can I define the provider base url for contract verification from code (as opposed to the CLI). I know I can do it with `pact-js` in the Verifier options. Our use case: we have two contracts against different endpoints implemented in the same code base, but the endpoints for each contract are only available under different subdomains. So, contract `x` needs to be verified against `x.localhost` and contract `y` against `y.localhost`. Otherwise the endpoints will be reported as not found.
matt.fellows
2019-07-31 12:50
Does the Ruby DSL not support this? Given that the pact JS, Go and a number of others depend on it that would be surprising
beth
2019-08-06 09:32
If you're using a native Ruby verification, then you're running the verification against a Rack app, and there is no base url.
enrique
2019-08-06 09:45
It?s a rails API, a monolithic API. A single codebase/process runs multiple providers. Each provider runs in a different subdomain in production. There is a check in place inside the Rails app to expose some routes in one subdomain and other routes in another subdomain. Rails routing constraints are used for that. So, I thought we could configure the `Pact.service_provider` for each provider to attack a different domain `provider_a.localhost`, `provider_b.localhost`, etc.
enrique
2019-08-06 09:46
It seems that I can do that with `pact-js` using `providerBaseUrl` in the `Verifier` options
enrique
2019-08-06 10:01
An alternative approach I?m thinking of would be to run the `rake pact:verify` in a specific Rails environment `contract-verification` where we configure all the providers without subdomain
bethskurrie
2019-08-27 07:27
In Ruby, you don't use a running server. You test directly against the rack app @matt.fellows
matt.fellows
2019-08-27 07:32
Ah yes. I was just saying I'd like to be able to do this in JS and Go with Ron just today
bethskurrie
2019-08-27 07:33
Is there a Rack equiv for other languages though? I got the impression that Ruby was pretty unique in having such a standardised interface.
matt.fellows
2019-08-27 08:14
Less so in JS, but the types are types and it works exactly as you?d expect
matt.fellows
2019-08-27 08:15
Node JS has an HTTP interface that most libraries (e.g. Express) use. Go has the same sort of thing, but goes one deeper and has an in-built HTTP testing package (i.e. you can do all of the things without pulling in a single external dependency)
enrique
2019-08-27 09:20
Oh, yes that would work. We also finally come out with a different approach. But, now, as you mention, the domain is set to `http://example.org`.
enrique
2019-08-27 09:20
We can work around that, but it feels wrong. Guess we need to configure rack test somehow
enrique
2019-08-27 10:12
Does `pact-ruby` expose any configuration option to change the domain of `rack-test`? That would be the ideal solution. It seems that we cannot do it outside PACT because we need access to the app used by PACT.
simon.nizov
2019-08-27 15:12
Hi!
I?m trying to publish the verification results to the broker as described in the docs https://github.com/pact-foundation/pact-ruby/wiki/Verifying-pacts#publishing-verification-results-to-a-pact-broker but for some reason I keep getting the following error:
```
Error returned from verification results publication 400 {"errors"=>{"provider_version"=>["can't be blank", "Version number '' cannot be parsed to a version number. The expected format (unless this configuration has been overridden) is a semantic version. eg. 1.3.0 or 2.0.4.rc1"]}} (Pact::Provider::VerificationResults::PublicationError)
```
While debugging I see that the `provider_application_version` attribute of my `Pact::Provider::VerificationResults::VerificationResult` instance is not blank at all.
Is it a naming thing? The broker expects `provider_version` but the Ruby library sends `provider_application_version` maybe? Any ideas?
simon.nizov
2019-09-06 12:36
Hey @bethskurrie, looks like the travis build of the pact ruby gem is broken? On every new PR it seems.
tanle.oz
2019-09-07 00:24
:eyes: It could be cause by some changes committed by mistake with the release script? https://github.com/pact-foundation/pact-ruby/commit/7371e2f9fc66491481288a2902630419b3f1debc#diff-249018b712e330bd9b05de4e31a5477aR5-R7
bethskurrie
2019-09-09 06:11
I've just reverted those gemfiles. I accidentally committed changes from my local testing.
joseph.haig
2019-10-04 13:45
I have a question that I suspect may have the answer (a) that is not what Pact is for or (b) that has already been answered ? (and possibly also (c) why would you want to do that?). Sorry if this is the the case.
For an API (pact provider, I think is the correct terminology) I would like to have a wrapper library that deals with all the http calls. This wrapper library would then be used by the client application instead of making all the API calls explicitly. I know that I can create the contract between the wrapper library and the API but, in terms of checking the contract during deployment, I want to do this in the client application. Is there a correct way to set this up? Should I (and is it possible to) create a contract between the client application and the wrapper library?
I have already done this (some time ago) and the solution I came up with is that the client application copies the contract from the wrapper library and submits that as its own, but this doesn?t feel right.
joseph.haig
2019-10-04 13:46
I?ve posted this in this channel because I?m mainly working in ruby & rails but it occurs to me that the question may be more general.
joseph.haig
2019-10-04 13:49
I?ve posted it again in #general but I don?t appear to have the option to delete. :disappointed:
c.metz
2019-10-22 14:35
Does anybody have an idea what's going on with the assets on https://github.com/pact-foundation/pact-ruby-standalone/releases/? We cannot download them anymore. This also breaks our pip install pact-python, as that will try to download the binaries there.
matt.fellows
2019-10-22 21:44
What?s the issue you?re having? I can download them just fine (I?m on a train tethering with my wifi hotspot)
c.metz
2019-10-24 09:15
Issues seemed to be a DNS issue indeed. Using Google DNS servers it just works fine.
bheemreddy181
2019-11-21 00:02
@matt.fellows @bethskurrie are dB inserts bad as part of pact workflow on the provider side ?
bethskurrie
2019-11-21 00:03
Personally, I've used mostly used pact for microservices, and for our pact verification tests, we usually use something like sqlite, so it's really easy just to use the DB.
bheemreddy181
2019-11-21 00:03
Typically I am talking more in regards to post endpoint which inserts data into dB I am mocking all the validations that end point does but directly inserting that data into dB because that what my presenter uses to render response back
bethskurrie
2019-11-21 00:03
If it's some heavy weight DB that it would be a pain to use in what should be a fast test, then mocking might be more convenient for you.
bheemreddy181
2019-11-21 00:05
I don?t mock validations on required fields but mock other validations which are supposed to be tested by the team who owns it
bethskurrie
2019-11-21 00:06
it's when you try and use a contract to do functional that it becomes a bad idea.
bethskurrie
2019-11-21 00:06
If the validation changes the way the endpoint behaves, then it's part of the contract.
bethskurrie
2019-11-21 00:07
Eg. if I was trying to test how the endpoint behaved when I put in invalid data, it would not be helpful to return a 200 OK!
bethskurrie
2019-11-21 00:13
Something that might help is to ask, if I stubbed out this component, what other tests do I have to make sure that it will all work together correctly (trying not to rely too much on e2e tests). What would be the consequence of stubbing something out and missing some coverage vs the consequences keeping it in?
bheemreddy181
2019-11-21 00:16
I mean I have enough functional tests on the provider side which tests these validations
bheemreddy181
2019-11-21 00:17
From my understanding I am making sure the return types on my presenter and fields aren?t dropped or required fields aren?t changed etc etc
bethskurrie
2019-11-21 00:17
is there a pact test that checks how the endpoint responds if the validation fails?
bheemreddy181
2019-11-21 00:19
But in that case each request values has different validations so they have to add all that combinations?
bethskurrie
2019-11-21 00:19
With Pact, you *don't* want to try and test the business rules that cause the validation to fail, but you want to pick a stable scenario that will cause the validation to fail so that the consumer knows that that response looks like (assuming all validation failure responses have the same pattern)
bethskurrie
2019-11-21 00:20
You could, of course, cause the validation to fail by modifying something in the provider state, rather than expecting some type of data from the consumer.
bheemreddy181
2019-11-21 00:22
When ever we write provider states in provider what all mocks should generally sit there
bethskurrie
2019-11-21 00:23
I personally mock downstream APIs, and anything that's too hard/slow to run as part of the verification test.
bheemreddy181
2019-11-21 00:23
Aren?t pact tests become duplicates of the provider functional tests if we write them at both places ?
bheemreddy181
2019-11-21 00:23
You mean if there are any third party API?s underneath my provider api ?
bheemreddy181
2019-11-21 00:34
Like say if I can?t create a payment after 10:30 pm cst but if I am running a test after that it would fail ?
bheemreddy181
2019-11-21 00:36
But before 10:30 I will get a 200 ok this will not happen in production because the configurations or jobs which run are restricted to run a hour before
bheemreddy181
2019-11-21 00:36
But let me go back and see all use cases and come back with a list if there are any
bethskurrie
2019-11-21 00:40
Ensuring you always get current time from a mockable location is always a good thing for testing
bethskurrie
2019-11-21 00:41
As long as you have a test that shows how it works when it succeeds, and when it fails.
bheemreddy181
2019-11-21 00:50
Ya that?s where I was mocking some of the underlying validations but I will go back and see which all use-case needs these
bheemreddy181
2019-11-22 02:57
@bethskurrie I have another use case where incoming request should not have date in the past in this you mean me mock the incoming time to current all the time and few are cutoff based requests like said above payment can be created given a :bank: bank is fixed cutoff
bheemreddy181
2019-11-22 02:58
I mean tomorrow if bank is extending the cutoff shouldn?t break the contracts correct those are not breaking contracts too
bethskurrie
2019-11-22 02:58
Is this a unique response? ie. is there anything different about the shape of the response body that comes back when the time cutoff has occurred, compared to other validation errors?
bheemreddy181
2019-11-22 03:01
That?s where I was mocking the validations for these so you mean these are valid mocks ?
bethskurrie
2019-11-22 03:01
All you need is one example of "this is what the response looks like when validation fails". Doing that multiple times is just overhead.
bethskurrie
2019-11-22 03:03
From the docs, "a functional test for the provider would ensure that when a given request was made, that an Order with the correct attributes was actually persisted to the underlying datastore"
bethskurrie
2019-11-22 03:04
Functional tests check "does it do the right thing with what I've sent". Contract tests just check "does it respond in the expected way".
bethskurrie
2019-11-22 03:06
I'd say that functional tests were a superset of contract verification tests -> they test the response is as expected AND that the right thing has been done with the data.
bheemreddy181
2019-11-23 21:30
Hey Beth, i can?t mock future dates all the time as this forces me to update my contract my consumer all the time , if my consumer doesn?t change we will keep verifying with old contract which has the old date as input
bheemreddy181
2019-11-23 21:30
which throws a error like below
```{"errors":[{"error":"validation_failed","reasons":{"effective_on":["Effective date in past."]}}]}```
bethskurrie
2019-11-23 21:47
So, you can either use rack middleware to update the date (look in the "verifying pacts" docs on the Ruby wiki) or you can stub "now".
bheemreddy181
2019-11-23 22:39
bethskurrie
2019-11-24 06:30
Your can set up the rack app manually. It's documented on that same page.
bheemreddy181
2019-11-27 14:28
Beth , thanks for all your inputs i was able to set up rack middleware for one use case
bethskurrie
2019-12-06 02:50
@khoatran now I've refreshed my memory, I've remembered the DSL for message pact is not done in Ruby yet. The underlying logic is done though, because it's being used by pact-js.
bethskurrie
2019-12-06 02:50
Which side would you be interested in using? Consumer or provider, or both?
bethskurrie
2019-12-06 02:51
Oops, now I see the #pact-message-ruby channel that I'd forgotten about! Moving over there.
bheemreddy181
2019-12-12 21:19
Just to verify, are we not supposed to test the data semantics using contract tests @matt.fellows @bethskurrie ?
bheemreddy181
2019-12-16 03:16
Well I am surprised here whether we have to mock the provider side functionality or not now
bheemreddy181
2019-12-16 03:17
As I heard last time from you is that we shouldn?t mock other than any other service dependencies( like if I have third party API?s ) using contract testing
bethskurrie
2019-12-16 03:18
If you're talking about the difference between a validation error response, and a success response, we want to cover that.
bethskurrie
2019-12-16 03:19
If we're talking about the differences between all 20 different enumerations of some particular field, then we don't want to cover that.
bethskurrie
2019-12-16 03:20
There might be a semantic difference between each value, but no structural difference to the response.
matt.fellows
2019-12-16 03:47
do we validate all of the permutations of valid, invalid (and so on), or do we just care about the unique set of responses we can illicit from the provider
matt.fellows
2019-12-16 03:48
from a consumers? perspective, we just care about the possible responses. The meanings of the card numbers are something the provider is interested
bheemreddy181
2019-12-16 03:52
Well from what I felt is semantics is how you are validating the data and inserting the data on to the database where are as syntax is how you are presenting the data back in your response
bethskurrie
2019-12-16 03:54
What you want to test is what a validation failure response looks like. To get that, the easiest way is to give it invalid data, but it's not the validation logic that you really care about.
bethskurrie
2019-12-16 03:55
You could mock some internals of the provider to force it to return a validation failure, but it may be more effort than its worth.
matt.fellows
2019-12-17 21:07
Oh, I thought the mock process in Ruby was purely Rack based, so it didn?t need to spin up an actual port at all.
matt.fellows
2019-12-17 21:07
But admittedly, it?s been a while since I used the Ruby Pact DSL (like, 4 years :stuck_out_tongue: )
bheemreddy181
2019-12-18 00:58
@bethskurrie ^ In case you missed i am open to create a request on the ruby implementation
bethskurrie
2019-12-18 01:04
You'll need to then use a method on the dsl base object to get the base url that it chose.
bheemreddy181
2019-12-18 01:07
you mean to say for mocking the response from the provider i need to get the base url it chose ?
shilpa3006
2019-12-24 05:08
@bheemreddy181 Hi Bheem, I am trying to setup PACT in ruby and trying to run basic example - Animal Service and Zoo App just for understanding purposes. I am able to generate PACT file. After that, when i try command rake pact:verify, nothing happens. It doesn't give me either failure or success messages. I tried pact:publish to see if file gets published to localhost:9292(its by default pointing to this from PACT repo) but getting error saying connection refused. Looks like you got success with setup. Can you please help?
shilpa3006
2019-12-24 05:33
@bethskurrie @matt.fellows I am pretty new to Pact. I am good until generation of Pact file(atleast was able to generate for the animal-zoo example). After that, rake pact:verify is doing nothing. am i missing some steps here?
shilpa3006
2019-12-24 06:33
I could install pact-provider-verifier gem and ran "pact-provider-verifier zoo_app-animal_service.json --provider-base-url http://localhost:9292" command, got all 3 interactions failed:
shilpa3006
2019-12-24 06:35
C:\Automation\PACT\pact-ruby-master\example\animal-service\spec\pacts>pact-provider-verifier zoo_app-animal_service.json --provider-base-url http://localhost:9292
INFO: Reading pact at zoo_app-animal_service.json
Verifying a pact between Zoo App and Animal Service
Given there is an alligator named Mary
a request for an alligator
with GET /alligators/Mary
returns a response which
WARN: Skipping set up for provider state 'there is an alligator named Mary' for consumer 'Zoo App' as there is no --provider-states-setup-url specified.
has status code 200 (FAILED - 1)
WARN: Skipping set up for provider state 'there is an alligator named Mary' for consumer 'Zoo App' as there is no --provider-states-setup-url specified.
has a matching body (FAILED - 2)
includes headers
WARN: Skipping set up for provider state 'there is an alligator named Mary' for consumer 'Zoo App' as there is no --provider-states-setup-url specified.
"Content-Type" which equals "application/json;charset=utf-8" (FAILED - 3)
Given there is not an alligator named Mary
a request for an alligator
with GET /alligators/Mary
returns a response which
WARN: Skipping set up for provider state 'there is not an alligator named Mary' for consumer 'Zoo App' as there is no --provider-states-setup-url specified.
has status code 404 (FAILED - 4)
Given an error occurs retrieving an alligator
a request for an alligator
with GET /alligators/Mary
returns a response which
WARN: Skipping set up for provider state 'an error occurs retrieving an alligator' for consumer 'Zoo App' as there is no --provider-states-setup-url specified.
has status code 500 (FAILED - 5)
WARN: Skipping set up for provider state 'an error occurs retrieving an alligator' for consumer 'Zoo App' as there is no --provider-states-setup-url specified.
has a matching body (FAILED - 6)
includes headers
WARN: Skipping set up for provider state 'an error occurs retrieving an alligator' for consumer 'Zoo App' as there is no --provider-states-setup-url specified.
"Content-Type" which equals "application/json;charset=utf-8" (FAILED - 7)
Failures:
1) Verifying a pact between Zoo App and Animal Service Given there is an alligator named Mary a request for an alligator with GET /alligators/Mary returns a response wh
ich has status code 200
Failure/Error: replay_interaction interaction, options[:request_customizer]
Errno::ECONNREFUSED:
Failed to open TCP connection to localhost:9292 (No connection could be made because the target machine actively refused it. - connect(2) for "localhost" port 9292
)
# C:/Ruby25-x64/lib/ruby/gems/2.5.0/gems/pact-provider-verifier-1.25.2/bin/pact-provider-verifier:3:in `<top (required)>'
# C:/Ruby25-x64/bin/pact-provider-verifier:23:in `load'
# C:/Ruby25-x64/bin/pact-provider-verifier:23:in `<main>'
# ------------------
# --- Caused by: ---
# Errno::ECONNREFUSED:
# No connection could be made because the target machine actively refused it. - connect(2) for "localhost" port 9292
# C:/Ruby25-x64/lib/ruby/gems/2.5.0/gems/pact-provider-verifier-1.25.2/bin/pact-provider-verifier:3:in `<top (required)>'
bethskurrie
2019-12-24 10:31
Which directory are you running `bundle exec rack pact:verify` from @shilpa3006?
bethskurrie
2019-12-24 10:31
That's not going to work unless you've manually started the Animal Service on port 9292.
bethskurrie
2019-12-24 10:38
I think that's likely to be the cause. I'm not familiar with running Ruby on Windows I'm afraid.
bethskurrie
2019-12-24 10:40
Is there anyone else in your company you could ask who might know about Ruby+Windows?
shilpa3006
2019-12-24 23:15
Yes Beth. I am familiar with writing BDD scripts in Ruby. I did so for most of our applications for test automation purposes with Ruby, Cucumber framework. But, I haven't developed applications itself with Ruby.
shilpa3006
2019-12-24 23:27
hmm. now i am curious. which OS is recommended for this pact framework? Also, I don't have Rails. It would be better if there would be any prerequisites w.r.t OS in documentation.
bethskurrie
2019-12-24 23:28
The native Ruby pact verify will manage the lifecycle of the app for you - you don't need to start and stop it and make extra endpoints for setting up the provider states.
bethskurrie
2019-12-24 23:29
It'll be something to do with Windows. If you can reproduce the issue with a Windows ci system as I mentioned in the issue, I may be able to help you.
shilpa3006
2019-12-24 23:29
I wish pact:verify works for me. How can i troubleshoot this issue? I don't see any logging for this as well.
shilpa3006
2019-12-24 23:31
not at the moment. can you pls send me that link where i can reproduce. I saw earlier. Somehow i lost it.
shilpa3006
2019-12-24 23:53
looks like i will not be able to do this. Its against our comp policy. I own a mac, i guess i can try there but eventually i need it at my work :disappointed:
bheemreddy181
2019-12-25 00:22
https://github.com/pact-foundation/pact-ruby-e2e-example better to start with this example
shilpa3006
2019-12-25 21:45
C:\Automation\PACT\pact-ruby-e2e-example-master\provider>bundle exec rake pact:verify:foobar
SPEC_OPTS='' C:/Ruby25-x64/bin/ruby.exe -S pact verify --pact-helper ./provider/spec/pact_helper.rb --pact-uri ./consumer/spec/pacts/foo-bar.json
shilpa3006
2019-12-25 21:46
C:\Automation\PACT\pact-ruby-e2e-example-master>bundle exec rake pact:verify:foobar_using_local_broker
Publishing Foo/Bar pact to pact broker at http://localhost:9292
Error making request - Errno::ECONNREFUSED Failed to open TCP connection to localhost:9292 (No connection could be made because the target machine actively refused it. -
connect(2) for "localhost" port 9292) C:/Ruby25-x64/lib/ruby/gems/2.5.0/gems/pact_broker-client-1.20.0/lib/pact_broker/client/pacts.rb:35:in `get', attempt 1 of 3
shilpa3006
2019-12-25 21:48
I agree @bheemreddy181 Pact is getting generated without any issue. Its just that pact:verify won't work
bheemreddy181
2019-12-25 21:48
You have pact broker running locally? Well ignore that let?s target first with having pact files locally
shilpa3006
2019-12-25 22:29
this one?
SPEC_OPTS='' C:/Ruby25-x64/bin/ruby.exe -S pact verify --pact-helper ./provider/spec/pact_helper.rb --pact-uri ./consumer/spec/pacts/foo-bar.json
shilpa3006
2019-12-25 22:56
C:\Automation\PACT\pact-ruby-e2e-example-master\consumer\spec\pacts>C:/Ruby25-x64/bin/ruby.exe -S pact verify --pact-helper ./provider/spec/pact_helper.rb --pact-uri ./co
nsumer/spec/pacts/foo-bar.json
Traceback (most recent call last):
11: from C:/Ruby25-x64/bin/pact:23:in `<main>'
10: from C:/Ruby25-x64/bin/pact:23:in `load'
9: from C:/Ruby25-x64/lib/ruby/gems/2.5.0/gems/pact-1.42.3/bin/pact:4:in `<top (required)>'
8: from C:/Ruby25-x64/lib/ruby/gems/2.5.0/gems/thor-0.20.3/lib/thor/base.rb:466:in `start'
7: from C:/Ruby25-x64/lib/ruby/gems/2.5.0/gems/thor-0.20.3/lib/thor.rb:387:in `dispatch'
6: from C:/Ruby25-x64/lib/ruby/gems/2.5.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command'
5: from C:/Ruby25-x64/lib/ruby/gems/2.5.0/gems/thor-0.20.3/lib/thor/command.rb:27:in `run'
4: from C:/Ruby25-x64/lib/ruby/gems/2.5.0/gems/pact-1.42.3/lib/pact/cli.rb:26:in `verify'
3: from C:/Ruby25-x64/lib/ruby/gems/2.5.0/gems/pact-1.42.3/lib/pact/cli/run_pact_verification.rb:14:in `call'
2: from C:/Ruby25-x64/lib/ruby/gems/2.5.0/gems/pact-1.42.3/lib/pact/cli/run_pact_verification.rb:20:in `call'
1: from C:/Ruby25-x64/lib/ruby/gems/2.5.0/gems/pact-1.42.3/lib/pact/cli/run_pact_verification.rb:43:in `load_pact_helper'
C:/Ruby25-x64/lib/ruby/gems/2.5.0/gems/pact-1.42.3/lib/pact/cli/run_pact_verification.rb:43:in `load': cannot load such file -- ./provider/spec/pact_helper.rb (LoadError)
bethskurrie
2019-12-25 23:04
This is the config file https://github.com/pact-foundation/pact-ruby-e2e-example/blob/master/.appveyor.yml
bethskurrie
2019-12-25 23:04
Can you run that command that you just ran again from the root of the project this time @shilpa3006
bethskurrie
2019-12-25 23:05
It can't find the `./provider/spec/pact_helper.rb` file because you're running it from the `spec/pacts` directory, and that's a relative path.
bethskurrie
2019-12-25 23:16
ok, this is annoying. When I run the command directly, it passes: https://ci.appveyor.com/project/pact-foundation/pact-ruby-e2e-example/builds/29754338
bethskurrie
2019-12-25 23:20
`bundle exec C:/Ruby25-x64/bin/ruby.exe -S pact verify --pact-helper ./provider/spec/pact_helper.rb --pact-uri ./consumer/spec/pacts/foo-bar.json` from the directory: `C:\Automation\PACT\pact-ruby-e2e-example-master`
shilpa3006
2019-12-26 00:39
C:\Automation\PACT\pact-ruby-e2e-example-master>bundle exec C:/Ruby25-x64/bin/ruby.exe -S pact verify --pact-helper ./provider/spec/pact_helper.rb --pact-uri ./consumer/s
pec/pacts/foo-bar.json
INFO: Reading pact at ./consumer/spec/pacts/foo-bar.json
Verifying a pact between Foo and Bar
A retrieve thing request
with GET /thing
returns a response which
has status code 200
has a matching body
includes headers
"Content-Type" which equals "application/json"
1 interaction, 0 failures
bethskurrie
2019-12-26 00:48
I was hoping that command would error so I could see what was wrong :joy:
shilpa3006
2019-12-26 00:51
Now i have issue with pact-broker. somehow not able to publish to localhost:9292
bheemreddy181
2019-12-26 00:53
Well pact:verify itself works fine this is an issue from windows from what I understand and you should always be on the root while running these commands
bethskurrie
2019-12-26 01:12
@shilpa3006 you'll need to be more specific if you want help. Please say what command you've used, and what the outcome was.
shilpa3006
2019-12-26 17:29
Sure @bethskurrie Before going to pact-broker, I have some questions. I have observed that BarApp's headers and payload have been hardcoded in this example under provider folder - bar_app.rb. If I want to invoke real time service, how can i do that?
shilpa3006
2019-12-26 17:30
@bheemreddy181: Please let me know how you invoking real app were headers and payload is dynamic?
shilpa3006
2019-12-26 17:32
Also, all our headers contain bearer token which generates and lives for few min
shilpa3006
2019-12-26 21:26
@bethskurrie @matt.fellows @bheemreddy181: I have very basic question. If provider services are in .Net, can i write my provider tests in Ruby or its mandatory that i should be writing in .Net since services are developed in .Net?
bethskurrie
2019-12-26 22:03
The only code you need to write for the provider side is the provider state set up code.
bethskurrie
2019-12-26 22:06
To set up the right state in .Net the provider verifier needs to make a request to a url. It's much easier if this url is an endpoint that gets run as part of the underlying provider application code, because you can reuse the services and db connections to insert the right data.
bethskurrie
2019-12-26 22:07
So, no, it's not mandatory to use Net code, but it will be much easier to manage the provider states.
shilpa3006
2019-12-26 22:49
So, it means that from Pact-Ruby framework, I can invoke actual app for getting actual response. But, how can i replace this code, incase i want to invoke actual app?
bethskurrie
2019-12-26 22:50
That's for native Ruby applications. If you want to verify an app in another language, you'll need to use pact-provider-verifier.
bethskurrie
2019-12-26 22:50
No, sorry, you should use the native implementation that wraps the pact-provider-verifier.
shilpa3006
2019-12-26 22:56
ok. so, i can use consumer tests in ruby and use pact-provider-verifier for .net? where do my provider tests be in? Sorry for basic questions. I am trying to understand.
matt.fellows
2019-12-27 02:01
So basically, find the Pact library that matches the language of the code base you are testing
matt.fellows
2019-12-27 02:02
in your case, if your consumer is Ruby use `pact-ruby` (https://github.com/pact-foundation/pact-ruby). If your back end is .NET use `pact-net` (https://github.com/pact-foundation/pact-net)
matt.fellows
2019-12-27 02:03
If you can?t use the language bindings for some reason, there are other approaches. For the provider side, see https://docs.pact.io/implementation_guides/other_languages#how-it-works (which includes the verifier mentioned). But only use this as a last resort
matt.fellows
2019-12-27 02:04
> where do my provider tests be in
As a general rule, they should live with the actual provider code. It?s not necessary, but in the vast majority of cases this is where it makes sense.
bheemreddy181
2019-12-27 02:34
Typically provider and consumer can talk two different languages but they should talk the same thing from API perspective and we can achieve that using pact
shilpa3006
2019-12-27 03:13
Got it. In our case consumer and provider both are in .Net. So, looks like it makes sense to implement pact-net then.
simon.nizov
2020-02-03 13:48
@joseph.haig - this one:
http://blog.pact.io/p/d7c9601f-e2ca-4208-b1c0-f02eaf96c3c2/
bheemreddy181
2020-02-06 15:02
Hey team , we use our own library for authentication between backend services and it?s typically based on the current date and converts the auth to hash with using pact how can I override the authentication - do I ignore the auth and add a test in some other environment ?
joseph.haig
2020-02-06 15:53
Is the problem that it is time based? You might be able to use the timecop gem to fix the time and so fix the authentication hash. (If you are using Rails you can use the built in time helpers instead of timecop)
joseph.haig
2020-02-06 15:55
and then, in the `given` condition, include a note about the time so that the service provider can do the same.
simon.nizov
2020-02-06 19:34
I would look into not including the authorization header in the pact and instead using the
```--custom-provider-header```
option of pact-provider-verifier
https://github.com/pact-foundation/pact-provider-verifier
matt.fellows
2020-02-06 21:22
Is the problem on the consumer side or provider (guessing provider, but want to be sure we?re on the same page)
bheemreddy181
2020-02-06 23:33
typically I see this as an issue on both sides, on my mock i can't typically say how my Hash will look like while setting up mocked expectations for provider for example the header looks something like this
```"Authorization": "APIAuth sample:/m/EVGq2l60r13qd7azBf9qqO20="```
bheemreddy181
2020-02-07 14:45
Thanks @simon.nizov I will give a look with custom headers basically as it?s been a valid request we will go ahead add a custom auth header you mean correct ?
simon.nizov
2020-02-07 14:47
The idea is not to include authentication in the pact. Only add the headers for the provider verification step.
bheemreddy181
2020-02-07 23:24
I was not able to achieve this in the provider states ended up having it on the middleware not sure if this is a great idea , rather than mocking to return true we are actually signing the request
matt.fellows
2020-02-08 02:40
I would still recommend having the header in the pact (for documentation and for completeness, if not too difficult). And then on the provider verification overriding where necessary
bethskurrie
2020-02-08 09:52
I don't want to do an official release of the API until we've integrated it with Pact JVM, because I don't want to have to make any breaking changes if I discover that the API that works for Pact Ruby doesn't work for Pact JVM.
bethskurrie
2020-02-08 09:53
If you're using your own broker you can enable the API by setting `PACT_BROKER_FEATURES=pacts_for_verification` . You'll need to grab the latest versions of the pact gems.
bethskurrie
2020-02-08 10:05
I'm putting out 2.48.0 of the broker and 1.47.0 of pact ruby. You'll need those two together for the informational messages to work correctly.
bethskurrie
2020-02-08 10:06
There's a whole lot of explanatory text that should help understand what's going on
bethskurrie
2020-02-08 10:16
Just be aware that at the moment, the relation that pact-ruby uses to look up the api is `beta:pacts-for-verification`.` When I make the public release, I'll be removing the `beta:` relation and changing it to `pb:pacts-for-verification` so if you had some code running in beta, and it stops working, upgrade both the broker and the gem, so that the officially released gem and API can work correctly together.
matt.fellows
2020-02-09 11:45
I just mean that you should still have the consumer code generate the correct auth header, even if it?s not correct by the time the provider verifies it (and use the approaches described to update it on demand during test cycle)
bheemreddy181
2020-02-11 01:32
Quick question regards to pact provider verification job - from consumer side we want to verify a branch all the time, but where as from provider side we want to look at the master tagged pact. so for this setup do we setup provider as below
``` consumer_version_tags [{name: ENV['pactConsumertags'], all: false, fallback: 'master'}]```
or just use different ENV variable for each job setup ?
bethskurrie
2020-02-11 01:33
> consumer side we want to verify a branch all the time
I don't understand what you mean by this
bheemreddy181
2020-02-11 01:50
Typically as we are running on the PR on GitHub its the branch name or GIT SHA what we are tagging the pact with and we want to verify that particular tag all the time
bethskurrie
2020-02-11 01:51
or is this during the providers "normal" verification, as part of it's own build?
bethskurrie
2020-02-11 01:52
The reason is, there is metadata in that URL that will make sure your results go to the right commits.
bethskurrie
2020-02-11 01:52
If you make a fresh request to the broker to fetch by tag, you'll lose that.
bheemreddy181
2020-02-11 01:56
So send this ${pactbroker.pactUrl} from webhook ? And there is no need for tagging
bheemreddy181
2020-02-11 01:59
How about the provider side verification job it will look at the tags ?
bethskurrie
2020-02-11 01:59
I've just updated https://github.com/pact-foundation/pact_broker/wiki/Webhooks#provider-ci
bethskurrie
2020-02-11 02:00
It depends if you're using matching branch names between the consumer and provider
bheemreddy181
2020-02-11 02:15
And these are nothing but your tags tagged from consumer side on their master build if I understand this correctly
bethskurrie
2020-02-11 02:16
It's been updated recently, so even if you have read it, it's worth another read
bheemreddy181
2020-02-12 22:35
Hey if I am getting this correct there will two rake tasks on Ruby implementation provider in which one will be consuming the pact url from the webhook and running verification and other take task is always pulling the master tagged pact
bheemreddy181
2020-02-12 22:37
And can we use pact-provider-verifier CLI client for running these two tasks independent of which implementation the provider is on
bethskurrie
2020-02-13 03:33
> Hey if I am getting this correct there will two rake tasks on Ruby implementation provider in which one will be consuming the pact url from the webhook and running verification and other take task is always pulling the master tagged pact
Yes.
bethskurrie
2020-02-13 03:34
> And can we use pact-provider-verifier CLI client for running these two tasks independent of which implementation the provider is on
Yes.
yau.yik.shiung
2020-02-17 16:25
hi there would like to get some insight (right/wrong) on the following initiative that i am going to introduce:
? BDD/Cucumber test is often used in microservice isolation testing with by mocking the dependent services
? I am going to replace the current mock server (wiremock) with pact-jvm-server so that the "assumption" made on the mock request/response can be verified on the provider test
? Any potential downside by doing that ? Is this design violating contract testing ?
bheemreddy181
2020-02-18 16:02
Maybe not a bad idea from what I see but if your cukes are testing one-to-one communication between consumer and provider that should be, but if it is taking a long time running through the entire application then these tests might take longer to run and don't forget there will be a provider build if the contract changes. So better to have tests around the communication rather than everything
yau.yik.shiung
2020-02-19 15:19
thanks for the feedback. yeah that's quite true as in BDD we are likely to have some test scenarios that are be redundant in term of the contract testing.
Might want to suggest:
? To revise the test cases to reuse the same mock data as much as possible
? Since swaggers are used, will recommend to run the provider test with swagger validation ( to reduce provider testing time )
bheemreddy181
2020-02-22 00:39
Team, can I use APIs for creating data in provider states, typically in the setup block for provider state?
matt.fellows
2020-02-22 02:07
Of course. The provider state function can do whatever you need it to. Most of the times it's a local in-proc setup, but there's nothing stopping your testa to reach out and hit an API
bheemreddy181
2020-02-22 02:12
Well is it recommended to do so or better skip the total time and just insert data into dB for doing a GET
matt.fellows
2020-02-22 02:13
It?s hard to provide a recommendation without understanding all of the intricacies, but generally speaking, updating the database is going to be the simplest and fastest and easiest to maintain, so I?d start that way
simon.nizov
2020-03-10 17:01
Hey @bethskurrie - did you get a chance to have a look at this? :point_up:
bethskurrie
2020-03-10 21:46
I haven't as my OSS day isn't happening this fortnight. But I haven't forgotten it. Thanks.
bheemreddy181
2020-03-13 20:27
Quick question folks , if i am trying to retrieve pacts with a particular tag say master like mentioned here https://github.com/pact-foundation/pact_broker/wiki/Using-tags#retrieving-pacts how does my rake task look like ?
```Pact::VerificationTask.new(:pull_request_verification) do |pact|
pact.uri "#{REMOTE_PACT_BROKER_BASE_URL}/pacts/provider/provider_namee/consumer/consumer_name/latest", pact_helper: 'spec/service_consumers/pact_helper.rb'
end```
bheemreddy181
2020-03-13 20:28
how does this rake task use config from my pact_helper which is like below
```honours_pacts_from_pact_broker do
# This example points to a local file, however, on a real project with a continuous
# integration box, you would use a [Pact Broker](https://github.com/bethesque/pact_broker) or publish your pacts as artifacts,
# and point the pact_uri to the pact published by the last successful build.
pact_broker_base_url "http://pact_broker.dev.com"
consumer_version_tags [{name: 'master'}]
end
end```
bheemreddy181
2020-03-13 20:29
I mean how does it look for the master tag which is specified in the helper
bheemreddy181
2020-03-16 23:59
@bethskurrie Sorry if you don?t mind can you help me getting some answer for this question ?
bethskurrie
2020-03-17 00:03
But it will ignore any configurations that tell it where to get the pacts from, because the custom task overrides that.
bheemreddy181
2020-03-17 01:16
If in that case if I don?t have my custom task how will it know which consumer it has to pick from broker ? When I say bundle exec pact:verify ?
bheemreddy181
2020-03-17 01:24
Can I pass variables to pact verification task similar to pact publish task like the uri tags and version something like that @bethskurrie ?
bethskurrie
2020-03-17 01:51
You just provide the provider name, and the broker knows which consumers it has.
bethskurrie
2020-03-17 01:52
Yes, you can pass env vars to the verification task the same way you can to any ruby code.
bheemreddy181
2020-03-18 00:40
I was more asking something like below
```PactBroker::Client::Verification.new(:Provider_Pull_Request_Verification) do | task |
task.provider_version = ENV['TRAVIS_BRANCH']
task.pact_broker_base_url = REMOTE_PACT_BROKER_BASE_URL
task.tags = 'master'
end```
So that we can avoid something like this
```Pact::VerificationTask.new(:pull_request_verification) do |pact|
pact.uri "#{REMOTE_PACT_BROKER_BASE_URL}/pacts/provider/sample/consumer/sample/latest", pact_helper: 'spec/service_consumers/pact_helper.rb'
end```
and the idea here is we can run multiple provider branch level verifications in different jobs on CI rather than just running pact:verify which pulls all the pacts at once. thoughts ?
bethskurrie
2020-03-18 01:46
All the custom verification task does is override which pact gets verified
bethskurrie
2020-03-18 01:47
Otherwise you'd have to duplicate your tags, versions and app configurations, potentially leaving to inconsistencies.
bheemreddy181
2020-03-18 13:59
while consumer initiates the verification we are passing in the changed pact , this is for provider side verification for each branch change
joseph.haig
2020-04-08 15:39
If I have defined an interaction can I do the equivalent of `expect(WebMock).to have_requested(:post, url)` for that interaction? Or do I just depend on the fact that the test will report an error if the request has not been made?
anguyen0815
2020-04-15 17:06
Hi guys, I have been trying to write consumer tests for a file upload api and it has to do with image/binary files. I couldn't get it to work so far and it looks like the mock service couldn't handle the binary file. I saw that there is this ticket https://github.com/pact-foundation/pact-mock_service/issues/32. Is that issue still applicable? If so, do you guys have any recommendations as far as testing image upload goes?
sairsule
2020-06-04 08:10
according to feature_support matrix, Asychronous message pacts is not yet implemented for Ruby.
Are there any timelines decided for it?
ian.mcwilliams
2020-06-05 08:28
Hey all! I'm about to implement pact as a provider in a ruby repo. I'm following the documentation here: https://github.com/pact-foundation/pact-ruby
ian.mcwilliams
2020-06-05 08:36
I've added pact_helper.rb, but I'm missing what should go in line 4 here - when I run the rake task, what kicks off an actual test run?
corey
2020-06-05 20:59
~The stub server seems to want an exact body match on requests made to it but we want to be flexible on one field in particular in a JSON POST body and it doesn't seem to support falling back to the matchers specified in the pact~
ian.mcwilliams
2020-06-11 07:52
Hey @bethskurrie I'm following up on the above, have run into an error:
ian.mcwilliams
2020-06-11 07:54
I'm using a local file to test it's working so I tried adding the method `app_in_config_ru` to pact_helper.rb
bethskurrie
2020-06-11 08:18
In the "verifying pacts" docs, look at the first line in the example `Pact.service_provider` block.
ian.mcwilliams
2020-06-12 10:47
Thanks @beth (http://Pactflow.io), I think that's moved us forward, we're now puzzling over another error
ian.mcwilliams
2020-06-12 10:48
Trying to follow the code, it seems to be internal to the Pact gem, but I think it must be trying to run our coded block with the --pact-helper flag?
bethskurrie
2020-06-16 10:41
@ian.mcwilliams I can't see anything unusual in that code that would explain the error you're getting.
bethskurrie
2020-06-16 10:42
Here's an example that I know works. https://github.com/pact-foundation/pact-ruby/blob/master/example/animal-service/spec/service_consumers/pact_helper.rb
bethskurrie
2020-06-16 10:44
Can you checkout the pact-ruby codebase, go into `example/animal-service` run `bundle install` and then `bundle exec rake pact:verify`
bethskurrie
2020-06-16 10:45
Also, when you're running your failing test, can you set the env var `BACKTRACE=true` - you might get more of a stack trace.
ian.mcwilliams
2020-06-16 14:35
Thanks @bethskurrie, I've downloaded pact-ruby and that's running fine
tyler.collins
2020-06-22 17:24
hi All, is there an easy way to prevent the `reports/pacts/help.md` file from being created in my repo when I verify the pacts on the provider side? I realize I can just .gitignore this but I?d rather not have to fiddle with that file
ian.mcwilliams
2020-06-23 19:38
@bethskurrie just an update - I got some support in the team to look into this and as I think you expected it's a problem with spinning up the system. We tried a few things and got the setup into good shape.
ian.mcwilliams
2020-06-23 19:39
It still doesn't work, as the system runs on a thin server and throws :async, which the pact gem doesn't know what to do with as it's running WEBrick
ian.mcwilliams
2020-06-23 19:41
I can't find anything suggesting that the server can be configured in the Pact gem, so perhaps it's just not compatible
ian.mcwilliams
2020-06-23 19:41
Do let me know if that's not the case though and I'll see if we can wrap back round to it in the future :slightly_smiling_face:
nmsuryavanshi
2020-06-24 07:31
Hi All, I m getting the below error when verifying pact using java(provider) can anyone please help. Thanks Expected header 'Content-Type' to have value '{"json_class":"Pact::Term"' but was 'application/json', Expected header 'Content-Type' to have value '"data":{"generate":"application/json"' but was '', Expected header 'Content-Type' to have value '"matcher":{"json_class":"Regexp"' but was '', Expected header 'Content-Type' to have value '"o":0' but was '', Expected header 'Content-Type' to have value '"s":"application\/json"}}}' but was ''
bethskurrie
2020-06-24 07:32
That pact is either a very old old version (like, 7 years old) or it's been hand crafted.
matt.fellows
2020-06-26 11:13
As I mentioned yesterday Namruta, please share your code example and also the gemfile so we can see what's going on. That pact is incorrectly generated
bheemreddy181
2020-07-16 01:21
Quick question around just pulling all the pacts for a provider in ruby https://github.com/pact-foundation/pact-ruby-e2e-example/blob/master/provider/Rakefile#L31 do we just specify the provider name and exclude the consumer name
bheemreddy181
2020-07-16 14:29
How generally people deal with a giant json while writing pact tests , are there any examples how pact.like can be used for bigger jsons?
bheemreddy181
2020-07-17 18:22
Team need help on understanding what i am doing wrong while pulling latest pact from master for one of my provider
bheemreddy181
2020-07-17 18:22
here is the error what i see
```1: from /usr/local/bundle/gems/pact-1.51.0/lib/pact/hal/link.rb:65:in `post!'
/usr/local/bundle/gems/pact-1.51.0/lib/pact/hal/entity.rb:102:in `assert_success!': Error retrieving https://pact-broker.enova.com/pacts/provider/identity/for-verification status=400 {"errors":{"consumerVersionSelectors":["tag must be a string at index 0"]}} (Pact::Hal::ErrorResponseReturned)```
bheemreddy181
2020-07-17 18:32
here is what my pact helper looks like
```# frozen_string_literal: true
require_relative './provider_states'
Pact.configuration.reports_dir = './provider/reports'
provider_version = ENV['GIT_COMMIT'] || `git rev-parse --verify HEAD`
publish_flag = ENV['PUBLISH_VERIFICATION_RESULTS']
Pact.configure do |config|
config.diff_formatter = :embedded
end
Pact.service_provider 'identity' do
app { ProxyApp.new(Identity::Application) }
app_version provider_version
publish_verification_results publish_flag
honours_pacts_from_pact_broker do
# Base URL of pact broker is mandatory
# basic auth username/password and token are optional parameters
pact_broker_base_url 'https://pact-broker.dev.com'
# Advanced configuration
# name: name of the tag
# all: it takes the boolean value true|false. Optional. Defaults to false.
# To fetch all the pacts for a tag, set it to true.
# To fetch only the latest pact, set it to false.
# fallback: In case, the tag does not exist, it will fetch pacts for the fallback-tag. This is an optional
# parameter.
consumer_version_tags [{name: 'master', all: false}]
end
end```
harsh.x.parekh
2020-07-22 19:53
never mind, i figured it out.. its the same as any other controller/request spec
harsh.x.parekh
2020-07-22 23:04
I?m adding pact gem to a large rails app, and `bundle install` complains `Bundler could not find compatible versions for gem "thor"` .. A `bundle update` is downgrading the version of thor the app is using which I don?t want to do.
1. Would it be better to update versions of thor being used in pact and pact-mock_service gems?
2. Would that be worth the effort?
harsh.x.parekh
2020-07-22 23:53
On broad brushes, it seems this will also need upgrading the version of thor on dependent runtime and development gems.. pact-message, pact-mock_service
tyler.collins
2020-07-31 00:15
is there a pact-ruby provider library that supports using minitest as opposed to rspec? I saw that there?s a pact-consumer-minitest gem, and wondering if there?s an equivalent for the provider side
bethskurrie
2020-08-20 01:54
It's a completely separate rake task, and shouldn't interfere with your minitest tests.
bheemreddy181
2020-08-21 17:41
Has any one started seeing issues latest docker image from pact while publishing results to pact broker
heytaco
2020-08-25 03:57
Hi there! My name is HeyTaco!, and you can use me to give people tacos to show your appreciation. My tacos will spread joy through Slack!
bethskurrie
2020-08-25 04:18
If you're doing something like `git rev-parse --something` , put a `.strip` on it
alex.elmekeev
2020-09-10 17:05
tyler.collins
2020-09-14 23:28
I?ve started using the enable_pending flag but oddly the tests are still failing (returning status code 1) even with pending pacts. Here?s some excerpts from the logs
```INFO: Reading pact at http://<pact broker url>/pacts/provider/<provider>/consumer/<consumer>/pact-version/b625d36696f1ae44adc80a9324e0ff6929f342f2
DEBUG: The pact at http://<pact broker url>/pacts/provider/<provider>/consumer/<consumer>/pact-version/b625d36696f1ae44adc80a9324e0ff6929f342f2 is being verified because it matches the following configured selection criterion: latest pact for a consumer version tagged 'master'
DEBUG: This pact is in pending state for this version of <provider> because a successful verification result for <provider> has not yet been published. If this verification fails, it will not cause the overall build to fail. Read more at https://pact.io/pending
Verifying a pact between <consumer> and <provider> [PENDING]
Given user is authenticated
a GET request for stuff
with GET /api/<route>/
returns a response which
has status code 200 (FAILED - 1)
has a matching body (FAILED - 2)
includes headers
"Content-Type" which equals "application/vnd.api+json" (FAILED - 3)
Failures:
1) Verifying a pact between <consumer> and <provider> [PENDING] Given user is authenticated a GET request for stuff with GET /api/<route>/ returns a response which has status code 200
Got 0 failures and 2 other errors:
1.1) Failure/Error: set_up_provider_states interaction.provider_states, options[:consumer]
RuntimeError:
Could not find provider state "user is authenticated" for consumer <consumer>
# /Users/tylercollins/.rvm/gems/ruby-2.6.3/gems/pact-1.54.0/bin/pact:4:in `<top (required)>'
# /Users/tylercollins/.rvm/gems/ruby-2.6.3/bin/pact:23:in `load'
# /Users/tylercollins/.rvm/gems/ruby-2.6.3/bin/pact:23:in `<main>'
1.2) Failure/Error: tear_down_provider_states interaction.provider_states, options[:consumer]
RuntimeError:
Could not find provider state "user is authenticated" for consumer <consumer>
# /Users/tylercollins/.rvm/gems/ruby-2.6.3/gems/pact-1.54.0/bin/pact:4:in `<top (required)>'
# /Users/tylercollins/.rvm/gems/ruby-2.6.3/bin/pact:23:in `load'
# /Users/tylercollins/.rvm/gems/ruby-2.6.3/bin/pact:23:in `<main>'
...and a few more failures that look similar to ^ this
3 interactions, 1 pending
Pending interactions: (Failures listed here are expected and do not affect your suite's status)```
@bethskurrie any idea what might be happening here?
tyler.collins
2020-09-14 23:29
my test setup looks like this
```Pact.service_provider 'provider' do
app_version ENV['CIRCLE_SHA1']
app_version_tags [ENV['CIRCLE_BRANCH']]
publish_verification_results ENV['CIRCLECI'] ? true : false
honours_pacts_from_pact_broker do
consumer_version_tags ['master']
enable_pending true
include_wip_pacts_since (Date.today - 7)
pact_broker_base_url ENV['PACT_BROKER_URL'],
username: ENV['PACT_BROKER_USER'],
password: ENV['PACT_BROKER_PASSWORD']
end
end```
tyler.collins
2020-09-14 23:36
I?ll also clarify that this test is verifying several contracts, some of which are no longer pending. So in the failure described above, there was a successful verification of a regular contract, and an unsuccessful verification of a pending contract from a different consumer in the same test run
bethskurrie
2020-09-14 23:39
@tyler.collins can you recreate the issue using https://github.com/pact-foundation/pact-ruby-e2e-example please
bethskurrie
2020-09-14 23:39
Here's a working example of using pending pacts https://github.com/pact-foundation/pact-ruby-e2e-example/tree/issues/pact-ruby-221-2
bethskurrie
2020-09-14 23:46
You can hardcode these credentials
Broker base URL: https://test.pactflow.io
username: dXfltyFMgNOFZAxr8io9wJ37iUpY42M
password: O5AIZWxelWbLvqMd8PkAVycBJh2Psyg1
tyler.collins
2020-09-14 23:56
I didn?t recreate using ^ that because I found what is causing my specific issue: https://github.com/pact-foundation/pact-ruby/blob/eb1a5893cd8670397cfa93dbd10d618f8f4b6d3c/lib/pact/provider/pact_spec_runner.rb#L162
tyler.collins
2020-09-14 23:57
so it seems I can?t have a combination of pending and non-pending pacts in the same test run with the current implementation.
bethskurrie
2020-09-15 00:04
Most users of the Ruby code are actually users of other languages that use the pact-ruby-standalone, so I've focussed all my dev on that interface, and completely forgotten to do the native Ruby one. Poor Ruby!
tyler.collins
2020-09-15 00:17
It?s the end of the day for me here in California so I gotta run, if you?d still like me to raise any issue for this I can do that in morning :thumbsup:
bethskurrie
2020-09-15 07:26
I'm going to have to give it more thought so that the ones that are not pending still cause the build to fail correctly.
nazar.khmil
2020-10-06 09:35
Hi, I was trying to follow pact message consumer example by following https://github.com/pact-foundation/pact-message-ruby/blob/master/spec/features/create_message_pact_spec.rb
`alice_producer` doesn't seem to be defined
Are consumers still WIP?
a.robecke
2020-10-15 07:57
Hey guys, can anyone point me to a sophisticated tutorial (preferably video) how to setup pact properly.
mateusz.derks
2020-10-22 11:37
Hey, is there any option to select particular consumer with `honours_pacts_from_pact_broker` ? I can only see filtering by tag, not sure how to narrow down the selection to the tag of a particular consumer.
mateusz.derks
2020-10-23 07:32
I guess I can create a consumer-specific tag like `my-project-production` to pick only `my project` consumer. Will check it out.
mikahchapman
2020-10-27 16:03
We just started trying to use the pact-stub-service in our UI testing to try to keep our requests in sync with the contracts, but we found that the regex on query params is not respected. I saw https://github.com/pact-foundation/pact-mock_service/issues/80 and https://github.com/pact-foundation/pact-support/pull/69, but there hasn't been any activity on them in some time.
Some questions about this functionality:
1. Is this part of spec v2 or v3?
2. Is there anything that can be done to help move this forward? At this point, we're having to break the link between the contract and our tests to move forward with our goals.
gerry.power
2020-11-20 13:41
@bethskurrie - is it possible to gain access to and provide help with the https://github.com/pact-foundation/pact-message-ruby consumer? We are rolling out our Ruby evented MicroServices, and are very interested in using Pact message validation.
he
2020-11-20 16:15
Hello all. Second day pact user here. Just trying to get some verifications running. I managed to get some pacts generated, and moved them over to the provider apps. Everything seems to be set up, and the verification even hits my api (I?m seeing an error message from it). But even when I enable backtracing, I?m not seeing it hitting my code in the stack anywhere. So, i?m having trouble figuring out what is causing the error. I thought maybe I could use `binding.pry` to get in there, but it doesn?t seem to be able to get ahold of the session.
Anyone have any debugging suggestions from the provider verification side?
he
2020-11-22 16:59
Aha! It appears my authentication was preventing it to get to the binding.pry statement. Looks like i?m all sorted!
gerry.power
2020-12-07 19:04
```Pact::Message Consumer
Not finished yet as nobody has asked for it. Ping @Beth Skurrie on http://slack.pact.io if you'd like use this.```
Ping @bethskurrie - we would like to use it^
gerry.power
2020-12-16 13:46
Excellent news! I will integrate with our project and test it over the next few weeks.
rafael.manzoni
2021-01-07 15:19
Hi there is any way to use VCR to stub an external api in a provider pact verification test?
rafael.manzoni
2021-01-07 15:30
Just in case, I was able to configure this by using this configuration in VCR:
```config.around_http_request do |request|
VCR.use_cassette(request.uri, &request)
end```
bheemreddy181
2021-01-21 03:26
I see Golang pact has an option to not fail or fail when pacts present on pact broker using `FailIfNoPactsFound` , is there a way we can do that in ruby ?
tsiakos
2021-01-21 14:04
@bethskurrie Hi Beth, I am using pact-message gem for create and verify consumer driven contracts for messages. The provider works fine!! I was wondering if I can use the consumer as well..
gerry.power
2021-01-21 14:11
hello :wave: - see the thread to my request https://pact-foundation.slack.com/archives/C9VHVEDE1/p1607367882061200
gerry.power
2021-01-21 14:11
I have been doing some early testing with it, and it?s working well for us.
bheemreddy181
2021-01-21 23:19
@bethskurrie Can you share some insights on this when ever you are free?
bheemreddy181
2021-01-21 23:24
if i am reading this correct , i feel this feature will enable provider to be able to go green if `master` pacts not present and gives an ability to consumer to verify the contracts on each pull request for the initial integration - correct me if i am wrong
bheemreddy181
2021-01-21 23:31
this my pact_helper.rb
```require_relative './provider_states'
Pact.configuration.reports_dir = './provider/reports'
provider_version = ENV['GIT_COMMIT'] || `git rev-parse --verify HEAD`.strip
publish_flag = true
branch = 'pull_request'
Pact.configure do |config|
config.diff_formatter = :embedded
end
Pact.service_provider 'pgs' do
app { ProxyApp.new(Pgs::Application) }
app_version_tags [branch]
app_version provider_version
publish_verification_results publish_flag
honours_pacts_from_pact_broker do
# Base URL of pact broker is mandatory
# basic auth username/password and token are optional parameters
pact_broker_base_url 'http://localhost:9292', {username: 'pact_workshop', password: 'pact_workshop'}
# Advanced configuration
# Optionally specify the consumer version tags for the pacts you want to verify
# Simple config - a list of tag names
# This will verify the latest pact with the tag `master`
consumer_version_tags ['master']
end
end```
bethskurrie
2021-01-21 23:31
Ok, it seems that the ruby one doesn't let you run with no pacts. The CLI version does (pact-provider-verifier).
bethskurrie
2021-01-21 23:31
``` def run_with_configured_pacts_from_pact_helper
pact_urls = Pact.provider_world.pact_urls
raise "Please configure a pact to verify" if pact_urls.empty?
Pact::Provider::PactSpecRunner.new(pact_urls, pact_spec_options).run
end```
bethskurrie
2021-01-21 23:34
The line of code that needs to change is lib/pact/cli/run_pact_verification.rb:75
bethskurrie
2021-01-21 23:35
(which, despite it's name, is not the pact-provider-verifier CLI, it's the process that runs the RSpec tests)
bethskurrie
2021-01-21 23:36
You'll need to add an option to the DSL lib/pact/provider/configuration/service_provider_dsl.rb
bheemreddy181
2021-01-21 23:37
Appreciate all the work you and Matt did so far for supporting PACT Open Source - its adding a lot of value
bheemreddy181
2021-01-21 23:40
Do you have any examples on how to use can-i-deploy for ruby , if you have those handy can you please share them
bethskurrie
2021-01-21 23:40
The docs are in the usual place (http://docs.pact.io and put "can-i-deploy" in the search bar).
bheemreddy181
2021-01-21 23:56
if i need to modify an incoming request parameter to make sure the tests pass - is that a good way for writing contract tests - like say i need a parameter to be always the next business day on the incoming request , i can't ideally ask consumer tp publish contract daily rather write a middleware to handle that request and modify that parameter to full-fill the use case
bheemreddy181
2021-01-27 22:44
Has any one seen issues with publishing results with latest pact ruby gems
bheemreddy181
2021-01-27 22:44
```/root/project/vendor/bundle/ruby/2.7.0/gems/json-2.5.1/lib/json/common.rb:216:in `parse': 809: unexpected token at 'URL path cannot contain a new line character.' (JSON::ParserError)```
bheemreddy181
2021-01-27 23:04
You think the consumer version which we are pulling from pact broker has a new line ?
bethskurrie
2021-01-28 01:01
Something that is being used to create one of the resources. Maybe it's the tag.
bethskurrie
2021-02-01 22:06
This is the place to ask about the http://config.ru path. Can you tell me what the problem you're having is?
guppy0356.nakira
2021-02-02 01:12
@bethskurrie
Okay :ok_hand:
I try to build gem like devise which expands Rails. In case of devise, it includes dummy rails app for its test. http://config.ru is located at `test/rails_app/config.ru` . I need to update `Pact.configuration.config_ru_path` .
guppy0356.nakira
2021-02-02 01:13
I want to know which file is prefer to call `Pact.configuration.config_ru_path=` .
bethskurrie
2021-02-02 04:36
@guppy0356.nakira don't override the http://config.ru path, set the rack app directly.
bethskurrie
2021-02-02 04:37
``` # Optional app configuration. Pact loads the app from http://config.ru by default
# (it is recommended to let Pact use the http://config.ru if possible, so testing
# conditions are closest to runtime conditions)
app { MyApp.new }```
bethskurrie
2021-02-02 04:37
See the second code example in this section https://docs.pact.io/implementation_guides/ruby/verifying_pacts#using-rake-pactverify
guppy0356.nakira
2021-02-02 05:12
It doesn't work :sob:
```require File.expand_path('../rails_app/config/environment', __dir__)
Pact.service_provider "My Service Provider" do
app { RailsApp::Application.new }
end```
@bethskurrie
bethskurrie
2021-02-02 05:13
@guppy0356.nakira look at what you've told me and ask yourself if you could give any helpful advice with only that information!
bethskurrie
2021-02-02 05:15
If you can put your code in a repository and provide instructions on how to reproduce the error then I'll have the best chance of helping you.
guppy0356.nakira
2021-02-02 05:16
My gem add some routes.
```Rails.application.routes.draw do
resources :books
end```
Dummy Rails app mount this module like this.
```Rails.application.routes.draw do
mount MyApp::Engine, at: :my_app
end```
guppy0356.nakira
2021-02-02 05:30
@bethskurrie
Why should not call like this?
```Pact.configuration.config_ru_path = File.expand_path('../rails_app/config.ru', __dir__)```
dany.marques90
2021-02-09 07:38
Hello guys, I've a problem downloading PACT binaries from our Nexus. (I previously downloaded the tar.gz file from github releases)
It says "Error: Error while installing binary: Checksum rejected for file 'pact-1.88.37-linux-x86_64.tar.gz' with checksum pact-1.88.37-linux-x86_64.tar.gz.checksum"
Any ideas ?
dany.marques90
2021-02-09 10:12
Seems that I've a problem with the npm proxy. this has nothing to do with checksum
gabe707
2021-02-16 20:34
```PactBroker::Client::PublicationTask.new(:local) do | task |
task.consumer_version = "1.0.0"
task.pact_broker_base_url = LOCAL_PACT_BROKER_BASE_URL
task.pattern = "/Users/gabrielholmes/Desktop/ascent-rails/spec/pacts/*.json"
end```
anyone know what im doing wrong here
gabe707
2021-02-16 20:35
Failed to publish pact due to error: PactBroker::Client::Error - Authentication failed
guppy0356.nakira
2021-02-17 06:52
How to enable https protocol. I expect `verify true` enables https protocol, but it doesn't enable https protocol.
```Pact.service_consumer "Zoo App" do
has_pact_with "Animal Service" do
mock_service :animal_service do
port 1234
verify true
end
end
end```
bethskurrie
2021-02-25 07:38
@guppy0356.nakira that's whether or not to very the interactions, not the ssl.
bethskurrie
2021-02-25 07:39
Https is generally a deployment concern, not a development one. Are you trying to verify a deployed provider?
bethskurrie
2021-02-25 07:40
@gabe707 as mentioned in the other channel, you need to upgrade your gem.
guppy0356.nakira
2021-02-25 07:46
I can't update endpoint url because this is constant variable. I need to skip verify ssl when running pact.
bethskurrie
2021-02-25 07:48
Have a look at the mock provider code. I think there may be a ssl setting.
olayemifolakemi
2021-03-05 15:26
Hi there, I'm having this issue when verifying pact on the provider side
bheemreddy181
2021-03-05 21:58
provider is returning charset by default here , you need to update your tests or add a regex match in your headers
bethskurrie
2021-03-11 03:53
You'll need to provide more information than that for us to give you good help.
gabe707
2021-03-11 03:54
pact-provider-verifier --provider-base-url='https://xxx-data-service-staging.herokuapp.com' --broker-token='xxxxxx' --custom-provider-header="Authentication: Bearer xxxxxx" --pact-broker-base-url='https://xxxx.pactflow.io/pacts/provider/Cds%20Graphql/consumer/Ascent%20Rails/version/4.0.0' --provider='Cds Graphql'
gabe707
2021-03-11 03:56
pact-broker-base-url='https://xxxx.pactflow.io/pacts/provider/Cds%20Graphql/consumer/Ascent%20Rails/version/4.0.0'
bethskurrie
2021-03-11 03:57
Read this section https://github.com/pact-foundation/pact-provider-verifier#usage
bethskurrie
2021-03-11 03:57
``` The parameters used when fetching pacts dynamically from a Pact Broker are:
--pact-broker-base-url (REQUIRED)
--provider (REQUIRED)
--broker-username/--broker-password or --broker-token
--consumer-version-tag or --consumer-version-selector
--enable-pending
--include-wip-pacts-since
To fetch a pact from a known URL (eg. when a
verification is triggered by a 'contract content changed' webhook), pass in the pact URL(s) as
the first argument(s) to the command.```
jon.pascoe
2021-03-14 23:33
I?ve just replaced all of the inter-microservice HTTP REST comms in my app with RabbitMQ.
Previously everything was 100% covered with Pact tests. Seemingly testing asynchronous messaging with pact-ruby isn?t possible yet.
Is this on the roadmap?
olayemifolakemi
2021-03-17 16:05
Hi Everyone, I am trying to verify pact but I keeping getting this error:
```Failure/Error: expect(response_body).to match_term expected_response_body
"content": "Pact::Term matcher: /\\w+...*/ generate: \"1. Hey, this is not an actual text\""```
olayemifolakemi
2021-03-17 16:08
The matcher code is like this:
```content: Pact::Term.new(
generate: '1. Hey, this is not an actual text',
matcher: /\w+...*/)```
guppy0356.nakira
2021-03-18 07:11
https://github.com/pact-foundation/pact-message-ruby/pull/18
I open new Pull Request :smile:
olayemifolakemi
2021-03-19 23:24
Hello there! How do we match simple key:value pair, where the value is a basic array, for example: `key: ["element", "elements"]` ?
guppy0356.nakira
2021-03-22 01:26
@bethskurrie
Thank you for your review at https://github.com/pact-foundation/pact-message-ruby/pull/18 .
How to publish new release? I want include new released pact-message at pact-provider-verifier.
bethskurrie
2021-03-22 01:26
Should be out soon https://github.com/pact-foundation/pact-message-ruby/actions/runs/674461634
olayemifolakemi
2021-03-22 12:00
Hello again:slightly_smiling_face:. Please how do I match array of strings in ruby? I have this example:
`array: ["apples", "mangoes", "oranges"]`
Then I am trying to match using `each_like`
`"array: Pact.each_like("apples", {min: 3})`
The result I got:
`["apples", "apples", "apples"]`
The result above was not what I expected
olayemifolakemi
2021-03-22 12:01
I expected it to match the type and not the values...please how do I fix this?
jacek.helper
2021-03-25 13:42
Hi,
I am using quite old version of pact_broker-client 1.28.3 and I would like to know if in the latest version command `pact-broker describe-version --pacticipant <PACTICIPANT> --latest prod --output json` also return free flow text when there is no pacticipant for a given tag? From my point it will be more consistent to return an empty json object or json object with some text field.
Sorry if has been already discussed, but I had no luck to find such discussion on slack.
cheers,
Jacek.
bethskurrie
2021-03-29 08:16
I don't think this has changed. Please raise an issue in the pact broker client project @jacek.helper
bheemreddy181
2021-04-01 20:37
How can i retrieve pact url for a given pact to manually pass the pact_url as an input to verify the pact ?
joseph.method
2021-04-01 21:00
How do you clear the interactions from the mock service in Ruby? It seems like there?s a way to do it via the command line
joseph.method
2021-04-02 01:21
Between tests yeah. I?m trying to do something that I probably shouldn?t be doing, which is to finalize and clear out the interactions in the middle of the test.
gabe707
2021-04-06 16:21
```Pact::VerificationTask.new(:foobar) do | pact |
pact.uri './consumer/spec/pacts/foo-bar.json', pact_helper: './provider/spec/pact_helper.rb'
end```
gabe707
2021-04-06 16:22
how to I add additional variables like authorization token, bearer token, etc in here?
gabe707
2021-04-06 16:23
Pact.service_provider "My Service Provider" _do_
honours_pacts_from_pact_broker _do_
_# Base URL of pact broker is mandatory_
_# basic auth username/password and token are optional parameters_
pact_broker_base_url 'http://...', {username: '...', password: '...', token: '...'}
bheemreddy181
2021-04-08 17:16
How can i modify a request based on the provider states in the middleware ?
bheemreddy181
2021-04-08 20:14
will be really interested in this https://github.com/pact-foundation/pact-ruby/issues/161
bheemreddy181
2021-04-09 00:47
Here is use case i am facing issue with
? My consumer rely's on the validation error from provider where if the date fields surpasses the cutoff , they will change the date and re-send the request.
? Pact Provider doesn't have that ability to change the incoming request for a particular use-case.
? Consumer can write a test but provider can't change the request fields to have the latest date to fail that validation.
Do i need to just mock the validation to return that error ?
normanrs
2021-04-09 22:21
Hello group! Has anyone used Pact with minitest? I'm going to have to setup an endpoint at some point and am right now dreading it because the docs I've seen for doing this aren't detailed at all. Setting up Pact with Rspec uses Rails magic and I'm kindof concerned the setup with minitest is going to be tough. ?
tjones
2021-04-10 06:46
I don't know the answer to this, but I don't think Pact has any rails magic. We use rspec for testing the pact broker itself, which is not a rails app.
tjones
2021-04-10 06:47
(I don't have much ruby knowledge, but I do know that we don't use rails and we do test the broker with pact)
normanrs
2021-04-10 20:42
The magic is in the provider pact_helper.rb. The docs tell you to require "pact/provider/rspec" and then do a Pact.service do block where you tell it what pact contract to honor. That part makes sense - what's difficult is telling it *what response* to validate against the pact. Since it's using an rspec framework, Pact.service knows how to connect to the app. But we've got some Sinatra apps which don't have testing setup with Rspec. So I'm trying to figure out how to connect Pact.service to the app.
normanrs
2021-04-10 20:43
See this example project, from this line down to see what I mean about Rails (Rspec) "magic". https://github.com/DiUS/pact-workshop-ruby/blob/8d5777e4da46a88318c47eb8b51f3e4a336517a5/spec/pact_helper.rb#L16
tjones
2021-04-12 01:15
> what's difficult is telling it what response to validate against the pact.
You don't need to do this. Pact validates all the requests for you. What you do in the provider spec is to tell the provider how to set up the states.
tjones
2021-04-12 01:17
Pact will validate all request/response pairs in the contract. So, for a request that has multiple responses, provider states are used to disambiguate the setup
tjones
2021-04-12 01:17
https://docs.pact.io/getting_started/how_pact_works#provider-verification
This might be helpful
bheemreddy181
2021-04-12 03:02
I feel this is an issue with pact-ruby while validating the headers on provider side
``` Expected header "Content-Type" to equal "application/json; charset=UTF-8", but was "application/json; charset=utf-8"```
is UTF-8 vs utf-8 is different ? Correct me if i am wrong
matt.fellows
2021-04-12 06:51
By default, unless you have a regex matcher on it it?s matching exact value
matt.fellows
2021-04-12 06:52
Header names are case-insensitive, values are not. But, I do believe these parameters in the header are equivalent
matt.fellows
2021-04-12 06:53
matt.fellows
2021-04-12 06:53
anyway, the simple fix is to apply a regex matcher that doesn?t care about the charset, or doesn?t care about the case of the charset
bheemreddy181
2021-04-12 18:13
Even with a matcher pact-ruby fails
``` Expected header "Content-Type" to equal "application\\/json(;\\s?charset=[\\w\\-]+)?", but was "application/json; charset=utf-8"```
gabe707
2021-04-12 19:42
question when pact runs against my local it's returning html format instead of json format
bheemreddy181
2021-04-12 21:26
How can i use dateExpression in ruby ? https://pactflow.io/blog/dealing-with-relative-dates-in-contract-tests/
gabe707
2021-04-12 23:01
bundle exec rake pact:verify:at [https://testexample.pactflow.io/pacts/provider etc
gabe707
2021-04-12 23:03
If the diff output is confusing, try using another diff formatter.
The options are :unix, :embedded and :list
Pact.configure do | config |
config.diff_formatter = :embedded
end
See https://github.com/pact-foundation/pact-ruby/blob/master/documentation/configuration.md#diff_formatter for examples and more information.
gabe707
2021-04-12 23:06
Expected header "Content-Type" to equal "application/json; charset=utf-8", but was "text/html; charset=UTF-8"
matthew.hall
2021-04-15 17:37
any tricks to starting a mock service on one docker container on a particular port, and then accessing it on another docker container, I can't seem to connect.
matthew.hall
2021-04-15 17:39
a previous implementation without pact using the same port worked without issue
raony
2021-04-15 19:29
Hi folks :wave: We are using `pact-ruby` for synchronous requests and now we are going to start using `pact-messages` for contract testing asynchronous events. The message consumer is working fine, but I couldn't manage to make the consumer contract builders share the same contract file. They seem to overwrite each other. Has anyone got into that scenario or has any idea on how to write both pact and pact-messages interactions to the same contract file? Thanks in advance.
uglyog
2021-04-15 22:43
If you use docker compose, it will setup the networking between the containers. Otherwise you need to make the mock server container available to the host or the other container. Remember, with docker, accessing localhost is the loopback inside the container.
matthew.hall
2021-04-15 23:04
thanks, yea we are using compose. I tried various setting: localhost, 0.0.0.0, the container name
matthew.hall
2021-04-15 23:04
nothing works, and our previous implementation which did something similar, (forked the process and listened on the same port) worked fine
uglyog
2021-04-15 23:05
Yes, they still need to be exported. Compose will then allow the traffic on the exposed ports
tjones
2021-04-16 06:51
This is a current limitation - you can't have both message and http pacts in the same contract. Usually the solution is to have two consumer names -something like "YourConsumer (HTTP)" and "YourConsumer (Message)"
github
2021-04-19 00:57
GitHub app is successfully upgraded in your workspace :tada:
To receive notifications in your private channels, you need to invite the GitHub app `/invite @GitHub`
matthew.hall
2021-04-19 19:44
```require 'pact/consumer/rspec'
require 'socket'
Pact.service_consumer "partner websites cron" do
has_pact_with "SimilarWeb" do
mock_service :similar_web do
port 5678
host "0.0.0.0" # Optional, defaults to "localhost". Useful when using a standalone mock service.
standalone false # Optional. If true, does not automatically start a mock service
# You must start/stop the mock service manually.
end
end
end```
matthew.hall
2021-04-19 19:45
```# lsof -i -P -n | grep LISTEN
ruby 1285 root 7u IPv4 635140 0t0 TCP 127.0.0.1:5678 (LISTEN)```
matthew.hall
2021-04-19 19:46
no matter what i put as the host, I can only get it to listen on 127.0.0.1
andrewmorton
2021-04-26 13:37
:wave: We're looking to use `pact-messages` to verify some asynchronous events. I'm having some difficulty getting the pact test to run using `bundle exec pact:verify` based on the documentation on https://docs.pact.io/implementation_guides/ruby/verifying_pacts as it keeps failing with `This document does not use a recognised Pact format:` (I'll put the full message in the thread). Likely it's something simple I've messed up but any tips / tricks would be appreciated
andrewmorton
2021-04-26 13:38
```This document does not use a recognised Pact format: {"consumer"=>{"name"=>"Service B"}, "provider"=>{"name"=>"Service A"}, "messages"=>[{"description"=>"feature X", "contents"=>{"text"=>"Hello world"}, "providerStates"=>[], "matchingRules"=>{}}], "metadata"=>{"pactSpecification"=>{"version"=>"2.0.0"}}} (Pact::UnrecognizePactFormatError)```
andrewmorton
2021-04-26 13:38
what is weird is that I copied the structure from the `pact-messages` repo and updated it (another team is in the process of integrating it with the consumer)
andrewmorton
2021-04-27 11:19
Resolved this, turns out I was missing a require in the `pact_helper.rb`
matt.fellows
2021-04-29 02:44
As discussed, a great starting point would be to attempt to use Pact on a real project. This will help get you in a helpful frame of mind
matt.fellows
2021-04-29 02:45
Next, you could take a look at some easy pickings: https://github.com/pact-foundation/pact-ruby/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22
bheemreddy181
2021-05-05 22:12
Beth , don't we need enable_pending flag added here https://github.com/pact-foundation/pact-ruby/blob/master/lib/pact/provider/configuration/service_provider_dsl.rb#L18 ?
bheemreddy181
2021-05-05 22:35
I don't think i need that , i confused around how can i pass a `enable_pending` with a custom verification task
bheemreddy181
2021-05-05 22:41
is this correct
```Pact::VerificationTask.new(:pact_consumer_verification) do |pact|
pact.uri ENV['PACT_URL'], pact_helper: 'spec/service_consumers/pact_helper.rb', ignore_failures: true
end```
bheemreddy181
2021-05-05 22:41
bheemreddy181
2021-05-05 22:41
confused with `Process will always exit with exit code 0` this description though
bethskurrie
2021-05-06 00:53
> Note that the pending feature is only applicable to the https://docs.pact.io/pact_nirvana/step_4#d-configure-pact-to-be-verified-when-provider-changes, where the list of pacts to be verified are fetched from the Pact Broker. It does not apply to the https://docs.pact.io/pact_nirvana/step_4#e-configure-pact-to-be-verified-when-contract-changes workflow where the pact URL is passed to the job via the webhook. This is because the pending status of the pact content is calculated based on the tags that the provider will use to publish the verification results, and the 'contract content changed' webhook cannot know this information.
bethskurrie
2021-05-06 00:53
The ignore_failures was a precursor to pending, and I never officially released it.
bethskurrie
2021-05-06 00:54
If this is for the webhook flow, it doesn't matter if that fails or not. It's expected to fail.
bheemreddy181
2021-05-06 00:55
So with ignore-failures is always pass even if the verification fails ?
bheemreddy181
2021-05-06 00:57
So ideally webhook workflow should always fail for the pacts which doesn?t have a provider state ?
bheemreddy181
2021-05-06 01:05
I am following the use case http://blog.pact.io/2020/02/24/how-we-have-fixed-the-biggest-problem-with-the-pact-workflow/ which says `The contract (consumer expectations) has changed.`
Which is the use case I am looking at where consumer added new expectations ( TDD ) those are not implemented yet so in that feature branch pacts shouldn?t pass ?
bheemreddy181
2021-05-06 22:26
I am still confused with pending pacts feature here
```The fact that the provider build can be broken by new or incorrect expectations in the contract (which is effectively written by the consumer team) is one of the biggest problems people have with Pact. It leads to contention between teams, and in some cases, stops teams using Pact at all.```
isn't this means consumer can push new expectations and there are chances provider is not ready yet thats where this pending flag is needed
Above information is contradicted a bit with https://pact-foundation.slack.com/archives/C9VHVEDE1/p1620262404096100
bheemreddy181
2021-05-06 22:53
```The fact that the provider build can be broken by new or incorrect expectations in the contract (which is effectively written by the consumer team)```
this only happens when the contract content changed webhook is triggering a job on provider
bethskurrie
2021-05-06 22:55
One which is triggered by the webhook that only does the verification for the changed pact.
bethskurrie
2021-05-06 22:56
We don't care about breaking the "webhook triggered build" because nothing should be depending on it. It's just a little thing that runs on the side.
bethskurrie
2021-05-06 22:56
We do care about blocking the provider's main CI/CD pipeline, because that stops them deploying.
bethskurrie
2021-05-06 22:57
This page describes how the builds should be set up https://docs.pact.io/pact_nirvana/step_4
bheemreddy181
2021-05-06 23:00
@bethskurrie here is the thing on the consumer branch which has new expectations and failed on build which will never get merged to master no ? if that is the case the second build you are talking about will never happen no ?
bheemreddy181
2021-05-06 23:01
As providers main CI/CD build is only looking at `master` / `prod` tagged contracts the above contract will never make it to master as the consumer CI failed on the branch
bethskurrie
2021-05-06 23:02
Or at least read through this section https://docs.pactflow.io/docs/workshops/ci-cd/workshop
bheemreddy181
2021-05-06 23:42
Beth here is the difference what we are doing from the above documented approach
Steps :
1. Consumer create a contract in the feature brach ( `feature-x` and pushes a commit
2. Build runs on the CI for consumer and publishes a contract tagged `feature-x`
3. Pact broker receives the contract with that and sends a webhook to provider to trigger a CI build on `master` branch with a reference to the pact on the `feature-x`
4. Provider CI build triggers and pull the contract with reference sent from consumer and the build fails and publishes results which only applies for the feature branch.
5. Consumer is blocked until provider either makes the changes and adds a provider states here
6. Regular CI builds don't fail here because on regular CI builds we are only looking at `master` contracts which gets tagged only once the feature branch goes green.
bheemreddy181
2021-05-06 23:44
Typically we tag the contracts twice once on the feature branch with branch name and next once merged on the master with branch name
bheemreddy181
2021-05-07 00:20
Now to unblock the consumer, provider has to make changes to support the new contracts else consumer has to wait ?
bethskurrie
2021-05-07 00:21
That's how integrations work - if the consumer wants to deploy a feature that requires the provider to do something, the consumer can't deploy until the provider supports it.
bethskurrie
2021-05-07 00:21
it's just surfacing that reality in a way that doesn't let you deploy or merge anything broken.
bethskurrie
2021-05-07 00:22
Before pact, you would only find out that the consumer/provider didn't work together when they both got deployed to the test environment and everything broke.
bethskurrie
2021-05-07 00:23
What I would suggest about your workflow is that turning on pending pacts means that the consumer would continue to get feedback on whether or not their feature pact was implemented yet or not.
bethskurrie
2021-05-07 00:23
The output that would be shown when the provider does a local verification would prompt them to add the provider state to their master build, without breaking it.
bethskurrie
2021-05-07 00:24
If you don't turn on pending pacts, the provider will need to make a deliberate change to the verification configuration to pull in that pact.
bheemreddy181
2021-05-07 00:25
how will that happen that won't happen no ? as provider is always looking at `master` tagged pact he will never know about `feature-x` tagged pact
bheemreddy181
2021-05-07 00:28
my custom verification task is always pulling the incoming pact_url based pact
bethskurrie
2021-05-07 00:29
The custom verification task is only for the "content changed" webhook flow.
bheemreddy181
2021-05-07 00:29
normal provider yes like below
```Pact.service_provider 'pgs' do
app { ProxyApp.new(Pgs::Application) }
app_version provider_version
app_version_tags [provider_branch]
publish_verification_results publish_flag
honours_pacts_from_pact_broker do
pact_broker_base_url 'https://pact-broker.enova.com'
enable_pending true
consumer_version_selectors [
{ tag: 'develop', latest: true },
{ tag: 'master', latest: true }
]
end
end```
bheemreddy181
2021-05-07 00:32
does that mean provider has to manually point to the consumer feature branch to know which all provider states needs to be added for the new contracts ?
bheemreddy181
2021-05-07 00:32
like
```consumer_version_selectors [
{ tag: 'feature-x', latest: true },
{ tag: 'master', latest: true }
]```
^
bethskurrie
2021-05-07 00:32
Really, go and do the CI/CD workshop. It will answer all these questions.
bethskurrie
2021-05-07 00:35
You know how the pact URL is passed in to the build for the pact changed webhook? This is how I run that.
bethskurrie
2021-05-07 00:35
Because the PACT_BROKER_TOKEN and PACT_BROKER_BASE_URL env vars are set, it just works.
bheemreddy181
2021-05-07 01:04
Oh this is how my custom task is written
```# consumer triggers this rake task from pact broker like : bundle exec pact:verify:pact_consumer_verification
# incoming request will have a reference to the pact file for consumer pull request
Pact::VerificationTask.new(:pact_consumer_verification) do |pact|
pact.uri ENV['PACT_URL'], pact_helper: 'spec/service_consumers/pact_helper.rb', ignore_failures: true
end```
And a sample PACT URL : PACT_URL="https://pact-broker.enova.com/pacts/provider/pgs/consumer/paymentinstructionservice/pact-version/7a4b428d139d37b0231e9b61c672f87ad46f0c33/metadata/Y29uc3VtZXJfdmVyc2lvbl9udW1iZXI9MDAxNmI2NjkxYWM2ZDY5M2EyNGQ5NGMzMzE2ZDBhNzliM2YxZWQ0MiZjb25zdW1lcl92ZXJzaW9uX3RhZ3NbXT1kZXZlbG9w"
matthew.hall
2021-05-12 15:15
@uglyog ^ I think I found the issue with remote connections if you could take a look and consider this fix please. Thanks
bethskurrie
2021-05-13 00:09
@matthew.hall the host is definitely used because otherwise this Dockerfile would never have worked https://github.com/pact-foundation/pact-mock-service-docker/blob/master/Dockerfile#L18
bethskurrie
2021-05-13 00:09
The service has to be bound to `0.0.0.0` otherwise it is not accessible outside the Docker container.
```CMD bundle exec pact-mock-service service --host 0.0.0.0 --port $EXPOSED_SERVICE_PORT --pact-dir ./pacts```
matthew.hall
2021-05-13 02:46
thanks, but I am creating the mock service with the ruby library, not using the command line version
matthew.hall
2021-05-13 02:48
```Pact.service_consumer "partner websites cron" do
has_pact_with "similar web" do
mock_service :similar_web do
port 5678
host "0.0.0.0" # Optional, defaults to "localhost". Useful when using a standalone mock service.
standalone false # Optional. If true, does not automatically start a mock service
# You must start/stop the mock service manually.
end
end
end```
matthew.hall
2021-05-13 02:50
I can only ever get it to listen to localhost for some reason. any other setting causes a rack exception to be thrown and the server doesn't start
github2
2021-05-18 00:22
[pact-foundation/pact-mock_service] New release _https://github.com/pact-foundation/pact-mock_service/releases/tag/v3.9.0_ published by github-actions[bot]
matthew.hall
2021-06-01 20:20
Is it possible to get pact consumer library to work with TestUnit (instead of rspec and minitest) ?
github2
2021-06-03 05:54
[pact-foundation/pact-mock_service] New release _https://github.com/pact-foundation/pact-mock_service/releases/tag/v3.9.1_ published by github-actions[bot]
scott.riley111
2021-06-25 08:37
Is anyone working on a relatively old version of Rails (3.2) as a provider with pact? Running into some issues and want to know if there?s precedent or if I?m going to just end up in pain :slightly_smiling_face:
bheemreddy181
2021-06-29 23:00
Beth / Matt - Any idea why do we see these error when we do pact verification on provider side the interactions are passing as expected but i do see connection not allowed
bheemreddy181
2021-06-29 23:03
i have `WebMock.disable_net_connect!(allow: "http://pact-broker.enova.com"])` in my rails helper too
matthew.hall
2021-07-15 14:20
```# In /spec/service_providers/pact_helper.rb
require 'pact/consumer/rspec'
# or require 'pact/consumer/minitest' if you are using Minitest
Pact.service_consumer "Zoo App" do
has_pact_with "Animal Service" do
mock_service :animal_service do
port 1234
host "0.0.0.0" # optional, defaults to "localhost"
end
end
end```
bethskurrie
2021-07-16 23:54
@bheemreddy181 because the tests failed, it's trying to get the previous version to show a diff to you.
bethskurrie
2021-07-16 23:55
I won't know why your webmock is not allowing the connection, because your configuration looks fine to me.
bethskurrie
2021-07-16 23:57
@scott.riley111 what issues are you seeing? Pact does not know or care about Rails. It does however get affected by active bloody support, and can be affected if you have a custom JSON serialization gem.
bethskurrie
2021-07-16 23:58
@matthew.hall yes, it shouldn't be too hard if you wanted to try. You can look at the mini test bindings and copy how it does that.
bethskurrie
2021-07-16 23:59
The touchpoints are small as you can see https://github.com/pact-foundation/pact-consumer-minitest/blob/master/lib/pact/consumer/minitest.rb
bheemreddy181
2021-07-17 04:04
Actually @bethskurrie@bethskurrie@bethskurrie tests were not failing here that?s where it confused me
olayemifolakemi
2021-07-18 07:33
Hello there:wave:. How do I verify pact for data that has null values included?
bethskurrie
2021-07-18 23:59
I can see this question coming on https://docs.pact.io/faq/#why-is-there-no-support-for-specifying-optional-attributes
scott.riley111
2021-07-19 09:56
I ended up needing to swap over to using the standalone verifier because of gem version conflicts/requirements
scott.riley111
2021-07-19 09:56
from memory it was something like `rack` needing >= 2 with `pact-ruby`, but we?re on `1.5` I think
bethskurrie
2021-07-19 10:49
Or you need to make sure the values are populated by the provider state @olayemifolakemi
github2
2021-07-27 07:01
[pact-foundation/pact-support] New release _https://github.com/pact-foundation/pact-support/releases/tag/v1.16.8_ published by github-actions[bot]
bheemreddy181
2021-07-27 21:56
Did something changed in the latest pact support gem
``` 4: from /home/circleci/project/vendor/bundle/ruby/2.5.0/gems/pact-support-1.16.8/lib/pact/matching_rules/merge.rb:41:in `recurse'
3: from /home/circleci/project/vendor/bundle/ruby/2.5.0/gems/pact-support-1.16.8/lib/pact/matching_rules/merge.rb:85:in `wrap'
2: from /home/circleci/project/vendor/bundle/ruby/2.5.0/gems/pact-support-1.16.8/lib/pact/matching_rules/merge.rb:100:in `handle_regex'
1: from /home/circleci/project/vendor/bundle/ruby/2.5.0/gems/pact-support-1.16.8/lib/pact/matching_rules/merge.rb:100:in `new'
/home/circleci/project/vendor/bundle/ruby/2.5.0/gems/pact-support-1.16.8/lib/pact/term.rb:31:in `initialize': Value to generate "{"case_types"=>["Bankruptcy", "Credit counseling", "Legal complaint", "ID theft", "Contingent Placement", "Deceased", "Cease & Desist", "Credit Reporting", "Debt Sale"], "loan_number"=>"2021IL316410875"}" does not match regular expression /\S.*loan_number=\d{4}[A-Z]{2}\d*/ (Pact::Error)```
which used to work pact support 1.0 version vs 1.16
bheemreddy181
2021-07-27 21:58
Something similar https://github.com/pact-foundation/pact-support/issues/46
bheemreddy181
2021-08-11 21:00
Team - Question around tagging failures from pact provider
```E, [2021-08-11T15:29:52.458498 #1291] ERROR -- : Coverband Error: #<RuntimeError: coverage measurement is not enabled> coverage measurement is not enabled
/home/circleci/project/vendor/bundle/ruby/2.4.0/gems/pact-1.32.0/lib/pact/provider/verification_results/publish.rb:87:in `block in tag_versions': Error returned from tagging request 404 (Pact::Provider::VerificationResults::PublicationError)
from /home/circleci/project/vendor/bundle/ruby/2.4.0/gems/pact-1.32.0/lib/pact/provider/verification_results/publish.rb:83:in `each'```
adamdullenty
2021-09-08 23:04
Hey everyone. I'm just working through the pact guide for Ruby at the point where I try to run the rake task from the producer project in order to verify against the pact from the consumer project: https://github.com/pact-foundation/pact-ruby#in-the-animal-service-provider-project
I'm getting this error:
```RuntimeError:
Could not find http://config.ru file at ./config.ru Please configure the service provider app or create a http://config.ru file in the root directory of the project.```
The "producer" in this case is a Ruby lambda function written using Serverless, so it doesn't really make sense to have a `http://config.ru` but I can carry on down this route if there's a known way to get this to work?
bethskurrie
2021-09-08 23:05
```Pact.service_provider "My Service Provider" do
app { MyApp.new }
end```
bethskurrie
2021-09-08 23:06
You can use a rack adapter like this one https://github.com/logandk/serverless-rack
adamdullenty
2021-09-09 10:22
I've been reading into the serverless-rack plugin and converting all of our serverless functions into rack apps is a bit much for the sake of contract testing. Do you think there would be a way of getting this up and running using serverless offline, running the lambda function in the background as part of a test script, and then calling `bundle exec pact verify` to avoid having to configure Rake, then killing the lambda?
adamdullenty
2021-09-09 12:48
Hey, I'm just looking for some pointers on how to debug an issue I'm seeing please.
I'm at the step in the guides where you verify your pacts in the producer app, I've got `pact_uri` configured to point at the shared JSON file in the consumer app, and getting the following error:
```Could not find provider state "valid payload" for consumer Rails Backend```
(the naming isn't overly detailed but I'm just working on a proof of concept branch currently)
I'm a bit puzzled because it must be reading the JSON file in order to find the provider state, so then where is it looking when it says it can't find the provider state...?
adamdullenty
2021-09-09 12:49
Does this actually mean that it can't verify the state against the producer..? I'd have expected to see some other failure message if this was the case, e.g. no response from the server, or response does not match or something.
bethskurrie
2021-09-10 01:34
As in, the code to set up the data for the provider state in the codebase.
bethskurrie
2021-09-10 01:35
Here are the docs @adamdullenty https://docs.pact.io/implementation_guides/ruby/provider_states/
bethskurrie
2021-09-10 01:37
@adamdullenty you can, but having done it myself, I found it tediusly slow to execute the tests.
bethskurrie
2021-09-10 01:38
It's actually a very small piece of code to turn a rack request into a serverless request.
bethskurrie
2021-09-10 01:41
If you want to stick with your locally running serverless app, you'll need to use the pact-provider-verifier instead. You won''t be able to use the native ruby rack verification tool.
adamdullenty
2021-09-13 08:14
Thanks, from the readme it originally sounded like these were optional if you needed to set up data in a specific way (I didn't given it's a stateless lambda): https://github.com/pact-foundation/pact-ruby#using-provider-states
adamdullenty
2021-09-13 08:24
OK, thanks. Can you see any downsides to having an alternative setup where the rack layer is set up purely for contract testing, i.e. we could have a `serverless.test.yml` for testing, and an un-altered `serverless.yml` for staging/production?
bethskurrie
2021-09-13 09:45
Contract testing is not about "testing in a production like manner", its about deliberately excluding all the deployment concerns and just focussing on the inputs and outputs, so having a different set up for contract testing and deployment is fine.
bethskurrie
2021-09-13 09:46
The consumer needs to not declare a provider state in the interaction then @adamdullenty
adamdullenty
2021-09-13 09:47
Apologies for all the questions. There's another thing I've been wanting to ask about our use case for testing the interaction between our Rails back end and a Ruby lambda.
One of our Lambda functions actually returns PDF data, i.e. `application/pdf` . Is this just a no-go with http://pact.io or is there a way to get this to work with an expected PDF response? The docs seem to suggest that it only works with JSON but curious whether this is a definite non-starter or something that can be worked around
bethskurrie
2021-09-13 09:51
It can be done with some pact implementations, but Ruby isn't the best for it.
bethskurrie
2021-09-13 09:51
You're never going to cover every aspect of a service with contract testing - I think that's one of the cases where an integration test is probably a better option.
adamdullenty
2021-09-13 10:41
https://pact-foundation.slack.com/archives/C9VHVEDE1/p1631238033016600?thread_ts=1631142261.007600&cid=C9VHVEDE1 <-- am I right in thinking you're using this instead of the https://github.com/logandk/serverless-rack plugin?
adamdullenty
2021-09-13 20:03
The issues I've been hitting with the `serverless offline` option are to do with stubbing / mocking AWS services. I think you mentioned this as being a downside @bethskurrie . Basically there seems to be no simple way of doing this given we're booting the lambdas via the serverless offline command line tool rather than spinning up an instance from within the Ruby code.
If we did go down the route of the rack adapter option, is this (stubbing out parts of the AWS client) something you can do via the provider state `up` / `down` methods, or would you usually do this when defining `app { ... instance of rack app goes here ... }` within `pact_helper.rb`?
adamdullenty
2021-09-13 20:50
would you be able to dig out a code snippet by any chance for how you are mounting the existing handlers within a Sinatra app with minimal changes please? I'm still trying to keep things as close to production as possible but the way I'm working through now seems pretty far removed
olayemifolakemi
2021-09-20 17:27
Hi there. I have a question about `provider states`. It looks like the values set in the `Consumer` side must match the created data in `provider states` in the `Provider` side. I would like to know if there's a way to use a random value like ids that's different from whats in the Pact json file...
Also, how do I verify `StartCursor` and `EndCursor` for a Graphql query in the Provider side? I keep seeing this error:
tjones
2021-09-21 05:08
In general, this is what Matchers are for - see: https://docs.pact.io/getting_started/matching/
tjones
2021-09-21 05:08
So, you can say "startCursor is a string, for example "foo"", with something like `startCursor: Matchers.like("foo")`
olayemifolakemi
2021-09-21 10:22
But I am getting the above error when running pact:verify in the Provider code
bethskurrie
2021-09-21 21:21
@olayemifolakemi you need to set those values to something in your provider state set up code.
bethskurrie
2021-09-21 21:21
If you expect a String, it can't be nil (because the verifier can't tell what type that nil would have been if it had been there).
nareshnavinash
2021-09-23 09:33
Hey Team :wave:
I have raised a PR in `pact-support` repo to remove the `randexp` dependency. - https://github.com/pact-foundation/pact-support/pull/91
? `randexp` is removed from `pact` in this PR - https://github.com/pact-foundation/pact-ruby/pull/202
? Issue with the randexp is that it overrides the Array's pick method in this file - https://github.com/benburkert/randexp/blob/master/lib/randexp/core_ext/array.rb
? This is causing issues with other unit tests which we have in our repo.
? I have tested running pact test by removing this randexp dependency and seems like tests are not affected by this.
? Also I see that this is just required within a single file and not used at any other place.
We are blocked with this and it would be a great help if someone could get his merged and pushed to `Ruby gems` Or if we have some other alternative to avoid `Array.pick` override by the `randexp` please let me know the same.
Thanks :pray:
jamesatroughton
2021-09-28 10:48
Hi there, I have a similar question. I want to provide a place holder with a default value so that i can create a contract but replace the value when verifying against the provider. I have got it working in java by adding
``` .valueFromProviderState("id", "${id}", "2b2a8b08-bfba-4524-b45a-0cbd2e137dbf") ```
What is the equivalent in ruby? I cant see it in the docs
jamesatroughton
2021-09-30 11:51
Hi there, I am currently writing some consumer tests in a ruby service. I have a requirement to be able to inject a value into the contract that will be used against provider (a random `id` that is a UUID generated by the DB). I can see that pact jvm dsl allows you to provide a placeholder with a default value that can then be replaced e.g.
``` .valueFromProviderState("id", "${id}", "2b2a8b08-bfba-4524-b45a-0cbd2e137dbf") ```
Is there a similar way of doing it in ruby? Many thanks
bethskurrie
2021-09-30 22:13
@jamesatroughton you could try using Rack middleware to modify the response. You'd have to hand write the interceptor though.
bethskurrie
2021-09-30 22:14
There was a PR opened to be able to inject values returned from the provider state, but the author never finished it unfortunately.
dimundo
2021-10-01 07:23
https://pact-foundation.slack.com/archives/C9VHVEDE1/p1633068897055200
will it be also added to broker docker ?
jamesatroughton
2021-10-01 08:43
Ahh okay @bethskurrie thanks for this. My provider test is written in java, is there a neat way to overwrite the value in the contract thats created by my ruby consumer test?
bethskurrie
2021-10-01 09:02
Find the right framework. What you want has got better support in jvm. I can't remember what it's called though.
bethskurrie
2021-10-01 09:04
I'm confused @jamesatroughton. In the other conversation you said your provider was JVM. This makes it sound like it's your provider that's Ruby.
jamesatroughton
2021-10-01 09:47
Hey, apologies @bethskurrie my consumer is ruby my provider is JVM. I wanted to see if I could get the placeholder working in java as a POC to myself as its the language I am more familiar with. But as my consumer is ruby I need to some how implement the functionality in ruby.
bethskurrie
2021-10-17 21:27
bethskurrie
2021-10-17 21:27
> or would you usually do this when defining `app { ... instance of rack app goes here ... }` within `pact_helper.rb`?
Within the rack adapter there.
bethskurrie
2021-10-17 21:31
> mounting the existing handlers within a Sinatra app with minimal changes please
We actually wrote it as a Sinatra app in the first place and used the lambda.rb to map from the incoming events to the sintra app.
bethskurrie
2021-10-17 21:32
Rack middleware is super simple though - I think it would be straightforward to write a custom bit of code with a hash that mapped the incoming path to a method call.
bethskurrie
2021-11-13 05:31
@dimundo there's already a setting to disable ssl verification for webhooks (I assume that's what you mean)
bethskurrie
2021-11-13 05:36
Ruby people! I'd love another pair of eyes on the pact broker client build. A month ago, I had green builds. The gems have not changed, and the rubies have not changed, but now I have broken builds.
Working: https://github.com/pact-foundation/pact_broker-client/actions/runs/1309815988
Not working: https://github.com/pact-foundation/pact_broker-client/actions/runs/1424091217
On Ruby 2.2,10 the approvals gem has stopped installing (neither ruby 2.2 (HA!) nor the approvals gem has recently been updated).
On Ruby 3.0.2, json-2.6.1 has stopped installing. I'm at a complete loss! The gem_make.out files do not seem to have anything helpful in them. Would appreciate any pointers.
I can only think something on the ubuntu-latest image has changed.
srividya.ece
2021-12-07 19:42
Hi @bethskurrie I am using ruby pact-mock-service standalone. I am setting up interactions using curl -X POST -H "X-Pact-Mock-Service: true" -d script/consumer-interaction.json localhost:1234/interactions . My question here is I have consumer-interaction.json something like
``` {
"request": { "path": "/image/v1", "method": "GET" },
"response": {
"status": 200,
"body": "img_news.jpg",
"headers": {
"Content-Type": "image/jpeg"
}
}```
I am doing it using postman, when I try to verify the interaction i get a success code 200 but no image displayed
Could someone please tell how can I send images (binary data ) in JSON body using postman, to get a response with image when tested against mock?
mike.geeves064
2021-12-07 21:06
I'm not familiar with the pact-mock-service, but my understanding was you would use it if you had a provider in a language that wasn't supported for Pact mocks? You definitely can Pack mock with Ruby, what are you trying to do exactly / reason for using the mock service?
srividya.ece
2021-12-08 07:17
The exact use case is we need to post all interactions to mock server stand alone. There are other teams who use this mock server and perform their consumer tests from their side. I know this is a bit wired usecases. But Could you please tell me if you have an idea about how can I get binary data (ex:image) ?
mike.geeves064
2021-12-08 10:59
Sorry but I still don't understand the use case, saying "the use case is we use it" isn't really a use case. I can't help with the pact-mock-service specifically. If you're trying to get the mock service to return a specific image for a test that doesn't seem to make sense, to me at least, as a contact, vs e.g. the response did be image/png and have a body for example
bethskurrie
2021-12-08 22:10
Can you please describe step by step exactly what you're doing, and exactly what you expect, and waht you're getting.
bethskurrie
2021-12-08 22:10
Pact Ruby doesn't support binary data very well, if that's what you're asking.
srividya.ece
2021-12-09 10:55
Yes exactly i want to know if pact ruby mock server supports binary data?
bethskurrie
2021-12-09 21:34
There is basic support for multi-part forms, but you seem to be mocking JSON.
tom.kelly
2022-01-10 15:10
Hey, not sure if this is the right place to ask but does anyone know how often releases are? We're just waiting on a pact-cli docker image release with https://github.com/pact-foundation/pact-ruby-cli/pull/41 included so our security scans stop failing
diva.pant1
2022-01-12 22:39
Hi our company currently uses vcr testing, and we would like to move to pact testing. I am still new to this and trying to understand how to go about it. The general docs doesn't help me at this point.
So we have these spec files with vcr tests, since I do not have to start from scratch, so to implement pact testing we to just make changes in the rspecs right?
matt.fellows
2022-01-15 02:59
Pact is a unit testing framework for one, so it would usually be written in Ruby code (e.g. as rspec tests)
matt.fellows
2022-01-15 03:00
If the docs aren?t helpful, perhaps you could explain what?s not helpful about them? Is it the concept?
matt.fellows
2022-01-15 03:00
One option could be to run through some of these tutorials, you can run them in a browser to simplify things: https://docs.pactflow.io/docs/tutorials
matt.fellows
2022-01-15 03:00
The Pact Ruby docs seem fairly clear about what code needs to be written: https://github.com/pact-foundation/pact-ruby
matt.fellows
2022-01-15 03:01
do note that as it is a unit testing tool, you will need access to the code under test and be comfortable writing unit tests
matt.fellows
2022-01-15 03:02
They are usually automatic on merging, but perhaps something went wrong here. Worth following up next week when Beth returns from annual leave
matt.fellows
2022-01-15 03:02
It?s a busy time of year with leave etc., so please bare with us now that we?re all returning to work and having to empty piles of emails :stuck_out_tongue:
matt.fellows
2022-01-15 03:03
> They are usually automatic on merging, but perhaps something went wrong here. Worth following up next week when Beth returns from annual leave
Sorry, it?s manually released. I thought this was docker but it?s the CLI tools.
matt.fellows
2022-01-15 20:59
We don?t have templates for the 12+ languages at the moment, just for the most popular configurations
diva.pant1
2022-01-15 21:03
okay so we have written tests in ruby, already published on pact-broker is it possible for us/or should we move to pactflow?
matt.fellows
2022-01-15 21:05
Yes absolutely, if you?re already using the Pact Broker, Pactflow is API compatible with it
matt.fellows
2022-01-15 21:06
The main difference is you would authenticate using API tokens, and not basic auth (or none, as the case may be)
gueorgui
2022-01-17 16:52
Hi, I?m building a proof of concept for pact/pactflow for our company. We have a few consumers (two react SPAs, two mobile apps), and one provider, which is a ruby on rails API. Most of the API requires auth (an `Authorization: Bearer xxx` header).
I?ve looked at the authorization docs and links here: https://docs.pact.io/faq/#how-do-i-test-oauth-or-other-security-headers and I?m still at a loss of how to proceed.
Is it still the best practice to manipulate the request from the consumer to automatically insert a generated header, despite the fact that it undermines confidence in the contracs?
Is it not possible to do something similar to what?s done with the Devise RSpec helpers, where you generate a new user (from a factory for example) and sign it in before performing the requests?
diva.pant1
2022-01-20 13:50
Hey people, not only new to pact testing but to ruby as well, but my company uses Ruby
Which file to make these config changes to ?
https://docs.pact.io/implementation_guides/ruby/gotchas
diva.pant1
2022-01-24 10:25
@bethskurrie could you tell me to which file should I make these changes, rspec or pact_helper?
diva.pant1
2022-01-24 13:08
Here instead of local host should do we have to put our pactflow url? `AnimalServiceClient.base_uri 'localhost:1234'`
https://docs.pact.io/implementation_guides/ruby/README
diva.pant1
2022-02-04 12:27
I am getting this error, after running rake spec
```NameError:
undefined local variable or method `application_service' for #<RSpec::ExampleGroups::NxtClientsApplicationServiceApplicationCreator_2::Call::WithRequiredParams:0x000055ce80e69b60>```
here `application_service`is my object to run the mock server
```require 'pact/consumer/rspec'
Pact.service_consumer "Nxt" do
has_pact_with "Application Service" do
mock_service :application_service do
port 1234
end
end
end```
What could be the problem?
diva.pant1
2022-02-04 13:05
When we run our spec files, the contract is saved in `/spec/pacts`, but we have to create the directory right, and how do we configure that the pacts are stored there?
diva.pant1
2022-02-11 13:38
Here `require pact/consumer/rspec` is a directory structure, or it should be configured in rake file. Is there specific document with the dependencies and keywords we use for Pact, so that I can go through it.
Here for eg, I don't understand what `require pact/consumer/rspec`is doing
diva.pant1
2022-02-11 14:14
I mean I know what require does, but I don't have a directory structure `pact/consumer/rspec`as suggeted in the readme
https://docs.pact.io/implementation_guides/ruby/readme/
matt.fellows
2022-02-16 10:40
This was pretty easy to find: https://github.com/pact-foundation/pact-ruby/blob/master/documentation/configuration.md#pact_dir
matt.fellows
2022-02-16 10:41
Also, if you go to http://docs.pact.io and search ?pact ruby configuration? or ?pact ruby dir? this is the top article
diva.pant1
2022-02-17 01:17
Yes thanks, I did see it, but what I am confused about is do we have to explicitly put these configuration in `pact_helper` file or somewhere else
matt.fellows
2022-02-17 02:11
I think this is more about how you structure your rspec tests. You can put it wherever makes sense. At Pactflow, we put it in a `pact_helper` file
diva.pant1
2022-02-21 20:15
no, I am confused about the configuration part as well. Do we explicitly have to code so that the pact files goes into `spec/pacts`?
diva.pant1
2022-02-21 20:22
Also do I need this step, when I am only converting VCR test to Pact test?
diva.pant1
2022-02-21 21:27
Do we have to explicitly specify the version of pact? If yes then in which file and how? Or just installing pact gem is enough?
bethskurrie
2022-02-21 21:29
You specify the *consumer version* (ideally the git sha) when you publish the pact. The Pact Broker versions the content for you.
diva.pant1
2022-02-21 21:30
Um sorry I meant to ask specification https://github.com/pact-foundation/pact-specification
diva.pant1
2022-02-21 21:33
Okay but it is not necessary to add right? and if yes then in which file do we add this specification.
bethskurrie
2022-02-21 21:33
it will probably be in the consumer definition dsl, but it's been a while since I looked.
diva.pant1
2022-02-21 21:38
and for storing pact files do we have explicitly configure as well like this, or not required?
```Pact.service_consumer "Nxt_Clients" do
has_pact_with "Application Service" do
mock_service :application_service do
port 1234
pact_specification_version '2'
end
end
end
Pact.configure do | config |
config.pact_dir = './spec/pacts'
end```
diva.pant1
2022-02-21 21:43
What is meant when its said that the pact files are automatically stored in `spec/pacts`
diva.pant1
2022-02-21 21:45
And do we require this configuration to be coded somewhere in the ruby project?
```Pact.configure do | config |
config.pact_dir = './spec/pacts'
end```
bethskurrie
2022-02-21 21:46
Is there a developer you can pair with in your organisation? Pact is a developer tool, not a tester one, so it requires a lot of general developer knowledge.
bethskurrie
2022-02-21 21:47
I think there may be some misunderstanding in your organisation about the skillset required to use Pact.
diva.pant1
2022-02-21 21:51
Okay, but my point of asking this question was , I am running my unit tests, and the error I am getting is application_service( which is my object here to access the mock server) is not defined, and I think maybe its a configuration issue
```Pact.service_consumer "Nxt_Clients" do
has_pact_with "Application Service" do
mock_service :application_service do
port 1234
pact_specification_version '2'
end
end
end```
bethskurrie
2022-02-21 22:31
unless you can share your entire codebase, I don't know if I can help you.
bethskurrie
2022-02-21 22:33
here is a working example https://github.com/pact-foundation/pact-ruby/tree/master/example/zoo-app
diva.pant1
2022-02-23 19:01
How do we publish ruby pacts to Pactflow, using this command?
``` pact-broker publish PACT_DIRS_OR_FILES ... -a, --consumer-app-version=CONSUMER_APP_VERSION -b, --broker-base-url=BROKER_BASE_URL```
https://github.com/pact-foundation/pact_broker-client
Is that correct?
jason.wang
2022-03-09 22:00
Hi! I have a question with respect to using pact-message-ruby. Is it possible to have both `Pact.message_provider` and `Pact.service_provider` in the same `pact_helper.rb`? When trying to do so, whichever one comes first seems to get overriden by the second resulting in failures. If it's not possible, is there a known workaround? Maybe separate rake tasks, one for HTTP and one for messages?
cc @victor.lau
victor.lau
2022-03-09 22:27
https://github.com/pact-foundation/pact-ruby/issues/260. Issue linked here for more in-depth description
jason.wang
2022-03-10 21:41
Is there a pattern to not include provider states if all provider states are `no_op`?
```Pact.provider_states_for 'My Service' do
provider_state 'some state that needs no setup' do
no_op
end
provider_state 'some other state that needs no setup' do
no_op
end
end```
jason.wang
2022-03-10 22:01
The warning that provider states are missing is still needed to inform the provider to add them if they are needed. But if there's some way within `pact_helper` to explicitly indicate that no setup/teardown is necessary for any provider states for the specific consumer, that could reduce complexity a little...
bethskurrie
2022-03-15 02:03
You can raise it in the pact-ruby repository, or in http://pact.canny.io @jason.wang
diva.pant1
2022-03-16 10:35
I keep running into this error after running my spec. Could anyone point me in the right direction, why I am getting this error
rachelb
2022-03-23 10:33
Hi :wave:,
We're just getting started using http://pact.io for api contracts between our frontend platform and ruby monolith. I'm having trouble as the provider state `set_up` method is not being called prior to the interaction being verified. Can anyone help? Here are some code snippets:
```from the contract:
"interactions": [
{
"description": "a request to GET cards",
"providerState": "user has cards", ...
from the provider states files:
Pact.provider_states_for "bloomandwild-frontend" do
provider_state "user has cards" do
# code reaches here
set_up do
# code doesn't reach here```
apart from that, the verification is working - ie I can successful verify an interaction that requires no set up.
Any help or advice appreciated TIA
rachelb
2022-03-23 22:58
The test fails as the expected user has not been set up in the database
``` 1) Verifying a pact between bloomandwild-frontend and v1-cards Given user has cards a request to GET cards with GET /api/v1/cards?locale=en&shipping_country_id=1 returns a response which has status code 200
Failure/Error: expect(response_status).to eql expected_response_status
expected: 200
got: 302```
Basically, the auth fails as user doesn't exist so response is a redirect.
bethskurrie
2022-03-23 22:59
is there any output to say that the provider state definition wasn't found?
rachelb
2022-03-23 22:59
No. See my comments in the code. It finds the provider state but never seems to execute the set_up method
bethskurrie
2022-03-23 23:02
there's nothing obviously wrong in the snippet you've shared :thinking_face:
rachelb
2022-03-23 23:05
Here are all the files (user data is made up)
```# pack_helper.rb
require "pact/provider/rspec"
require "pry"
require "rails_helper"
require_relative "provider_states_for_bloomandwild_frontend.rb"
Pact.service_provider "v1-cards" do
honours_pact_with "bloomandwild-frontend" do
pact_uri "spec/pacts/bloomandwild-frontend-v1-cards.json"
end
end
# provider_states_for_bloomandwild_frontend.rb
Pact.provider_states_for "bloomandwild-frontend" do
provider_state "user has cards" do
set_up do
user = User.create!(id: 6390154, email: "")
user.credit_cards.create!(
"brand": "Visa",
"created_at": "2022-03-21T09:59:57.543+00:00",
"exp_month": 2,
"exp_year": 2024,
"id": 10121358,
"kind": "card",
"last4": "4242",
"temporary": false,
"token": "card_1Kfi1oKoz4lNOAHNvfFpz1ec",
"updated_at": "2022-03-21T09:59:57.581+00:00",
)
UserToken.create!(user: user, kind: :login, token: "BYsijJUFrmzU-pTzhaZM")
end
tear_down do
no_op
# clean up objects
end
end
end
# the contract
{
"consumer": {
"name": "bloomandwild-frontend"
},
"provider": {
"name": "v1-cards"
},
"interactions": [
{
"description": "a request to GET cards",
"providerState": "user has cards",
"request": {
"method": "GET",
"path": "/api/v1/cards",
"query": "locale=en&shipping_country_id=1",
"headers": {
"Accept": "application/json, text/plain, */*",
"x-angular-version": "6",
"x-fingerprint": "eaa08c06-ada8-4717-831d-e480d2dd12f3",
"x-fingerprint-old": "",
"x-user-email": "",
"x-user-token": "BYsijJUFrmzU-pTzhaZM"
},
"matchingRules": {
"$.headers.x-fingerprint": {
"match": "type"
},
"$.headers.x-user-email": {
"match": "type"
},
"$.headers.x-user-token": {
"match": "type"
}
}
},
"response": {
"status": 200,
"headers": {
},
"body": {
"cards": [
{
"brand": "Visa",
"created_at": "2022-03-21T09:59:57.543+00:00",
"exp_month": 2,
"exp_year": 2024,
"id": 10121358,
"kind": "card",
"last4": "4242",
"name": "Visa ending 4242 (exp. 2/24)",
"temporary": false,
"token": "card_1Kfi1oKoz4lNOAHNvfFpz1ec",
"updated_at": "2022-03-21T09:59:57.581+00:00",
"user_id": 6390154
}
]
},
"matchingRules": {
"$.body.cards": {
"min": 1
},
"$.body.cards[*].*": {
"match": "type"
},
"$.body.cards[*]": {
"match": "type"
}
}
}
}
],
"metadata": {
"pactSpecification": {
"version": "3.0.0"
}
}
}```
rachelb
2022-03-23 23:08
Yeah, that is how I found out no data is being created and that it never seems to execute set_up
rachelb
2022-03-23 23:09
But, as I said above, for an interaction which requires no set up, I can verify it. So everything seems to be working except for the set up.
rachelb
2022-03-23 23:22
Yup, I have double checked but I guess something, somewhere is awry. I just can't see what :shrug:
rachelb
2022-03-23 23:22
But now I know which part of the the gem to look in, I can carry on debugging. Thanks for helping.
rachelb
2022-03-23 23:25
The state is missing from the `interaction`
interaction
{
:description => "a request to GET cards",
:provider_states => [],
:request => {
:method => "GET",
rachelb
2022-03-23 23:26
Hmm why multiple provider states? In the contract, there is only one but here in the gem it has an array.
rachelb
2022-03-23 23:31
Is there some other syntax? I tried changing the contract to
``` "providerStates": ["user has cards"],```
and now the interaction has this
``` :description => "a request to GET cards",
:provider_states => [
[0] {
"name" => nil,
"params" => nil
}
],```
so I wondering how to add my one state in an array format?
bethskurrie
2022-03-23 23:34
that' says it's a v3 pact specification pact, but the provider state format is in v2 format.
bethskurrie
2022-03-23 23:42
I think the problem is, there are two parsers, and it uses the parser based on the pact specification number.
bethskurrie
2022-03-23 23:43
your pact says it's v3, so the v3 parser is looking for an array at `providerStates`
bethskurrie
2022-03-23 23:44
if it's the implementation backed by the ruby shared codebase, then it does not support v3.
rachelb
2022-03-23 23:45
Okay. FE dev did ask me which version to use and I said latest ie v3 is fine.
I think I have lots more to go on now. Hopefully we can get it sorted.
Thanks so much for your help @bethskurrie :pray:
rachelb
2022-03-25 16:08
:wave: Hi @bethskurrie, me again
I'm having trouble with authenticating the user in the pact. Something to do with the Warden middleware (I think). I found your gist https://gist.github.com/bethesque/203e9d2ec08f4a40d2df but am not sure what exactly I would put in `RealApp` Apparently we don't normally run a real server for our rspec tests (except for system/capybara ones).
When I try to authenticate a user i get this
```# RuntimeError: Invalid strategy current_user
# from /Users/rachelbingham/.rbenv/versions/2.7.4/lib/ruby/gems/2.7.0/gems/warden-1.2.9/lib/warden/proxy.rb:385:in `_fetch_strategy'```
Just wondering if you have any insight on how I might configure this so I can authenticate requests realistically?
bethskurrie
2022-03-28 02:42
The example in https://gist.github.com/bethesque/203e9d2ec08f4a40d2df isn't "running a real app" - it's still just a rack app.
bethskurrie
2022-03-28 02:44
otherwise, you need to set up real users in your database for each verification, and make sure that the auth creds you're passing in to each request are valid, and that can be a pain to manage.
bethskurrie
2022-03-28 02:44
typically, I turn off auth for pact tests. that can usually be covered elsewhere in the testing pyramid.
bethskurrie
2022-03-28 02:45
ie. if you have integration tests that go through the UI, the auth has to be covered there anyway.
alejandro.velez
2022-04-07 17:11
a little confused around `ENV['CI_BUILD_URL']` in this example in the docs https://docs.pact.io/implementation_guides/ruby/publishing_pacts is this supposed to be the Pact URI of the generated pact? In buildkite for example, this ENV will be auto populated with the url of the job, but the provider rake task needs the Pact URI if I?m not mistaken.
alejandro.velez
2022-04-07 17:50
ah never mind! I think I want `PACT_URL` not `BUILD_URL` :sweat_smile:
jason.wang
2022-04-07 19:25
Hey team, I was wondering what the purpose of the assertion in the consumer spec if we're mocking the provider service. Example: https://github.com/pact-foundation/pact-ruby/blob/master/example/zoo-app/spec/service_providers/animal_service_client_spec.rb#L28
bethskurrie
2022-04-07 21:46
@jason.wang the consumer side of a pact spec checks 2 things. 1, that the consumer code sends the expected request and 2. That it does the right thing with the response.
bethskurrie
2022-04-07 21:48
Eg does it parse the body correctly and return a domain object. Should it raise an exception if it gets a 500. Should it return null for a 404.
bethskurrie
2022-04-07 21:49
To check these, you should use your normal testing framework expectations.
yeseniavega411
2022-05-03 19:03
Hello,
with Pact v2, can we use the matchers in the unit test assertions?
yousafn
2022-05-03 19:34
Yes many matchers are supported in V2 and matchers are highly recommended,
You can see the pact v2 specification for more detail
https://github.com/pact-foundation/pact-specification/tree/version-2
yeseniavega411
2022-05-03 19:38
Thank you very much! I got a little confused and just wanted to make sure
gemhar
2022-05-10 15:31
Is there a way to share data between some of provider states(not all), by data I mean common response hash in the form of variables or constants
thomas.koppensteiner
2022-06-01 08:39
Hello,
the https://github.com/pact-foundation/pact-ruby#current-pact-specification-version states the currently version `2` of the pact specification is supported by `pact-ruby`.
Are any GitHub issues or Milestones to track the progress towards the support of version `3` or `4` of the specification?
yousafn
2022-06-01 11:10
Hey V4 spec is available in JVM and Rust at the moment,
taken from https://pactflow.io/blog/changelog-oss-may-2022/
> V4 Pact Specification
>
> Pact specification V4 is https://github.com/pact-foundation/pact-specification/tree/version-4! We worked hard on listening to the community, after the release of v3, 5 years ago. We consolidation many of the requests people made about things that haven't worked quite properly. One of the biggest changes is consolidation the file format to allow for HTTP and message interactions with a single file.
> ? :video_camera: See an AMA from 2021 where Ron Holshausen took us through "https://www.youtube.com/watch?v=u7LzZ6Fm1Ok?"
> ? :orange_book: Read the V4 spec RFC for a full list of changes: https://github.com/pact-foundation/pact-specification/issues/71
> ? :rocket: Implementations in https://github.com/pact-foundation/pact-reference/blob/master/rust/README.md core and https://github.com/pact-foundation/pact-jvm#supported-jdk-and-specification-versions has been completed
> ? :earth_africa: All our Pact specifications are open-source and you can see them all https://github.com/pact-foundation/pact-specification#index
> Plugins, Protobufs and gRPC (oh my!)
I'm not sure if we have tracking tickets for the v3/v4 in each language, but I hope to update and reboot our feature table soon https://docs.pact.io/roadmap/feature_support and get some tickets tracking work, if we don't already have them either in each repo or on our canny board https://pact.canny.io/ where you can submit a feature request, and people can vote on it
msparks
2022-06-01 15:21
hi there!
I have a question about the pact specification being used in the latest gem.
what does https://github.com/pact-foundation/pact-ruby#current-pact-specification-version mean for multiple provider states?
I am able to get my tests to enter the v3 interaction parser, when *attempting* multiple provider states, but pact complains with `WARN: Currently only 1 provider state is supported. Ignoring`
additionally, despite that warning, both provider states do _seem_ to run.
am I missing something obvious?
bethskurrie
2022-06-01 23:13
@msparks I suspect that I updated the behaviour but didn?t update the message.
bethskurrie
2022-06-01 23:14
I honestly don?t know what the plan is for porting Ruby to the ffi. I don?t have the headspace to pick it up. We need another Ruby maintainer.
msparks
2022-06-02 14:44
that was my guess, since I was seeing the code for both states run, I just didn?t understand if there was some inference I was missing with the uneven support of writing pacts in v2 and verifying in v3.
msparks
2022-06-02 14:46
I saw also that the metadata for multiple provider states seems to inject the first as `providerState` is that also expected?
msparks
2022-06-03 13:30
the, I guess, rspec object(?) that contains interaction, the request?
this:
```{:block=>
#<Proc:0x00005592bd328138 /var/lib/bundle/ruby/2.7.0/gems/pact-1.62.0/lib/pact/provider/rspec.rb:170>,
:description_args=>["has status code 201"],
:description=>"has status code 201",
:full_description=>
"Verifying a pact between patient-ui and onelife Given pediatric patient has relationship with member administrator member administrator for pediatric beneficiaries signs membership_tos with POST /api/v2/patient/administrator/beneficiaries/3598076/tos_signatures.json returns a response which has status code 201",
:described_class=>nil,
:file_path=>
"/var/lib/bundle/ruby/2.7.0/gems/pact-1.62.0/lib/pact/provider/rspec.rb",
:line_number=>170,
:location=>
"/var/lib/bundle/ruby/2.7.0/gems/pact-1.62.0/lib/pact/provider/rspec.rb:170",
:absolute_file_path=>
"/var/lib/bundle/ruby/2.7.0/gems/pact-1.62.0/lib/pact/provider/rspec.rb",
:rerun_file_path=>
"/var/lib/bundle/ruby/2.7.0/gems/pact-1.62.0/lib/pact/provider/rspec.rb",
:scoped_id=>"1:1:1:1:1:1",
:pactfile_uri=>
#<Pact::Provider::PactURI:0x00005592bdfeb5c8
@metadata={},
@options={:token=>nil},
@uri="spec/service_consumers/patient-ui-onelife.json">,
:pact_criteria=>
{:description=>
/member administrator for pediatric beneficiaries signs membership_tos/,
:provider_state=>
/pediatric patient has relationship with member administrator/},```
bethskurrie
2022-06-08 03:57
yes, to be backwards compatible, it picks the first state as the single provider state, but the interaction domain object also has an array of provider state objects on it.
thomas.koppensteiner
2022-06-08 11:39
FYI I created the following to Github issues to start tracking the progress:
? https://github.com/pact-foundation/pact-ruby/issues/266
? https://github.com/pact-foundation/pact-ruby/issues/267
msparks
2022-06-08 14:28
as I saw! multiple provider states do _seem_ to be working for me, at least in the very tight scenarios I am working with. but other v3 features, like generators, don?t seem to be. unless I?ve gotten something wrong there, which is entirely possible.
jean.paiva42
2022-06-14 12:33
Hey I am very new to pact and sorry for just be dropping messages like this here but I?ve been trying to use: https://www.rubydoc.info/gems/pact-provider-verifier/1.11.0#setting-a-custom-authentication-header
and while I do get to hit my endpoint and it seems like the expectations are actually running it seems like my provider is returning a body in a format different from what I am expecting, even though the content is what I intended?
I am expecting a json on the contract response but it seems like I am getting the provider response with `\` on each time a quote appear. Is there a way to deal with a situation like this, maybe treat the response before comparing them?
What I am expecting (example):
`{"foo":"bar"}`
what I am getting:
`{\"foo\":\"bar\"}`
Is this something I can fix with the pact-provider-verifier or I would need to fix with my provider?
bethskurrie
2022-06-15 00:47
If the returned response doesn?t have a Content-Type of application/json, the matcher won?t know to parse the body into JSON, and will treat it as a string.
jean.paiva42
2022-06-15 14:46
Interesting, my response is being returned with `"Content-Type": "application/octetstream"` ?. Is there a workaround I can do with pact-verifier or the way to go would be add the `application/json` on my response?
marti92
2022-06-15 18:35
Hello!
Is it possible to run pact verify but as part of an Rspec test instead of running the rake task?
bethskurrie
2022-06-15 21:55
The returned content type seems wrong to me. I think you have detected a genuine bug in the provider.
bethskurrie
2022-06-16 00:44
Possibly, but it would be a custom job, and you?d need to know what you were doing.
marti92
2022-06-16 16:10
I sounds useful to be able to use a Pact API to verify pacts, pass options, and not just the pact helper
marti92
2022-06-16 16:10
I was able to get it working with the rake task in the end, thanks for your response!
marti92
2022-06-16 20:06
Hello! A little late here, but the solution was to change the contract version from 2 to 3? Like
```"metadata": {
"pactSpecification": {
"version": "3.0.0"
}
}```
marti92
2022-06-16 21:07
Fixed it by upgrading the JS client to beta, but still not getting it to call `set_up`
marti92
2022-06-22 17:38
Are MatchersV3, from the JS library, supported when validating pacts via Ruby?
bethskurrie
2022-06-23 00:57
Unfortunately not yet. This is a big gap in the implementation, and we are very aware that we need to get this implemented.
marti92
2022-06-23 17:05
I somehow made them work? I only get a warning when validating which says
```WARN: Ignoring unsupported combine AND for path....```
but the validation itself works
massimiliano.devivo
2022-08-02 12:14
hello everyone :wave:
I am getting more into pact these days
and I might have a question for https://github.com/pact-foundation/pact-mock_service :thread:
massimiliano.devivo
2022-08-02 12:14
I was trying a test script on the lines of:
```request_headers = { "Content-Type" => "application/x-www-form-urlencoded" }
request_body = URI.encode_www_form(
[
...
[
"device_id",
Pact.term(
generate: "3387FE91-453B-4237-B986-17F4F0DC0E13",
matcher: /^[a-zA-Z0-9]{8}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{12}$/
)
]
...
]
)
interaction_mock_domain = "http://127.0.0.1:9292"
interaction_mock_path = "/interactions"
interaction_mock_headers = { "X-Pact-Mock-Service" => true }
interaction_mock_body = {
request: {
method: request_method,
path: request_path,
headers: request_headers,
body: request_body
},
response: {
body: response_body
}
}.to_json
RestClient::Request.execute(
url: interaction_mock_domain + interaction_mock_path,
method: :post,
headers: interaction_mock_headers,
payload: interaction_mock_body
)```
but it seems to me that I must be passing it wrong overall,
because the term finally seems to not be matching (cause is maybe read as string):
```...
* Expected "Pact::Term matcher: /^[a-zA-Z0-9]{8}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{12}$/ generate: \"3387FE91-453B-4237-B986-17F4F0DC0E13\"" but got "3387FE91-453B-4237-B986-17F4F0DC0E13" at $.body.device_id[0]
...```
massimiliano.devivo
2022-08-02 13:53
--------------
I was able to put more thoughts and check more carefully and realised that I was likely doing still a bit of a mess .. :sweat_smile:
reviewing where/what to encode and/or applying ?.to_json? solved the issue, and this example worked for me :slightly_smiling_face:
```request_body = {
..
"device_id" => Pact.term(
generate: "3387FE91-453B-4237-B986-17F4F0DC0E13",
matcher: /^[a-zA-Z0-9]{8}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{12}$/
),
..
}
interaction_mock_body = {
request: {
method: request_method,
path: request_path,
headers: request_headers,
body: request_body
},
response: {
status: 200,
headers: response_headers,
body: response_body
}
}.to_json```
tjones
2022-08-02 23:01
you would only need to invoke the mock service directly if you're doing something really custom
bethskurrie
2022-08-02 23:15
@massimiliano.devivo can you explain more about the underlying problem you?re trying to solve? As Tim says, it?s not normal to need to interact directly with the mock service.
massimiliano.devivo
2022-08-03 07:17
the underlying problem that we wished to try to solve is to experiment if it is possible to replace a fully integrated client tests system
with a set of tests that rely on pact to mock the network
(but preserve the ui interactions part)
we are aware of the recommendations to not use pact with UI
bethskurrie
2022-08-05 00:57
The pact mock was written for a specific purpose, and because of that, it doesn?t work very well for other usecases.
massimiliano.devivo
2022-08-05 07:13
we also have some VCR setup,
but we realised that maintenance of the recording + the dataset to be able to save the recording is rather heavy,
hence we wanted to try new tooling which allows more re-usage
massimiliano.devivo
2022-08-05 07:59
it might be true,
but the current possibilities might still be better than other toolings,
do you happen to have other recommendations in mind ? it would be very appreciated :pray: :slightly_smiling_face:
we are evaluating different things
tjones
2022-08-05 08:11
In what I understand of your system, I would lean a bit more into the pact model, and replace your integration tests with contract tests at the API level, and unit/module tests for the UI
tjones
2022-08-05 08:11
By module test I mean what is sometimes called an ?integration test?, but it doesn't leave your service boundary, ie you mock the API
tjones
2022-08-05 08:12
I spoke a bit about this in the pact day last year, I can link you later when I am not on mobile
massimiliano.devivo
2022-08-05 08:13
you found it anyway :smile: ,
thank you for the info, we will peek into it :pray:
msparks
2022-08-11 16:05
random question for anyone who might know the answer: is it possible to match keys in matchingRules in the contract? I know that jsonpath can return keys. but it?s not clear to me if the matching done in pact exactly follows jsonpath.
bethskurrie
2022-08-11 23:24
Not in v2 of the pact spec. if you search in the later versions, you might find a matching rule for keys.
bethskurrie
2022-08-11 23:24
Look on the v3 and v4 branches https://github.com/pact-foundation/pact-specification
bethskurrie
2022-08-11 23:25
Though, having said that, pact ruby doesn?t support v3 yet, and I don?t have a timeline for when it will.
alejandro.velez
2022-08-15 20:01
In providers that have many states, have people extracted out the provider states using lambdas (`->` )? Would it be helpful to add examples of how to do that in here? https://github.com/pact-foundation/pact-ruby/wiki/FAQ I?m willing to help :slightly_smiling_face:
alejandro.velez
2022-08-17 15:15
thanks beth! we use factory bot so wanted to leverage existing factories but ended up following a similar approach with different files for each `provider_states_for` block
alejandro.velez
2022-08-23 18:27
is it possible to configure a service provider with both a `honours_pact_with` block that references local files and `honours_pacts_from_pact_broker` for CI/CD ? or is it preferred to abstract the local verification with a custom task like -> https://docs.pact.io/implementation_guides/ruby/verifying_pacts#using-a-custom-pactverify-task ?
alejandro.velez
2022-08-23 18:29
currently if I try this CI fails looking for those local files, but just wanted to ask in case I?m missing something :slightly_smiling_face:
patrickbadley
2022-09-19 19:42
Crossposting for Ruby/gRPC exposure: https://pact-foundation.slack.com/archives/CEQBDD5U4/p1663616539124209
bethskurrie
2022-09-20 02:03
We need to update the ruby client to use the rust core. The problem is, we don?t have anyone who can pick up that work at the moment.
patrickbadley
2022-09-20 13:22
Thank you, @bethskurrie! Do you have any idea when this might get put on the roadmap to be worked on?
bethskurrie
2022-09-20 20:40
I wish I had an answer. We are hiring a new Ruby dev at SmartBear, and may be able to get it into the SmartBear backlog, but I can't give you any definites, I'm sorry.
Cc: @matt.fellows
matt.fellows
2022-09-21 07:48
There is a non-trivial amount of work to do this, and we don?t currently have any capacity to do this - definitely not in 2022.
We currently prioritise the top 5 languages by usage, and Ruby is not one of them sadly.
Once we?ve done the top 5, the implementation plan should have ironed out most of the bumps, and would probably be a bit easier for community maintainers / contributors to pick up (or indeed us if we have increased our capacity by then).
I?d like to give you a commitment, but I?m afraid at this stage I can?t.
If you _are_ interested in doing the uplift yourself, we will definitely be able to invest in supporting you. Let me know and I can connect you to the right people/places.
patrickbadley
2022-09-21 13:08
Thank you Matt and Beth! I'm not sure we would be able to work on it either.
kellie.persson
2022-09-23 18:13
Hello Everyone :wave: ,
I am testing out PACT w/ pact-swift and a docker image pact-broker. I have been able to publish my pact to the pact broker and now am trying to verify the pact from the provider side of things (ruby).
On the provider side I am setting up my provider states but I am having a tough time getting any gem dependencies to load, i.e. using `circumstance-1.0.0` gem to setup state for me.
Do I need to do any special setup to gain access to these gems inside the provider state files? Thank you for you helpful. Excited to get this POC going.
kellie.persson
2022-09-27 02:15
Hello @bethskurrie
Thank you for the reply. I was able to get past the issue by making use of
```Pact.configure do | config |
config.include ::Circumstance::Helpers
end```
in my `pact_helper.rb` file.
kellie.persson
2022-09-27 16:29
@bethskurrie, I have a followup question. It appears that `let` statements are not allowed in the provider state `set_up` do block
E.g.
```provider_state "default" do
set_up do
load_circumstance :data
end
end```
under the hood, in the `data` circumstance loads another circumstance,
```Circumstance.define(:data) do
load_circumstance :base
end```
in this circumstance :sweat_smile: , the following let statement is used:
```Circumstance.define(:base) do
let(:level) { Level.find(1) }
end```
it is this :arrow_up: `let` statement that seems to be causing the following error when trying to validate.
```Failure/Error: let(:level) { Level.find(1) }
NoMethodError:
undefined method `let' for #<Pact::Provider::State::ProviderState:0x00007f854b79c7c8>```
I am a ruby novice, but I believe let can only be defined in ruby `describe` blocks. Is there any way around this error that I am seeing. I am trying to minimize the setup code by using previously defined circumstances that are used in our other RSpec tests.
Thank you for any help or direction you can provide. Let me know if you need additional information.
bethskurrie
2022-09-28 01:18
`let` is an rspec feature. You can only use plain ruby inside the provider state blocks.
kellie.persson
2022-09-28 01:20
Gotcha. Will look to clean things up on my end to use plain ruby. Thanks so much for your help.
2022-10-24 16:13
This message was deleted.
patrickbadley
2022-10-26 15:04
Hello! I was wondering if there is guidance on best practices around things like contract test code organization?
? Do you recommend putting your consumer contract unit tests in their own folder, or alongside other unit tests in your project?
? Should they have their own spec_helper files?
? Similarly on the provider side: best practices for organizing provider states. For example, should all of the states for a single consumer go in one file? Should states be able to be shared across consumers?
We are just getting off the ground with pact and would like to leverage any learnings from those of you with experience. Thank you in advance!
tjones
2022-10-27 03:21
I'm not a ruby person, but:
> Do you recommend putting your consumer contract unit tests in their own folder, or alongside other unit tests in your project?
I put them wherever I would normally put tests for the code that the consumer contract is calling
> Should they have their own spec_helper files?
I'm not qualified to answer this. I think it would depend on if they uniquely need their own spec_helper.
> best practices for organizing provider states. For example, should all of the states for a single consumer go in one file?
My guideline for this is - how many states are there? I think it's best if files are kept under 250 lines in general, so it would depend on that. In some ecosystems it might be hard to separate out the states.
> Should states be able to be shared across consumers?
Ideally states are about the provider and not about the consumer, so it should be fine to share them. However, there's usually a need for some alignment between provider and consumer teams, since the consumer team are the people writing the state into the contract. If I were adding a consumer to a provider that already had some states, I would review the states to see if there were some that I could re-use.
tjones
2022-10-27 03:22
In some projects, I've completely separated the unit tests and the pact tests - if, for example, running one of them is much more time consuming than the other.
patrickbadley
2022-10-27 13:17
Awesome, thank you @tjones! This is great! If anyone else has their own thoughts, I welcome any more input.
bethskurrie
2022-11-02 05:51
If you can provide a reproducible example @patrickbadley we can have a look at it.
patrickbadley
2022-11-02 13:01
Thank you for the response Beth! I actually just now realized that this was because we were requiring a "test_helper" file that loaded up a number of dependencies that was used by our minitest tests. I created a trimmed down version for our pact tests and no longer see this message. Sorry for the noise on this isolated issue.
patrickbadley
2022-11-02 13:02
I'm going to delete the original post as it is unlikely to provide value to anyone else.
bethskurrie
2022-11-03 02:35
My pact tests just run as part of the normal unit test suite with the normal settings.
bethskurrie
2022-11-03 02:35
The only difference being that WebMock needs to allow connections to localhost.
kellie.persson
2022-11-14 23:51
Hello, I am building out a POC and I using provider states to set up my data. I am trying to setup up my api to work with provider states. I am a bit confused by the direction https://github.com/pact-foundation/pact-provider-verifier#api-with-provider-states.
> you will need to create a dev/test only HTTP endpoint that accepts a JSON document that looks like:
> ```{
> "consumer": "CONSUMER_NAME",
> "state": "PROVIDER_STATE"
> }```
> The following flag is required when running the CLI:
> ? `--provider-states-setup-url` - the full url of the endpoint which sets the active consumer and provider state.
Does my test only endpoint need to access a body in the request that I can pass in `CONSUMER_NAME` and `PROVIDER_STATE` or is the url just supposed to pass up those values as parameters in order to pass along w/ `--provider-states-setup-url` ?
Once I correctly parse the consumer and state, what do I need to do in my controller to properly load the provider state?
Thank you in advance for any and all assistance.
bethskurrie
2022-11-14 23:51
If you?re using pure ruby @kellie.persson then you don?t need to make an endpoint.
kellie.persson
2022-11-14 23:53
i have been able to verify already from the provider side but that?s just because i am testing it out locally
bethskurrie
2022-11-14 23:53
the pact broker is not involved with the replaying part of the interactions.
kellie.persson
2022-11-14 23:54
Okay. I am using pact-swift for my consumer tests (generate the pacts). I would like to be able to verify from the consumer end but for that I do need to access the test api for the provider state
bethskurrie
2022-11-14 23:55
there are two ways to do verification for ruby. If you?re ok using the version 2 of the specification (fewere features) then you can just use pure ruby as per the link I sent above.
bethskurrie
2022-11-14 23:56
If you want to use the verifier CLI (supports a higher version of the specification) then you will need to make an endpoint on your OWN api that can set up the provider states.
bethskurrie
2022-11-14 23:56
I would recommend doing one of the tutorials, as even though the language may be different, you?ll get the basic concpets worked out https://docs.pactflow.io/docs/tutorials
bethskurrie
2022-11-14 23:57
This is a pure ruby provider you can copy from for the provider states https://github.com/pact-foundation/pact-ruby/tree/master/example/animal-service
bethskurrie
2022-11-14 23:58
and if you?re game, this is a real life example https://github.com/pact-foundation/pact_broker/tree/master/spec/service_consumers
kellie.persson
2022-11-14 23:58
Awesome. Thanks so much Beth. I have been able to verify using version 2 of the specification. Wanted to see if we would be able to support the higher version of the specification. Will go through the tutorial! Thanks again.
stevet
2022-11-16 05:57
I am slt from github, I have been working on these pull requests
https://github.com/pact-foundation/pact-ruby/pull/273
https://github.com/pact-foundation/pact-provider-verifier/pull/85
I just wanted to introduce myself and say hello
github2
2022-12-07 20:21
The GitHub user https://github.com/bethesque has signed out.
Use the following command/s to recreate subscriptions
/github subscribe pact-foundation/pact-ruby
/github subscribe pact-foundation/pact-mock_service
/github subscribe pact-foundation/pact-support
maxime.raverdy
2022-12-12 09:47
Hello, team! :smile:
I was looking some to customise the request on the way (by example adding some headers etc..) on the provider tests.
I think the ?easiest? way to do it is to use `request_customizer` from here (https://github.com/pact-foundation/pact-ruby/blob/master/lib/pact/cli/run_pact_verification.rb#L87) but I don?t saw any docs or specs to help me to pass this options from `rake pact:verify`
Do you have any idea how to do it, please?
Thanks a lot :pray:
bethskurrie
2022-12-13 01:08
@maxime.raverdy docs here https://docs.pact.io/implementation_guides/ruby/verifying_pacts#modifying-the-request-with-live-data
noor.hashem
2022-12-13 14:22
Hi team :wave:, are there any ruby examples of how to write pact verification tests ie the provider side tests? I've written some in nest js but first time working with ruby here :smile:
andrew.favaloro
2023-01-12 12:17
Does anyone here know the status of consumers in https://github.com/pact-foundation/pact-message-ruby? I know the readme.md says it?s ?Done but not documented yet?, but the https://docs.pact.io/roadmap/feature_support lists Async pacts as not a feature for ruby
alex.strizhak
2023-01-20 10:26
Hey, thanks @andrew.favaloro for raising it I had the same questions :+1:
Take a look at this repo: https://github.com/pact-foundation/pact-message-demo it might help with Consumer part, I think.
For Consumer side:
https://github.com/pact-foundation/pact-message-demo#how-it-works---consumer-side
However `Fully implement v3 pact specification` in a TODO section, so I?m not sure if it?s works :thinking:
@bethskurrie could you please shed some light on V3 and V4 version, I see 0.11.1 tag version: https://github.com/pact-foundation/pact-message-ruby/releases/tag/v0.11.1 but seems like you are talking about something else.
bethskurrie
2023-01-24 03:14
The demo was written for developers of other pact libraries to build on top of the pact message code in the pact-ruby-standalone.
alex.strizhak
2023-02-02 15:46
Hello guys, is it possible to use https://docs.pact.io/getting_started/how_pact_works#non-http-testing-message-pactfor https://github.com/rails/rails/tree/main/activesupport::https://apidock.com/rails/ActiveSupport/Notifications messages?
It seems like `no`, because ActiveSupport::Notification, as I understand, is using memory for a queue, but not the external requests that are expected by Pact, so probably it can be done only via some other Message Queue, like Kafka, for example:
```ActiveSupport::Notifications.subscribe("my_message") do |payload|
Kafka.produce(queue: 'test-queue', message: payload)
end```
where `Kafka.produce` can be handled by Pact.
However, in this way there is makes sense to remove ActiveSupport::Notifications and keep using only Kafka but it?s different story.
Is anybody was trying to use Pact for ActiveSupport::Notification somehow?
Appreciate any feedback/thought :pray:
bethskurrie
2023-02-02 22:57
@alex.strizhak you can use message pact for anything - just decouple the transport mechanism from the business logic
bethskurrie
2023-02-02 22:58
whatever business logic happens to the message - test that bit, not the active support or kafka bit.
brendanmbliss
2023-02-07 19:01
Hi, I am working on implementing message pact testing for a ruby on rails backend architecture. I have two rails apis communicating via AWS SNS. I have the consumer pact written and that seems to be working correctly - it generates a pact file with the expected message body. On the provider producer side I am running into a snag. I have been following the guides on this repo: https://github.com/AndrewJanuary/pact-ruby-demo and in this one: https://github.com/pact-foundation/pact-message-ruby.
The problem is when I try to setup the provider test and call my code that generates the message, it can't find the class. My conclusion is that pact isn't instantiating my rails app. I can add requires to bring everything in but that gets very long and annoying.
I was reading through the HTTP documentation here: https://docs.pact.io/implementation_guides/ruby/verifying_pacts#using-rake-pactverify and it says that "_Pact loads the app from http://config.ru by default. (it is recommended to let Pact use the http://config.ru if possible, so testing conditions are closest to runtime conditions)"_
Has anyone else run into this problem? should pact message load the app automatically? or does anyone have a repo that uses pact messaging on a rails app?
My setup is essentially the same as this example here: https://github.com/AndrewJanuary/pact-ruby-demo/blob/main/spec/service_consumers/pact_helper.rb albeit I am on a rails app instead of a simple ruby app.
Thanks you for your help!
noor.hashem
2023-02-13 20:51
Hey I have a ruby on rails provider that uses Rspec to run tests and want to write out a provider verification test. Is there an example of it working with Rspec?
zhig.ivan
2023-02-17 09:16
Hi everyone, I am working on CI integration with Jenkins + Guthub and using pact gem. I am stuck upon showing count of successful/failed interactions as i can't find a way to provide output file using *`out`* option mentioned here https://github.com/pact-foundation/pact-ruby/commit/ca19aa844dd81800d206d7af60ab81fc47e07a64 as part of `rake pact:verify` command. The idea was to use the output format similar to rspec with following options `-r rspec_junit_formatter --format RspecJunitFormatter -o tmp/spec-report.xml` . Need some hint please.
brendanmbliss
2023-02-17 17:14
For those interested, I did find a work around. Not sure if it is the best approach. but here is what I did:
`# load the rails app before the test and then we can access our service and call it`
Pact.set_up do
Rack::Builder.parse_file(Pact.configuration.config_ru_path).first
end
brendanmbliss
2023-02-17 17:15
I do this before running the provider message pact verification. So the rails app is loaded into memory and available to call.
noor.hashem
2023-02-22 15:46
Hi there, posting here if anyone can help with a ruby on rails provider getting a 401 unauthorized error. More details in this thread. https://pact-foundation.slack.com/archives/CLS16AVEE/p1676993580488259
bethskurrie
2023-02-23 03:14
The command line verifier supports this, but I?d need to do some digging to see if the same is supported in the native ruby
bethskurrie
2023-02-23 03:22
This is where the `out` and `format` get passed into the underlying pact gem from the pact-provider-verifier https://github.com/pact-foundation/pact-ruby/blob/master/lib/pact/provider/pact_spec_runner.rb#L145
bethskurrie
2023-02-23 03:23
I?d try setting the `rspec_opts` in the verification task https://github.com/pact-foundation/pact-ruby/blob/master/lib/pact/tasks/verification_task.rb#L32
andrew.favaloro
2023-03-01 21:29
I have a question, and I think it mostly comes from me having a stronger Python background than Ruby. I have the following couple of files - but we parallelize our tests, and so I think that each spec file is trying to separately spin up pact servers, so I get errors that the address is already in use. Is there any accepted way to handle this?
andrew.favaloro
2023-03-01 21:35
I tried wrapping the set up in a `shared_context`, but the setup for the shared context gets run each time it?s included. I could just randomize the port every time, but that doesn?t seem like the right move
bethskurrie
2023-03-01 22:06
You?d really need to know what you were doing to get pact running parallel.
bethskurrie
2023-03-01 22:07
You could use this gem to find a free port https://rubygems.org/gems/find_a_port/versions/1.0.1
bethskurrie
2023-03-01 22:08
if you dynamically set a port on the mock server, you can use `<your_service>.mock_service_base_url` to get the base URL to send the requests to.
sugi
2023-03-02 13:33
Hi there, Started trying out bi-directional pactflow for ruby microservices...I'm currently looking to use rswag for writing provider tests...Wondering if there is any other tool that you are using on the provider side?
ivan.mikhalka
2023-03-05 22:57
Hi, everyone. I am using Pact docker CLI `verify` for verifying my provider, Pactflow is a broker. Issue is that I need to pass valid ID to graphql request variable on the fly. This situation described here: https://docs.pact.io/provider/handling_auth#4-modify-the-request-to-use-real-credentials.
So I have such request body: `{ "query": "....", "variables": { "ID": "placeholder" } }` , so I need to replace placeholder with real ID. I know that `--custom-middleware` option stands for this, but I am complete newb in Ruby, could you, please, provide some examples, or appropriate reading for my level, to understand the topic and be able to implement it?
ivan.mikhalka
2023-03-06 02:06
After some reading, such `custom_middleware.rb` seems working:
```class AddCustomAuth < Pact::ProviderVerifier::CustomMiddleware
def initialize app
@app = app
end
def call env
body_string = env['rack.input'].read
new_body_string = body_string.sub("placeholder", "realID")
new_body_io = StringIO.new(new_body_string)
env['rack.input'] = new_body_io
@app.call(env)
end
end```
realID is going to comes from file.
ivan.mikhalka
2023-03-08 01:43
Hi, all, I am using docker cli for verifying provider, and getting such error:
``` 1) Verifying a some - with POST /graphql/ returns a response which has status code 200
Failure/Error: expect(response_status).to eql expected_response_status
expected: 200
got: 500
(compared using eql?)
# /pact/bin/pact:15:in `<top (required)>'
2) Verifying a some - with POST /graphql/ returns a response which has a matching body
Failure/Error: expect(response_body).to match_term expected_response_body, diff_options, example
Encoding::CompatibilityError:
incompatible character encodings: ASCII-8BIT and UTF-8
# /pact/bin/pact:15:in `<top (required)>'```
From provider itself, I am getting something like:
```graphene_django.views.HttpError: POST body sent invalid JSON.```
Could someone help?
ivan.mikhalka
2023-03-08 03:09
I found the issue.
In Ruby custom_middleware file I obtain id from curl query and then insert it to request body.
I was need to remove all whitespaces:
```id = `curl -X POST http://example.com -H "Content-Type:application/json" --data-binary "@${PWD}/request_body.json" | jq .id -r`
# Replace string in request body
body_string = env['rack.input'].read
new_body_string = body_string.sub("placeholder", id.gsub(/\s/, ""))
new_body_io = StringIO.new(new_body_string)
env['rack.input'] = new_body_io
new_body = env['rack.input'].read```
bethskurrie
2023-03-16 21:53
@sugi I?ve been using openapi_first to make sure the OAS that was created outside the repository matches the actual code.
pryan
2023-03-26 23:51
Hello! I have been trying to get a pact test to work with our rails apps. Right now I'm having an issue where the body of my request seems to be getting translated as a string? I'm trying to add a header to specify the content-type but it seems to have no effect on the pact files/test results (see attached).
Am I doing something wrong? I can't seem to find any clear examples/documentation on this. Thanks!
pryan
2023-03-27 20:58
Few more retries and it seems to work. Possible just an issue with generating the new pact file properly.
pryan
2023-03-28 01:47
Hello! I have a question regarding Pact and contract/functional testing!
If I had a consumer client such as the one below, I think writing a test for the sign_up method is pretty straightforward. It it similar to the zoo-app example and makes sense to me.
But how would I approach a method such as sign_in, where there is a series of requests stemming from the same ConsumerExample client method. This would result in a sequence of requests, and I'm just not sure what to make of this (how to test ConsumerExample.sign_in).
Should I be testing at the http_client level? Is the Consumer example containing business logic a red flag? Is there a creative/best practice?
I can't seem to find anything after googling around for a while - hoping I can get a little more intuition here, or maybe a link to some relevant examples/documentation.
Thanks! cc @andy.jenness
pryan
2023-03-28 02:10
Would I just break out these requests as separate tests, trigger then via the http client, and then manipulate the provider states such that each can be ran independently?
tjones
2023-03-28 03:09
In a Pact test, each interaction is independent. So the general answer to ?how do I handle an operation with multiple requests? is to break out the requests in to separate interactions controlled by provider state
tjones
2023-03-28 03:10
However, for login, this usually isn?t practical, because usually your login code is handled by a library that does the oauth dance for you.
tjones
2023-03-28 03:10
if you?re hand rolling the oauth dance, or have some other custom login system, then you might want to do pact tests for each request.
zhig.ivan
2023-03-28 19:07
Thanks for information, but I still can't understand how to pass these options to pact:verify rake command. Should I create a custom rake command for this?
pryan
2023-03-28 19:41
Thanks Timothy - Might have some follow up but this makes sense. Appreciate the response.
haroldrobson11
2023-03-30 13:20
Hello can anyone help me I'm trying to run the standalone pact cli via docker like so in gitlab
```docker run --net=host ###.http://dkr.ecr.eu-west-1.amazonaws.com/base-images/pactfoundation/pact-cli:latest verify $PACT_URL -e PACT_BROKER_BASE_URL=https://pact.dev.###.####.###/ --provider-base-url=http://localhost:8000```
but I keep getting this error when it runs in CI
```Error reading file from https://pact.dev.###.####.###/pacts/provider/battery-api/consumer/fleet/version/"b47b9a1-develop+b47b9a1.SNAPSHOT.runner-5ybevqbc-project-456-concurrent-2"
bad URI(is not URI?): "https://pact.dev.###.####.###/pacts/provider/battery-api/consumer/fleet/version/\"b47b9a1-develop+b47b9a1.SNAPSHOT.runner-5ybevqbc-project-456-concurrent-2\"" /usr/lib/ruby/3.1.0/uri/rfc3986_parser.rb:67:in `split'
/usr/lib/ruby/3.1.0/uri/rfc3986_parser.rb:72:in `parse'
/usr/lib/ruby/3.1.0/uri/common.rb:188:in `parse'```
Really at a loss how to get it to work without the encoding being wrong
haroldrobson11
2023-03-30 13:21
I suspect it's something to do with the double quote marks, this is a valid pact url if the quotes are not escaped
haroldrobson11
2023-03-30 13:24
I think the chain of events is
1. the url is encoded correctly, I send it to Gitlab CI as a variable, the url encoding is changed to real double quote marks (by Gitlab?)
2. bash or some other process escapes the double quote marks
3. pact cli cant find the pact
Has anyone had this use case?
haroldrobson11
2023-03-31 11:35
also later in the the same log session it has a slightly more mangled version of the url
```bundler: failed to load command: /pact/bin/pact (/pact/bin/pact)
/usr/lib/ruby/3.1.0/uri/rfc3986_parser.rb:67:in `split': bad URI(is not URI?): "https://###/pacts/provider/battery-api/consumer/fleet/version/\\"b47b9a1-develop+b47b9a1.SNAPSHOT.runner-5ybevqbc-project-456-concurrent-2\\"" (URI::InvalidURIError)```
haroldrobson11
2023-03-31 16:25
I determined that there shouldn't have been any quote marks in the URL and they were there because of this command
```pact-broker publish pacts --consumer-app-version=\"$(npx absolute-version)\" ```
I just needed to remove the quotation marks here.
pryan
2023-04-01 03:19
Is there any way to use matchers and content-type XML with Pact Ruby? From the documentation it seems like this might only work for JSON?
pryan
2023-04-01 03:21
In this case there is a timestamp I'd like to match too. But perhaps the best way would be to try and stub it out on the provider side?
milda.abromaviciute
2023-04-04 08:26
hello there Pact team, I was wondering if there are plans to update the standalone ruby pact cli to use a new version of ruby? I know traveling ruby isn't something that has been updated for donkey's years, but are there other options to look into? We would love to use it as a universal way to chat to pactflow across teams, independent of the tech stack, however we can't allow the vulnerabilities within that package to travel along the environments unfortunately.
yousafn
2023-04-06 12:50
Hey hey,
It opens up a can of worms :can-of-worms: :slightly_smiling_face:
There seems to be very little movement in any of the ruby packagers, and we've been migrating functionality over to the rust core. (equivalent ruby based distribs have ported over to go/rust over time for easier cross platform distrib)
https://github.com/pact-foundation/pact-ruby-standalone/issues/70#issuecomment-961729859
https://github.com/pact-foundation/pact-ruby-standalone/issues/95#issuecomment-1497398831
some comments regarding the above.
I've been watching a couple of forks, and have a bit of a play yesterday at getting ruby 3.1.2 support for osx/linux & windows, and including aarch64 support for linux/osx, been successful so far, but its a complex tool-chain and issues may arise which are outside of our expertise. - I'm creating CI builds for them, and will provide the fixes upstream but unsure if and when they may be merged.
Couple of questions
1. What part of the pact-ruby-standalone are you interested in using
2. Is there the ability to use it via the docker pact-cli image, which uses ruby 3.x
3. which vulnerabilities have you identified, and how have you found them?
4. What is your teams/companies policy towards open source in terms of vulnerabilities/support, is there support/capacity provided by your teams to help fix the toolchain you use, or is the onus on the library maintainers.
Generally the core pact team is _very_ small, I would imagine its probably smaller than the numbers in your team(s), so although we would love to support all the things, its a delicate balancing act.
We would love to see all the equivalent operations provided by the pact-ruby-standalone, available in rust clis,
we already have several here
https://github.com/pact-foundation/pact-reference/tree/master/rust
I'll look to work with other maintainers this year to map out parity equivalence between the ruby-standalone and rust libs, and provide good first tasks that community members can pick up.
pryan
2023-04-10 21:51
Hello! I'm seeing some behavior between pact and pact-broker. We are deploying pact-broker behind a reverse proxy, and trying to mount the pact-broker in a rails application. Everything seems to work quite well, except when we try to publish contracts from internal services.
We want end users to view the pact-broker UI from outside of the reverse proxy, but the publication/verification tasks are executed internally. For some reason, it seems as though the publication task is picking up the URL from the pact-broker configuration.
Within a provider service, we are specifying `task.pact_broker_base_url = "http://contract-testing/pact"` within the `PactBroker::Client::PublicationTask` in the rake file. When I execute the publication task, it initially uses the correct URI for publication, but at some point it seems to swap that URL out for the `config.base_url = "https://contract-testing.chm.life/pact"` value specified in the pact-broker configuration.
I inserted a break point to try and demonstrate (See attached). cc @andy.jenness
pryan
2023-04-10 21:55
And from the documentation for the config.base_url configuration variable, I think this is the correct setup. But I have tried swapping it out for the internal resource route. This allows the publication event to work, but now the JS on the broker UI is trying to access the incorrect URL!
milda.abromaviciute
2023-04-11 09:57
Hey! thanks very much for the response. From our side:
1. We are using `pact-broke`r and `pactflow`, in the future likely to use `pact-mock-service`
2. Yes I am currently looking into running this as a service as an alternative
3. Can't currently find the exact vulnerability sorry as it was from last week or so and the branch has since been deleted, but it was going through our usual security checks in the pipeline (to preinstall the standalone to our jenkins pods)
4. We're currently weighing all options and thus looking into the dockerised solution you offer instead. Unsure of open source contribution policies but will defo have a look, as I'm keen on working with some rust :eyes: So I'll look out for any good first tasks to pick up in spare time anyway :thumbs:
I think for now will look into that dockerised option (tho I want to run it as a service rather than spin up a pod each time - some workaround required). In the mean time, will keep an eye on that rust repo :slightly_smiling_face:
pryan
2023-04-11 23:03
It looks like this is the expected behavior. X-posted here with a little more context. https://pact-foundation.slack.com/archives/C9VPNUJR2/p1681253434689569
paul.caplan
2023-04-18 14:59
Hello! My organization is looking at adopting contract testing. We have a very large existing suite of integration tests that use VCR. Has anyone actually succesfully converted VCR cassettes into consumer contracts, and/or built any utility to do so?
https://docs.pactflow.io/docs/bi-directional-contract-testing/contracts/pact/#converting-mocks-into-a-pact-compatible-format
> Tools like https://github.com/vcr/vcr and https://netflix.github.io/pollyjs can record the actualy calls your application makes and story them as a fixture file for future use. This makes your tests reliable, but introduces the possibility of drift. Converting this mocks into a pact file reduces that possibility.
yousafn
2023-04-18 21:14
Heylo Rubians! (Does Ruby programmers have a pluralism)
I've been playing with the travelling ruby build system for a while and pleased to have raised a PR against it which brings support for Ruby 3.1.2 (and future versions), and support for ARM64 architecture.
https://github.com/phusion/traveling-ruby/pull/132
I've been testing out consuming these into the pact-ruby-standalone project. Would love to find any willing volunteers who
a) have used the travelling ruby packaging system to try it out
b) anyone with arm machines who want to be willing volunteers
squarism
2023-04-18 22:49
You'd have to write the contract tests. VCR is similar, you could probably meta-program it but I wouldn't. I would just do one or two and see how it goes.
I tried Polly a long time ago (because I missed VCR) and didn't have a great time.
Also, VCR is more like a magic mock. Pact is sort of a different type of testing tool. A typical CI flow (to me would be something like this)
? unit tests (which ideally would not need VCR)
? integration tests (which could use VCR for conveniences)
? contract tests (which are trying to enforce many-service interactions)
Theses are different levels and styles usually using different libraries.
? unit tests (rspec)
? integration tests (maybe rspec's request specs, but now you need bigger libraries)
? contract tests (pact)
I know some Ruby apps are all mixed up (take Rails) where there are not clean lines between the things. But you'll probably find yourself over time on a project not running the end-to-end tests that much and now you've filtered the tests for productivity. And you'd do the same in a CI pipeline where each test step is fancier and fancier.
Essentially, the testing pyramid.
? It tells you what to write
? It also kind of tells you what order your tests should run in (pact is beyond the peak)
squarism
2023-04-20 18:15
I have been wondering for a few years: why is https://github.com/reevoo/pact-messages not maintained or more mainlined? I think I understand that it's not an official project but is this:
? not the way to do non-HTTP pact
? it's just convenience functions to read a contract file
? there's some other way in the official libraries but not in all languages?
It hasn't been updated in 5 years and I'm not complaining about free OSS labor etc, I'm just wondering if this was a novel project that just hasn't been picked up by anyone or if it has been invalidated by a version bump, other techniques or something else.
squarism
2023-04-20 18:16
I was going to write a blog post a while back to demo and explain pact but I didn't want to use this gem because of the age.
I ended up getting stuck without it and couldn't finish it.
tjones
2023-04-21 08:36
> why is https://github.com/reevoo/pact-messages not maintained or more mainlined?
I think this question is better left on that repo - I don?t think anyone here will know
noor.hashem
2023-05-02 18:26
Hello all! Does anyone know if there is any kind of package for pact ruby on rails specifically? Or any third party packages that help with implementing pact in a ruby on rails provider?
yousafn
2023-05-11 09:37
Ever wondered what the Pact (Ruby) Core looks like?
https://github.com/pact-foundation/devrel/issues/10
There may be more consumers, :elmo_shrug: Feel free to chime in on the issue if you can add anything
lluis.casals
2023-05-15 16:01
Hello! I have a problem regarding the https://github.com/pact-foundation/pact-provider-verifier/ gem, as it seems that is sending a wrong formatted JSON body on the request.
I am executing the next command: `bundle exec pact-provider-verifier hq-placements-client/pacts/hq-placements-client-hq-placements.json --provider hq-placements --provider-base-url ?http://localhost:3000/?
The body in the contract is this one:
```"body": {
"sort_field": "not permitted value"
}```
And I can see that the provider is receiving this body:
```"{\"sort_field\":\"not permitted value\"}"=>nil```
BUT in case I use the `query` instead of `body` in the contract json:
```"query": "sort_field=invalid"```
The request works properly.
Also, mention that I can do the same request using Postman or ?curl? and it works properly:
```curl --location --request GET 'localhost:3000/placements' \
--header 'Content-Type: application/json' \
--data '{
"sort_field": "not permitted value"
}'```
What am I doing wrong?
Thanks a lot for anyone that could help me. :pray:
lluis.casals
2023-05-16 14:49
What do you mean by spec file?
? I am using a contract with this specification:
``` "pactSpecification": {
"version": "2.0.0"
}```
? For the gem: pact-provider-verifier (1.36.1)
yousafn
2023-05-16 14:50
Hey hey,
Yeah that is what I mean, just wanted to know if it was a v2 or v3+ spec (as that ruby verifier supports up to v2 only) just as a first pass for troubleshooting, may be worth raising that as an issue against the repo as well to track. Nothing reaches out to me straight away sorry!
lluis.casals
2023-05-16 15:00
Ah! ok, I will do so.
I did some debugging and I can see that when the query method is a GET (catching-it with Wireshark), the body is translated into query params (what is formerly accepted, since body on a GET request is not the ?correct? way to handle the request).
As fast as I change-it to other methods, the body appears and in a correct way.
rabrosimov
2023-05-26 07:32
Hi Everyone! :slightly_smiling_face:
Does anyone know how to set provider state params on consumer side?
https://docs.pact.io/implementation_guides/ruby/provider_states#provider-state-params
quinton.miller
2023-06-05 16:32
Hey everyone, I found in the pact-reference repo under the ruby folder about the pact_verifier_cli and I was wondering if there are setup instructions for this tool or is it included in the normal pact docker image?
uglyog
2023-06-05 23:20
Docs for that are here: https://github.com/pact-foundation/pact-reference/tree/master/rust/pact_verifier_cli
You can either download the executable you need from https://github.com/pact-foundation/pact-reference/releases/tag/pact_verifier_cli-v0.10.6 or you can use the published docker image https://hub.docker.com/r/pactfoundation/pact-ref-verifier/tags
rabrosimov
2023-06-09 08:07
Hi there. Is it possible to get access to request params from provider states?
For example: on consumer side I send GET/POST params and on provider side I want to see the list of those params and rewrite if needed
tjones
2023-06-09 08:47
No, because this would mean that you couldn?t be sure the contract was appropriately validated
rabrosimov
2023-06-09 09:22
Thanks for your response @tjones.
I'm trying to rewrite on provider state 1 POST param ("memberId") which comes from consumer.
I rewrite it using:
```allow_any_instance_of(ActionController::Parameters).to receive(:[]).with(:variables).and_return({ "memberId" => member.id, "stateCd" => 'CT' })```
but the problem is that I don't want to specify other params like "stateCd" because I want them to come from consumer side.
if I override only "memberId":
```allow_any_instance_of(ActionController::Parameters).to receive(:[]).with(:variables).and_return({ "memberId" => member.id})```
then I'll lost "stateCd"
rabrosimov
2023-06-09 15:28
btw which RAILS_ENV do you use when running `bundle exec rails pact:verify` ? Locally I'm using `development` but on CI not sure which one to use
rabrosimov
2023-06-10 10:27
@tjones because on provider side I already have generated members and their "ids" I don't know from consumer sides but only theirs names. So I send a request from consumer side specifying random member_id and on provider side I fetch specific member_id by name and override GET/POST params "memberId" which came from consumer:
```member = Member.find_by(name: 'user0')
allow_any_instance_of(ActionController::Parameters).to receive(:[]).with(:variables).and_return({ "memberId" => member.id})```
I don'w want to hardcode correct member_id on consumer side. It may work locally on my laptop but there is no guarantee that the same DB id will be on another instance
tjones
2023-06-10 10:53
Aha! Have a look into the provider state variables and fromProviderStat- I?m not sure if it?s supported in Ruby yet, but it?s for this exact use case
rabrosimov
2023-06-10 11:04
@tjones thanks. I will be grateful if you could send me some links because I didn't find how to pass vars into provider states.
tjones
2023-06-10 11:43
They come *from* provider states. I don?t know the Ruby docs, I?m afraid. If it supports pact state v3, you can do it
quinton.miller
2023-06-12 15:41
Thanks for your help. I was able to try out the executable on my project. Is there anything that writing a Provider Verification test gives you that the verifier doesn't? Like a pros and cons of using the verifier vs writing tests?
ivan.mikhalka
2023-07-04 21:16
Hullo,
why I am getting error
```/usr/lib/ruby/3.0.0/net/http.rb:987:in `initialize': Failed to open TCP connection to http://xyz.pactflow.io:443 (getaddrinfo: Try again) (SocketError)```
when trying to publish pact via docker CLI?
Command:
```docker run --rm -w ${PWD} -v ${PWD}:${PWD} --network bridge -e PACT_DO_NOT_TRACK -e PACT_BROKER_BASE_URL \
-e PACT_BROKER_TOKEN pactfoundation/pact-cli:latest pact-broker publish "${PWD}/pactFiles/" --consumer-app-version=1234 --tag=branchName --branch=branchName```
tjones
2023-07-05 04:41
This looks like a docker networking error, rather than a Pact configuration thing
tjones
2023-07-05 07:57
It looks to me like your network is not reaching your docker container correctly
ivan.mikhalka
2023-07-05 08:42
seems so, any URL cannot be accessed. Probably, issue that I am using very slow internet this week
yousafn
2023-07-05 10:41
> I used to use similar command previously on my PC, without any problem
Linux / Windows?
They all use different networking setups for Docker, as Docker is only native on Linux, other platforms are a cludge
ivan.mikhalka
2023-07-10 08:57
So it works on other internet connection, probably, it was some configuration on that router or something similar
hazem
2023-07-13 17:27
:wave::skin-tone-4: - is there any significant difference with the following two commands in the docker image `pactfoundation/pact-cli:latest`:
? publish
? pact-broker publish
yousafn
2023-07-13 17:34
I believe its just an alias, but would need to check source to confirm for definite, are you seeing any discrepancy?
hazem
2023-07-13 17:36
No - I recall switching over to the docker cli for a specific publishing reason. Now I want to reuse more of it, eg can-i-deploy and record-deployment. I have some build stuff wrapped in mage targets for this and just realized there are two different publish options.
yousafn
2023-07-13 17:44
as an fyi
This is cli commands mapped for the docker image https://github.com/pact-foundation/pact-ruby-cli/blob/master/lib/pact/cli.rb
This is where they go for the ref `::PactBroker::Client::CLI::Broker` https://github.com/pact-foundation/pact_broker-client/blob/master/lib/pact_broker/client/cli/pact_commands.rb#L14C19-L14C26
noor.hashem
2023-07-19 17:50
Hellooo! Has anyone used an older version of the pact gem, im using version 1.32.0 and im having some troubles passing in the *include_wip_pacts_since*, *enable_pending*, and *consumer_version_selectors* options. I see this attached error that options method is not found. Even when I passed in any of those options without the *options* method it would tell me "consumer_version_selectors missing method, undefined method.
Am i passing these options in wrong? Because these ones are working fine:
? pact_broker_base_url
? verbose
? publish_verification_results
lluis.casals
2023-07-26 15:01
Hello there!
Please, let me ask if there are any plans to update the Faraday gem version for the pact-provider-verifier gem shortly.
I am asking this because I can see that the dependency for that gem is specified to be https://github.com/pact-foundation/pact-provider-verifier/blob/master/pact-provider-verifier.gemspec#L26C41-L26C61= 0.9.0?, ?<= 2.0?> and I have a dependency in my repository that needs to use at least 2.5.
Thanks a lot for you help!
yousafn
2023-07-26 15:18
I assume we had to pin to lower than 2, because we used travelling-ruby to package cross-platform and that only supported up to ruby 2.4
faraday latest 1.x https://rubygems.org/gems/faraday/versions/1.10.3 shows a require of ruby 2.4
faraday 2.x moved to a require of ruby 2.6
https://rubygems.org/gems/faraday/versions/2.0.0
We?ve recently updated traveling-ruby on a fork, to package Ruby 3.2.2 runtime, so this should be possible now.
Happy to accept PR?s, but will get Beth to review as she is our Ruby expert and may know further detail, but that is my best guess
lluis.casals
2023-07-26 15:21
Ok, thanks a lot! I?ll talk with the team and will see what we want to do.
Thanks again for your answer. :ok_hand:
lluis.casals
2023-07-28 11:53
So we?ve made a ?simple? PR: https://github.com/pact-foundation/pact-provider-verifier/pull/107
I was not able to see any documentation regarding asking to have the GH Actions run, can you help me with this, @yousafn, please? :pray:
Thanks a lot!
yousafn
2023-07-28 13:48
Thank you! I can indeed, its a protection feature to avoid non maintainers to be able to run potentially malicious workflows :+1:
yousafn
2023-08-03 16:31
I can only imagine it doesn?t exist in that old a version of the gem
https://rubygems.org/gems/pact/versions/1.32.0 is from July 2018
yousafn
2023-08-03 16:32
If for whatever reason you need the changes in that version, you could backport them, but would recommended moving to the latest, or check the changelog or git history in pact-ruby to ascertain at which version they were introduced
michelle.he
2023-08-08 21:40
@bethskurrie we are experimenting with pact testing messages. We use kafka, and we want to be able to test the following:
1. MyConsumer sends a message to TopicA
2. MyProvider does some stuff and sends a message to TopicB
It looks like that the https://github.com/pact-foundation/pact-message-ruby.git have some testing capabilities to assert on the message MyProvider sends to TopicB that it has to be certain structure and type. However, we don't see any expectations on the message MyConsumer sends to TopicA that trigs the response from MyProvider. Is my understanding correct?
matt.fellows
2023-08-08 23:49
In Pact message, each part of that sequence should be tested in isolation
matt.fellows
2023-08-08 23:56
i.e.
`MyConsumer` -> `TopicA` : Actually, `MyConsumer` is a ?provider? in this case. It?s producing a message (1)
`MyProvider` -> `TopicB` : Likewise, `MyProvider` is a ?provider? in this case as it?s producing a message (2)
My assumption is that `MyProvider` actually gets the message first from `TopicA` , in which case it?s also a consumer (3)
matt.fellows
2023-08-09 00:41
So actually there would be a few tests here.
You would start with (3) - write the consumer test first. Then implement the provider verification (1).
You would then write the consumer test for the app that reads from `TopicB` (4 - it?s not clear on who is consuming from that topic, is it `MyConsumer` again?)
Once you?ve done this, you would verify that the message sent to `TopicB` is correct (2)
This section of the docs that might help too: https://docs.pact.io/getting_started/how_pact_works#non-http-testing-message-pact
matt.fellows
2023-08-09 00:42
If my assumption about it being essentially an asynchronous request/response message, to further clarify, there are two pairs of tests between the applications. One where `MyConsumer` is the consumer and one where it is the provider.
yousafn
2023-08-09 15:30
:blobwave:
Are you using pact-ruby? Would you like to collab on work to introduce the pact ffi (rust core) into pact-ruby and the other Pact gems?
I?ve already published a couple of gems with the pact_ffi shared lib being loaded into the namespace with ruby?s `ffi` gem.
https://github.com/YOU54F/pact-ruby-ffi
I?ve learned Ruby by example from our codebases and happy to pair,
maxime.raverdy
2023-08-17 15:07
Hello there,
I have a consumer generated by https://github.com/surpher/PactSwift. So all specifications are from V3.
We are a provider on pact-ruby.
So do you know how can I remove the warning like this:
```WARN: Ignoring unsupported combine AND for path```
Thanks a lot :pray:
yousafn
2023-08-17 15:14
At the moment you cant with the pact gem as it only supports up to V2
You can use the pact-reference core (which is built in rust) as a https://docs.pact.io/implementation_guides/cli#native-binary-new or you could alpha test the pact-ffi gem
https://github.com/YOU54F/pact-ruby-ffi
I?ve just updated the pact ffi libraries and the interface in the latest gem?s (0.0.3)
And example of a verifier is here
https://github.com/YOU54F/pact-ruby-ffi/blob/deps/update_libs/spec/pactffi_verifier_spec.rb
yousafn
2023-08-17 15:29
your current pact ruby implementation does not support v3 specification at the moment
maxime.raverdy
2023-08-17 15:33
This ok :slightly_smiling_face: But is there a way to support it? :thinking2:
maxime.raverdy
2023-08-17 15:41
ahah I read it :smile:
The problem is to understand your example here => https://github.com/YOU54F/pact-ruby-ffi/blob/deps/update_libs/spec/pactffi_verifier_spec.rb :thinking2:
Are you running a test like https://github.com/pact-foundation/pact-reference/tree/master/rust/pact_verifier_cli does? (meaning testing through a open url)
Or it is something we can add in our project and test again the test env like `pact-ruby` do? :think_up:
yousafn
2023-08-17 16:06
So the https://github.com/pact-foundation/pact-reference/blob/master/rust/README.md is available via the https://github.com/pact-foundation/pact-reference/tree/master/rust/pact_verifier_cli, or via an https://github.com/pact-foundation/pact-reference/tree/master/rust/pact_ffi#pact-ffi (Foreign function interface).
The current guidance would be to run the verifier CLI against an open URL, to test your provider, in order to support contracts generated in V3 or V4 format.
Pact-ruby does not support V3/V4
Pact-ruby-ffi supports V1-V4 utilising the `ffi` gem?s functionality to load the Pact FFI?s functionality via this shared library, providing a very light-weight ruby-equse wrapper around.
> Or it is something we can add in our project and test again the test env like `pact-ruby` do?
The end goal would be for you to continue to use pact-ruby gem as usual, with it leveraging the pact-ruby-ffi gem to interface with the new pact-core.
The spec linked above, utilises pact-ruby-ffi gem, calling the verifier functions exposed in the FFI. You would start your provider in your ruby tests, rather than requiring it to be started from the outside. This wouldn?t really be exposed to the end user of the pact-ruby interface as its probably
a) a bit too low level
b) a big shift from the existing pact ruby interface, and we want to keep user facing changes to a minimum.
yousafn
2023-08-17 16:07
In the example linked, I am not actually even starting up a provider :slightly_smiling_face: just providing enough args to get the verifier to run, and return a failure due to no pacts to verify
maxime.raverdy
2023-08-17 16:20
hum :thinking2:
And do you have an example of "The end goal would be for you to continue to use pact-ruby gem as usual, with it leveraging the pact-ruby-ffi gem to interface with the new pact-core." ?
yousafn
2023-08-17 16:28
I don?t no, as it doesn?t exist yet.
I have an interactive example here https://killercoda.com/safdotdev/course/safacoda/grpc_plugins_quick_start_ruby
which utilises the pact-ffi gem for the consumer side, and the pact_verifier_cli for the provider side, to test a gRPC server.
the pact_verifier_cli step in step5, would be relevant to your current use case of needing to use verifier_cli on the command line, with a running server
maxime.raverdy
2023-08-18 07:26
Thanks a lot for having take time with this :pray:
I'll check then :bow:
jianbin.lin
2023-08-18 14:50
Hi, do you think that this https://github.com/pact-foundation/pact-support/pull/86/files proposed is something that we can integrate into pact-ruby to make it support v3?
yousafn
2023-08-18 14:54
please read https://pact-foundation.slack.com/archives/C9VHVEDE1/p1692284869342579
the inclusion of the ffi will allow pact ruby to utilise v3 / v4 features.
that pr may still be relevant but may not
jianbin.lin
2023-08-18 14:56
I read it. But ffi appears to be hard to go with as there is no concrete example .
jianbin.lin
2023-08-18 15:00
Or is it possible to have a running example to use `pact-ruby` to verify v3 pacts via ffi?
jianbin.lin
2023-08-18 15:13
To confirm, this binary cannot be integrated with the ruby tests. We need to deploy a http server to use it?
yousafn
2023-08-18 15:14
no, its a standalone binary. you tell it where your running provider is. you could do this externally or you could start the verification process by calling out to an external process in ruby
jianbin.lin
2023-08-18 15:38
Sadly speaking, we find that Pact can help us to reduce the backend breaking changes issues. But the lack of v3 support on pact-ruby will stop us from using it in production project. :weary:
lluis.casals
2023-09-12 10:52
Hello! Please, let me continue on this quite old thread.
Is there any way to have a release of the gem with the latest changes?
Thanks a lot for your help.
yousafn
2023-09-12 11:01
Sorry didn?t realise it wasn?t out, I assume this should go as a minor release
yousafn
2023-09-12 12:23
Hey @lluis.casals not sure if you can advise.
I?m not sure what is correct in ruby land in terms of package etiquette.
The PR introduces the restriction on minimum ruby version 2.6 or greater, so I just want to check if it should be bumped as a major or minor.
I would traditionally do a major in node-js projects on a language runtime restriction, but not sure if its done at minor level in ruby gems. (Gem versions seem to be _much_ lower than equivalent npm packages, and it?s been around alot longer, which is why I want to clarify)
yousafn
2023-09-12 12:29
Both semver specs and other sources such as http://gov.uk
https://semver.org/spec/v2.0.0.html#what-should-i-do-if-i-update-my-own-dependencies-without-changing-the-public-api
https://docs.publishing.service.gov.uk/manual/publishing-a-ruby-gem.html#ruby-version-compatibility
> We should then release the updated gem as a _minor version_. In the past, https://github.com/alphagov/govuk-developer-docs/pull/3932, but this was superfluous given that the change is low risk (Dependabot shouldn?t even raise a PR unless the upstream app is on a supported Ruby version). It also limited our ability to benefit from the automated workflows agreed in RFC-156, which https://github.com/alphagov/govuk-rfcs/blob/main/rfc-156-auto-merge-internal-prs.md#4-version-increase-is-patch-or-minor. Note that patch versions are generally reserved only for bug fixes.
lluis.casals
2023-09-12 12:58
Nice list of resources :ok_hand:
IMHO I would treat-it as a minor, so if the latest is https://github.com/pact-foundation/pact-provider-verifier/releases/tag/v1.38.0, next one could be 1.4
yousafn
2023-09-12 13:03
It?s out now,
https://rubygems.org/gems/pact-provider-verifier/versions/1.38.0
The last release was
https://rubygems.org/gems/pact-provider-verifier/versions/1.36.1
it should have been 1.37.0 however I used the old release workflow (which isn?t hooked up to the release, so it committed a tag, but didn?t trigger a release).
milda.abromaviciute
2023-09-26 12:44
Hi Pact team, quick query re: ruby version of pact ruby standalone. Saw it got bumped to ruby 3.2.2 a few months back, which is fantastic news! My question is, is the pact team gonna track security vulns related to the ruby version and update accordingly? Just need to understand what the maintenance looks like going forward, as our security team will need that info prior to installing the standalone on our end. Thanks a lot!
yousafn
2023-09-26 13:03
We are using a fork of the traveling-ruby build system
https://github.com/YOU54F/traveling-ruby
So have the ability to update as and when.
We use dependabot of the pact-ruby-standalone repo to track gem updates.
OSS Software is provided without warranty, given or implied. The source can be updated by anyone and PR?s proposed to patch any vulns.
What is the expectation of the security team?
yousafn
2023-09-26 13:04
Pertinent note in the licensing agreement
https://github.com/pact-foundation/pact-ruby-standalone/blob/7d6467e942884cf88f171de34bd1a6b5dbe94100/LICENSE#L15-L21
yousafn
2023-09-26 13:05
Now that doesn?t mean we don?t want to ensure it?s fully supported, and patched, but it?s a team effort and users of OSS must be prepared to help support projects they use, and your security team should take this into consideration.
milda.abromaviciute
2023-09-26 13:09
Hi Yousaf, thanks for the thorough reply. That is absolutely reasonable. We use dependabot also - so likely whatever flags up for us will flag up for you, too. I think expectation is just that it's not left alone/not updated with suggested patches etc. But as it's an active project and you guys are on top of it, we'll make sure to keep an eye out on anything that can be helped with, too. Thanks again for sorting the higher version of ruby in the project, it's making our life much easier! :smile: :tulip:
bethskurrie
2023-10-05 23:48
Hello ruby people! If anyone is up for a hacktoberfest contribution, the mock service needs a rack update, and it would be greatly appreciated https://github.com/pact-foundation/pact-mock_service/issues/145
me1685
2023-10-12 14:49
Has anyone been able to get the protobuf + grpc plugin to work with Ruby? I?m having trouble setting it up
yousafn
2023-10-12 17:58
yes part of the v4 spec and implemented in the rust core and exposed to other libraries via a cli and ffi.
i?ve unofficially been messing about integrating it with ruby
https://github.com/YOU54F/pact-ruby-ffi
patricio.dossantos_sl
2023-11-24 17:37
Hi there...
Anyone know an issue when using Pact with Rails 7.1.2 ?
I tried to upgrade a Rails app from 7.0.8 to Rails 7.1.2 and Pact start creating issues related with RSpec, even when I am using Minitest
The error:
```Error:
OperationResultTest::#target_type#test_0001_should be set to configured value after initialize for new record:
RSpec::Mocks::OutsideOfExampleError: The use of doubles or partial doubles from rspec-mocks outside of the per-test lifecycle is not supported.```
I am not using Rspec. And looking into Gemfile.lock, I see that Pact is the the introducing rspec. So I decided to disable pact, and my tests are green.
Any idea?
clm.whyte
2023-11-30 11:58
Has anyone run into issues having both `service_provider` and `message_provider` in the same `pact_helper.rb` file?
The solution I'm about to try is just changing the name of the message provider to `super_secret_name_for_slack_message` , and I expect that to work.
It would be ideal though, if we didn't need to have two different names for the provider service depending on which type of Pact we're expecting.
```Pact.service_provider "super_secret_name_for_slack" do
honours_pacts_from_pact_broker do
pact_broker_base_url pact_base_url, {token: token}
consumer_version_selectors [version_selector]
end
app_version provider_version
app_version_tags [provider_branch]
app_version_branch provider_branch
publish_verification_results publish_flag
end
Pact.message_provider "super_secret_name_for_slack" do
honours_pacts_from_pact_broker do
pact_broker_base_url pact_base_url, {token: token}
consumer_version_selectors [version_selector]
end
app_version provider_version
app_version_tags [provider_branch]
publish_verification_results publish_flag
builder do |message_description|
DatabaseCleaner.clean
CONFIG[message_description].call
end
end```
clm.whyte
2023-12-01 14:53
I've been able to create a new rake task which points to a new pact_helper file specifically for messages:
`contract_tests.rake`
```desc "Provider Contracts Message Verification"
Pact::VerificationTask.new(:messages) do |task|
task.pact_helper './spec/contract/service_consumers/pact_helper_message'
end```
gerard.molina
2023-12-13 12:48
Hello!
Would it be possible to have a release of the https://github.com/pact-foundation/pact-ruby with the latest changes? Specially the one regarding the x509 certificates handling.
Thanks in advance :raised_hands:
tom.dracz
2023-12-20 11:02
Hey there!
I'm having a problem with Pact ruby and provider verification. I've got a service that requires a date passed in the request body that is within next 30 days and can't find a good way to make it dynamic. Static JSON pactfile will obviously mean I would have to update the Pact every month which is not great.
Since pact ruby flavour doesn't yet support v3 Pact spec, there's no generators or similar to help out here.
Scouring through the code I've noticed https://github.com/pact-foundation/pact-ruby/commit/4ae0b5844aaaacf961af495df6a5d1a97c61f309 some `request_customizer` got added a good while back and in principle should let me achieve what I want to - i.e. dynamically modify the request body before running interaction.
However I'm unable to see how I can tap into this/pass customizer as an option when running `bundle exec pact verify` - it's not a CLI recognised option. Any good ideas here?
sterankin
2023-12-22 12:54
Trying to set up a quick POC locally. I have a pact json file in my rails app and have followed the guide.
1. Should I be running the rake command against `test` or `development`?
```bundle exec rake pact:verify
rake aborted!
KeyError: key not found: "RAILS_ENV"```
2. The API request in the consumer pact is a GET request to get foo/123. How do I ensure this id and associated data will exist in the database? (either test or dev). Surely I don't create this data but if I need do how is this done? I was under the impression that Provider simply pulls down the contract and runs it against an instance of the app. Since this will run on CI then I assume it will run against `test` and out sqlite3 db?
sterankin
2024-01-05 14:25
Just to follow up on this. Our consumer is Java based so it using v4 of the pact specification, but they are able to generate version 3.
it looks like ruby only supports v2, so a lot of warnings are generated,
e.g.
`WARN: Ignoring unsupported combine AND for path`
in terms of ensuring the test data is there, I am using the provider_states_for and inserting into the test database.
The only way I can get this to work is by using the:
```setup_do
... // using factorybot to create the item in sqlite3
end```
if i tried to use:
```provider_state "there is a foo named test foo" do
set_up do
.. // using factorybot to create the item in sqlite3
end
end```
it never works, the code in the provider state never gets called. I assumed it was some naming issue, in that the `providerState` field in the pact contract json needed to match the `provider_state` in the provider rb file. Both are exactly called `there is a foo named test foo` so i am not sure what the issue could be?
The pact provider and consumer names also match up and are the same in the json file and the pact_helper.rb etc
i am using the pact 1.64.0 ruby gem.
``````
yousafn
2024-01-09 08:03
hey up
i think pact jvm can also generate v2 specs which are fully supported by the ruby impl. provider state key was renamed from v2 -> v3
for test data, you would use provider states, where your provider would be responsible for honouring the state and setting the up the pre requisite data
https://docs.pact.io/getting_started/provider_states
sterankin
2024-01-09 11:42
Thanks - I will see if they can generate the v2 specs.
Any ideas why the `provider_state` is not working? I have to use the base state to setup the data, but this is less than ideal.
No matter what I try, the provider_state block never gets executed
sterankin
2024-01-09 11:48
```
require 'factory_bot_rails'
include FactoryBot::Syntax::Methods
Pact.provider_states_for 'GEB' do
provider_state "there is an Thing named Test Thing" do
set_up do
Thing.delete_by(id: 1)
create(:thing, id: 1, name: 'Test Thing', postal_addresses: [create(:postal_address, country_id: 1, postal_zip_code: "abc123")])
end
tear_down do
# Any tear down steps to clean up the provider state
end
end
provider_state "a thing does not exist" do
no_op # If there's nothing to do because the state name is more for documentation purposes,
# you can use no_op to imply this.
end
end```
joseph
2024-01-22 19:54
Hello,
I have an integration that uses `pact-ruby` on the provider and `pact-js` on the consumer. When I run the provider verification, I see `WARN` logs for
> `WARN: Ignoring unsupported combine AND for path`
On the consumer side, we're using matchers from the V2 version, not V3, since V3 matchers aren't yet supported by `pact-ruby`. Still seeing these logs, though. Is there any way to suppress these logs on provider verifications other than by increasing the log level to `ERROR`?
Thanks.
joseph
2024-01-29 18:34
@bethskurrie Sorry for the ping, but I figured you'd be the best to ask about this since it seems to be `pact-ruby` related. I've tried configuring the logger as outlined below, to no avail unfortunately. Do you happen to have any suggestions on suppressing these in console output?
```Tried both:
Pact.configure do |config|
config.logger = Logger.new($stderr, level: Logger::ERROR)
end
Pact.configure do |config|
config.logger = Logger.new($stderr)
config.logger.level = Logger::ERROR
end```
wiktor2.karpinski
2024-02-17 10:14
Hi, I'm interested in using pact-ruby for a project I'm running, however, it looks like for my use case I would require some V3 features. I'm particularly interested in state provider params and I'm wondering if there's a minimum feature set required to contribute at least partial support for V3 Any guidance on implementation also appreciated. Thanks!
yousafn
2024-02-20 12:11
Hey Wiktor,
We created a pact-compatability-suite to help test the implementations, and to check feature parity between implementations.
The v3 feature files are here
https://github.com/pact-foundation/pact-compatibility-suite/tree/main/features/V3
They are already in use across the Pact-JVM, Rust and PHP (ffi branch) repos.
Pact Reference, our new Pact Core in Rust supports v3/v4 specification, and I?ve currently wrapped the shared library in a Ruby FFI wrapper Gem
https://github.com/YOU54F/pact-ruby-ffi
The preferred path going forward, I think would be to integrate the rust core with ruby, to save having to reimplement features in the Ruby core.