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
Copy file name to clipboardexpand all lines: README.md
+6-4
Original file line number
Diff line number
Diff line change
@@ -591,7 +591,7 @@ We expected this failure, because the product we are requesting does in fact exi
591
591
592
592
We could resolve this by updating our consumer test to use a known non-existent product, but it's worth understanding how Provider states work more generally.
593
593
594
-
Move on to [step 7](https://github.com/pact-foundation/pact-workshop-jvm-spring/tree/step7#step-7---adding-the-missing-states)
594
+
Move on to [step 7](https://github.com/pact-foundation/pact-workshop-jvm-spring/tree/step7#step-7---adding-the-missing-states)
595
595
596
596
## Step 7 - Adding the missing states
597
597
@@ -613,9 +613,9 @@ Let's open up our provider Pact verifications in `provider/src/test/java/au/com/
_NOTE_: The states are not necessarily a 1 to 1 mapping with the consumer contract tests. You can reuse states amongst different tests. In this scenario we could have used `no products exist` for both tests which would have equally been valid.
644
644
645
+
Move on to [step 8](https://github.com/pact-foundation/pact-workshop-jvm-spring/tree/step8#step-8---authorization)
646
+
645
647
## Step 8 - Authorization
646
648
647
649
It turns out that not everyone should be able to use the API. After a discussion with the team, it was decided that a time-bound bearer token would suffice. The token must be in `yyyy-MM-ddTHHmm` format and within 1 hour of the current time.
0 commit comments