039: Pact HTTP Provider Testing (Golang) 

It would be possible to run test without docker however it would take a lot of work you would have to install and config an instance of Postgres to run on your machine and run all the migrations to create the tables. If you can just install docker on you machine it would be easier. I have a make file that would do all the work after that. `make test` would create all the docker instance you need and run the test. if you don't have make you can run the commands yourself `docker build . -t service_test --target=test` - Builds the container `docker-compose up -d` - Starts the container `docker-compose exec -T http go test -tags="integration pact e2e" ./...` - runs the tests on the running container `docker-compose down` - stops the container

The test in the e2e directory do not run with a plain `go test -v ./...` because they have build tags (ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-QSnSLzeqkDE.html) applied to them they will only run with the correct tags on the test command `go test -v -tags="integration pact e2e" ./...`

@@TestingAllTheThings Thank you! I like your channel and will totally start the series from the beginning

Glad you liked it

Glad you found the videos helpful For the pact tests could could seed the database via the setup methods in the tests or use the state handlers as part of the pact setup. Using the state handers allows you to intercept the setup of the consumer and the given in each of the interactions. For a simple case of a thing being there or not that would probably work. If your responses become more complex (soft delete for example) you might want to jump into the state handlers

@@TestingAllTheThings Thanks for your reply, appreciated.