Contract Testing Strategy for TCS

Please find the below points which describe the flow/interactions between the services we want to introduce contract testing to start with. Initial POC needs to be done for TCS contract testing based on the demo of Pact testing done for  ESR/ETL and ESR Service.

The POC will use the initial calls to profile and reference (on clicking "create post") as a starting point for generating pacts. Below is the different flow needs to be considered for contract testing for TCS initially.

As a proof of concept, we'll look at creating a post in TCS and the interactions/flow with other services.

The basic flow is as follows:

Click "create post". 
Calls to: 
/profile/api/userupdate
/reference/api/funding-types

Further calls from smart search when filling in form:
/reference/api/sites
/tcs/api/specialties
/reference/api/grades
/reference/api/local-offices
/tcs/api/programmes
/reference/api/trusts
/tcs/api/findByNationalPostNumber
/tcs/api/rotations

On click of "Save", calls to:
/tcs/api/posts
/reference/api/dbcs
/reference/api/dbcs/user
(These calls are because the posts list screen loads after clicking save)