elitau / pact_elixir Goto Github PK

Travis seems to have a very limited amount of credits for OSS:

Builds have been temporarily disabled for public repositories due to a negative credit balance.

Another CI provider might be useful.

Play with StreamData

With semantic-release semantic versioning is assured, a changelog is generated and a lot of other great features and open source library guidelines are realised.

Hey,

First of all thank you for the library 🙌 I'm using it for the first time in a project that's running Erlang/OTP 22, and I'm getting the following error:

==> pact_elixir
Compiling NIF crate :pactmockserver (native/pactmockserver)...
   Compiling erlang_nif-sys v0.6.4
   Compiling url v1.5.1
   Compiling unicase v1.4.2
   Compiling rustler_codegen v0.18.0
   Compiling env_logger v0.4.3
error: failed to run custom build command for `erlang_nif-sys v0.6.4`

Caused by:
  process didn't exit successfully: `/home/app/elixir-artifacts/_build/service_level_test/rustler_crates/pac
tmockserver/release/build/erlang_nif-sys-530dba2e3c1f88c9/build-script-build` (exit code: 101)
--- stdout
Unsupported Erlang version.

Is the erlang_nif-sys version up to date in the Cargo.toml?
Does 'cargo update' fix it?
If not please report at https://github.com/goertzenator/erlang_nif-sys.

--- stderr
thread 'main' panicked at 'gen_api.erl encountered an error.', /home/app/.cargo/registry/src/github.com-1ecc
6299db9ec823/erlang_nif-sys-0.6.4/build.rs:28:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

Is it possible to add support for Erlang/OTP 22? Is it just a matter of updating the rustler version in the Cargo.toml? If so, I don't mind submitting a PR! Thanks in advance 🙇‍♂️

During boot of the pact_elixir application a Supervisor with :simple_one_for_one strategy (or the new Dynamic Supervisor should be started. Then start mock servers upon test run with Supervisor.start_child(supervisor_pid, [args]) and stop them with Supervisor.terminate_child(supervisor_pid, child_pid).

Thus the mock servers would be restarted upon errors during test runs without bringing the whole application down.

A sane default would be the root of the project - which it is now.

They also serve as documentation for users and developers of the library.

It seems that this pact elixir implements against PACT V2.
Current version it is V3.

Do you have a plan to move to V3?

thanks

If someone uses this library to generate pact files, rust must be installed on their systems. I don't know how and if is possible at all, but it would be great to have some kind of precompiled executables in the hex package.

This should return something like http://localhost:51234

https://docs.pact.io/getting_started/provider_states

Since June 15th, 2021, the building on travis-ci.org is ceased. Please use travis-ci.com from now on.

In pact-foundation/pact-reference@5606c0c#diff-72812e30873455dcee2ce2d1ee26e4ab and pact-foundation/pact-reference@dab7fb9#diff-72812e30873455dcee2ce2d1ee26e4ab @uglyog added a Rust interface underneath the previously exported C functions.

Use this Rust interface instead of the C functions.

Write pact file automatically after test suite ends and is green. To do this the library need to add an on_exit ExUnit hook.

@uglyog from pact-reference told me this about the pact_ verifier lib:

ME: I have a very rough implementation of the consumer side (through wrapping pact_mock_server) and now had looked into the provider side. But the API there is kind of hard: you need to pass in many complex objects into theverify_provider function (ProviderInfo, PactSource etc.). Is it planned to create a simpler API there, too?

@uglyog: There has been a bit of discussion on what the provide API should look like. No consensus yet, I was waiting for an implementation so we can work it out. If you can define what you need (making it consumer driven 😉 ), we could implement that.

https://docs.pact.io/getting_started/matching

Show failures and errors like ExUnit would do.

As this project is also for me to learn new things...

Blog post about Ebert

https://github.com/pact-foundation/pact-go/tree/master/examples/messages

Following the implementation guidelines of pact the a pact broker client needs be built, which uploads the generated pact file to a pact broker.