You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -54,13 +54,19 @@ It's accessible at http://127.0.0.1 with username 'pactbroker' and password 'pac
54
54
55
55
To run the test, this time pushing the generated pact into the broker with version '0.1' of UserServiceClient, use:
56
56
```
57
-
(venv) $ pytest --update-pact 0.1
57
+
(venv) $ pytest --publish-pact 0.1
58
58
```
59
59
60
60
The `tests/conftest.py` adds this custom option, and `tests/test_client` has code in the `pact` fixture to upload to the broker if the command line option was passed.
61
61
62
62
63
-
Then, you can validate the provider (UserService) and push the result to the broker by running `./verify_pact.sh 0.2` -- which runs the same `pact-verifier` command as above but has additional args for pulling the pact file from the broker (instead of getting the .json locally) and pushing the verification result to the broker.
63
+
Then, you can validate the provider (UserService) and push the result to the broker by running:
64
+
```
65
+
(venv) $ python pact_python_demo/user-app.py
66
+
(venv) ./verify_pact.sh 0.2
67
+
```
68
+
69
+
This runs the same `pact-verifier` command as above but has additional args for pulling the pact file from the broker (instead of getting the .json locally) and pushing the verification result to the broker.
64
70
65
71
Log in to the broker and take a look at the matrix. You will see that UserClientService version 0.1 has been verified against UserService version 0.2
0 commit comments