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
This is an e2e example to show the provider verification working for both cli and python api.
3
+
This is an e2e example to show the provider verification working for both cli and python api.
4
+
5
+
Note in this example we are within conftest we are creating a Broker instance. This is purely to help demonstrate using Pact Broker in the code and you are strongly advised to set up a persistent Broker or use Pactflow
4
6
5
7
## Setup
6
8
7
9
Create your own virtualenv for this. Run
8
10
9
11
```bash
10
12
pip install -r requirements.txt
11
-
pip install ../../
12
-
pytest
13
+
pip install -e ../../
14
+
./run_pytest.sh
13
15
```
14
16
15
-
This should provide you with a relative path to pact install relatively (2 dirs up)
17
+
This should provide you with a relative path to pact install relatively (2 dirs up) You can look at the Makefile in the root folder for more details.
18
+
16
19
17
-
Create the local broker (for demo purposes only) Open a separate terminal in the examples/broker folder and run:
20
+
# Running
21
+
This example runs broker as part of it's tests. However, if you did wish to create the local broker open a separate terminal in the examples/broker folder and run:
18
22
```bash
19
23
docker-compose up
20
24
```
21
25
22
-
If you can open a browser to http://localhost and see the broker you have succeeded.
26
+
If you can open a browser to http://localhost and see the broker you have succeeded. You will have to remove the fixture in conftest.py to get this for the consumer to work, however.
23
27
24
28
## Consumer
25
-
26
29
From the root directory run:
27
30
28
31
```bash
@@ -40,9 +43,7 @@ To get the consumer to publish a pact to broker you will need to run (2 is an ar
0 commit comments