{"id":1387,"date":"2022-03-08T08:05:57","date_gmt":"2022-03-08T15:05:57","guid":{"rendered":"https:\/\/bullyrooks.com\/?p=1387"},"modified":"2022-03-13T13:43:15","modified_gmt":"2022-03-13T20:43:15","slug":"kube-cloud-pt6-provider-contract-test-for-rest-endpoints","status":"publish","type":"post","link":"https:\/\/bullyrooks.com\/index.php\/2022\/03\/08\/kube-cloud-pt6-provider-contract-test-for-rest-endpoints\/","title":{"rendered":"Kube Cloud Pt6 | Provider Contract Test for REST Endpoints"},"content":{"rendered":"\n
Now lets move over to message-generator repo and create a new branch<\/p>\n\n\n\n
This time we’re doing quite a few things that may be new (they were to me).<\/p>\n\n\n\n
First, we’re adding the dependencies to create the pact provider tests. We need these in order to get access to the classes that we’ll use to write the provider side tests (which are significantly different than the consumer tests). Additionally, we need the pact provider plugin. This gives us access to the functions we can call through maven to publish the test verifications as well as confirm that the contract has been met before we can deploy.<\/p>\n\n\n\n
Next, pact provider tests introduce a dependency on the pact broker. We don’t necessarily want our unit tests to have to call out to pact broker every time we want to build and test a minor change that doesn’t affect the contract. In fact, we want to limit those executions because they’re expensive and have an environment dependency (a connection to the pact broker). So we’re introducing the surefire plugin configuration to ignore certain tests (annotated with the junit Tag<\/code> annotation) and a new profile which will run those tests using a profile flag when we actually want them executed.<\/p>\n\n\n\n
Tests<\/h2>\n\n\n\n
Lets first create the provider verification test in src\/test\/java\/com\/bullyrooks\/messagegenerator\/controller\/MessageControllerContractIT.java<\/code><\/p>\n\n\n\n
First, set our tag (ContractTest<\/code>) and our pact configuration to setup a pact provider test that should talk to the pactflow pact broker. We’re going to inject our token into the environment variables later. Next we’re letting the test know to setup a pact server in @BeforeEach<\/code>. This server is going to take our contract, setup a client to make the requests the contract specifies and verify the response against the contract. That’s what we’re doing with the PactVerificationSpringProvider <\/code>(verifying the contract against the response). Finally, we’re defining a @State<\/code> test (which should match the state from the contract). The only thing we have to do here is tell our controller to interact with our mock MessageService <\/code>and force it to return the expected response to match the contract.<\/p>\n\n\n\n
Its actually really easy, but the hard part is figuring out where to mock and defining the behavior to return. Some interactions are basic (like this one), but some contract tests may drive you to use more of your actual service behavior (like a behavior driven test). The line between black box tests (behavior tests) and contract tests will be blurred. I prefer<\/em> to keep them separate because they perform separate functions and contract tests require environment configuration. However, that introduces a risk that your contract test behavior could drift from your behavior tests and the contract tests could<\/em> pass, but your service doesn’t actually exhibit the behavior they say they do. You will have to find the balance for your team and organization.<\/p>\n\n\n\n
In all other unit tests add this annotation<\/p>\n\n\n\n
@Tag(\"UnitTest\")<\/code><\/pre>\n\n\n\n
This will keep the contract test verification step from running them.<\/p>\n\n\n\n
You should be able to confirm both types of tests now (unit tests):<\/p>\n\n\n\n
mvn clean test<\/code><\/pre>\n\n\n\n
should run successfully since it shouldn’t use any of the new contract test logic. <\/p>\n\n\n\n<\/figure>\n\n\n\n
Before we run the contract tests you’ll need to set the environment variables.<\/p>\n\n\n\n
Make sure to add a secret for the PACTFLOW_TOKEN <\/code>in the message-generator<\/code> repository similar to what you did in the last course.<\/p>\n\n\n\n
update features.yaml<\/p>\n\n\n\n
name: Cloud Application Feature Branch Build\r\n\r\non:\r\n push:\r\n branches-ignore:\r\n - main\r\nenv:\r\n PACTFLOW_URL: https:\/\/bullyrooks.pactflow.io\r\n PACTFLOW_TOKEN: ${{secrets.PACTFLOW_TOKEN}}\r\n PACTBROKER_HOST: bullyrooks.pactflow.io\r\n\r\njobs:\r\n build:\r\n runs-on: ubuntu-latest\r\n steps:\r\n - uses: actions\/checkout@v3\r\n with:\r\n fetch-depth: 0 # Shallow clones should be disabled for a better relevancy of analysis\r\n - name: Set environment variables\r\n run: |\r\n # Short name for current branch. For PRs, use target branch (base ref)\r\n GIT_BRANCH=${GITHUB_HEAD_REF:-${GITHUB_REF#refs\/heads\/}}\r\n echo \"GIT_BRANCH=$GIT_BRANCH\" >> $GITHUB_ENV\r\n echo \"VERSION=$GITHUB_SHA\"\r\n echo \"VERSION=$GITHUB_SHA\" >> $GITHUB_ENV\r\n\r\n - name: Set up JDK 11\r\n uses: actions\/setup-java@v2.5.0\r\n with:\r\n java-version: '11'\r\n distribution: 'adopt'\r\n cache: maven\r\n\r\n - name: Maven Tests\r\n run: .\/mvnw -B test\n\r\n\r - name: Create Pact Version Tag\r\n run: |\r\n .\/mvnw pact:create-version-tag \\\r\n -Dpacticipant=message-generator \\\r\n -DpacticipantVersion=${{ env.VERSION }} \\\r\n -Dtag=initial\r\n\n - name: Verify Contract Tests\r\n run: |\r\n .\/mvnw -B verify -Pcontract \\\r\n -Dpactbroker.host=${{env.PACTBROKER_HOST}} \\\r\n -Dpact.verifier.publishResults=true \\\r\n -Dpact.provider.version=${{env.VERSION}} \\\r\n -Dpact.provider.branch=${{env.GIT_BRANCH}} \\\r\n -Dpact.provider.tag=okteto \\\r\n -DPACT_CONSUMER_SELECTOR_TAG=okteto,pre-okteto\r\n continue-on-error: true #verify may fail, but we're relying on can-i-deploy to control deploy\r\n\r\n - name: Set up Docker Buildx\r\n uses: docker\/setup-buildx-action@v1\r\n\r\n - name: Cache Docker layers\r\n uses: actions\/cache@v2\r\n with:\r\n path: \/tmp\/.buildx-cache\r\n # Key is named differently to avoid collision\r\n key: ${{ runner.os }}-multi-buildx-${{ github.sha }}\r\n restore-keys: |\r\n ${{ runner.os }}-multi-buildx\r\n\r\n - name: Build and push\r\n id: docker_build\r\n uses: docker\/build-push-action@v2\r\n with:\r\n context: .\r\n push: false\r\n cache-from: type=local,src=\/tmp\/.buildx-cache\r\n cache-to: type=local,mode=max,dest=\/tmp\/.buildx-cache-new\r\n # This ugly bit is necessary if you don't want your cache to grow forever\r\n # till it hits GitHub's limit of 5GB.\r\n # Temp fix\r\n # https:\/\/github.com\/docker\/build-push-action\/issues\/252\r\n # https:\/\/github.com\/moby\/buildkit\/issues\/1896\r\n - name: Move cache\r\n run: |\r\n rm -rf \/tmp\/.buildx-cache\r\n mv \/tmp\/.buildx-cache-new \/tmp\/.buildx-cache\r\n\r\n - name: Pact Can-i-deploy\r\n run: |\r\n docker run --rm pactfoundation\/pact-cli:latest \\\r\n broker can-i-deploy \\\r\n --pacticipant=message-generator \\\r\n --to-environment=okteto \\\r\n --version=${{ env.VERSION }} \\\r\n --broker-base-url=${{ env.PACTFLOW_URL }} \\\r\n --broker-token=${{ env.PACTFLOW_TOKEN }}<\/code><\/pre>\n\n\n\n
First, set the environment variables we’ll need. Then I renamed the maven build task to signal that I was just running unit tests. Next I am running the contract tests in a separate task. You can see that the results are being published and that I’m running can I deploy at the end. However, there’s an important piece here where I’m creating a version tag. This signals to pact that I’ve got a new service and since our service is a provider it will be able to be promoted without needing to fulfill a contract if there’s no consumers. If we don’t have this piece we’ll never be able to deploy since we won’t have a fulfilled contract. Publishers should<\/em> be able to publish if no one depends on them yet and that’s what we’re allowing.<\/p>\n\n\n\n
The first part is the same. However, I need the version when I run the verify step here, so I’ve moved the “Bump Version” task. This will actually run the tests and publish the results back to the pactflow service (pact.verifier.publishResults=true<\/code>). I’m telling it which version and branch I am running against so that the verification results can be stamped correctly. Additionally, I’m stamping with my environment (okteto), so that can know “where” my contract verification is valid.<\/p>\n\n\n\n
The next part is the ‘can-i-deploy’ check, which comes before the Deploy <\/code>task. This checks to see if the version that I’m about to deploy is compatible with all versions in my okteto environment. This can get really tricky with rollback, so if that is important to you make sure you have a rollback plan!<\/p>\n\n\n\n
Finally, if everything works, I update the release and deploy record.<\/p>\n\n\n\n
Build and Deploy<\/h2>\n\n\n\n
First, we need to create an ‘environment’ so that pact knows what services need to interact with each other in each environment. Lets make one for okteto<\/p>\n\n\n\n
Go ahead and commit your feature branch and lets go ahead and create a PR similar to what we did for the consumer. It should pass once the build succeeds<\/p>\n\n\n\n<\/figure>\n\n\n\n
and when that succeeds, go ahead and merge to main. Watch this kick off. You should see your contract get verified and deployed successfully.<\/p>\n\n\n\n<\/figure>\n\n\n\n
Also, you’ll see that the contract has not<\/strong> been fulfilled in pactflow<\/p>\n\n\n\n<\/figure>\n\n\n\n
So we need to get the consumer rebuilt now that we’ve got a provider in place.<\/p>\n","protected":false},"excerpt":{"rendered":"
\nNow lets move over to message-generator repo and create a new branch…\n<\/div>\n
![\"\"](\"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/03\/image-10.png?resize=674%2C255&ssl=1\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/03\/image-11-1024x250.png?resize=960%2C234&ssl=1\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/03\/image-12.png?resize=827%2C710&ssl=1\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/03\/image-13.png?resize=563%2C241&ssl=1\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/03\/image-14-1024x358.png?resize=960%2C336&ssl=1\")
<\/figure>\n\n\n\n