DiUS announced four-time finalist in the ARN Innovation Awards for 2020.
DiUS is proud to be named as four-time ARN Innovation Awards 2019 finalists, in diverse categories.
We have now entered the era of the serverless function and we no longer have to worry about where or how our code runs. Someone else will do the worrying for us (for a nominal price) and we only have to concern ourselves with getting our functions to fulfill their destinies and become all they can be.
If you’re using Travis CI, Code Climate, or one of many other CI tools with Github, you’ve probably noticed the little checklist of items that shows just above the “merge” button when you open a pull request.
In a recent project, we had two frontend applications both of which are consuming common microservice APIs (all developed by our team). During the project we decided to go ahead with creating Consumer Driven Contract tests to make sure that all the applications were working well with each other.
Imagine – you’re on a team writing an app that uses three different HTTP APIs, and you’ve decided to use consumer contracts to test your integrations.
With the move to microservices, or µ-services for the more stylish, Consumer Driven Contract testing with Pact evolved as a strategy to be able to determine if all of our services will talk correctly to each other.
Contract testing is an approach that captures the interactions between two services and saves them as a contract, which can then be used later to verify that both parties adhere to it.
How do we measure that our development arm, technical architecture and processes are working in order to improve them?
So you heard about Pact and want to get started. This guide should hopefully get you going in the right direction.