This time we will deal with an advanced topic: CI/CD implementation. But not just at a high level as we did in our first article “Contract Testing Workflows”, in this one we will go deeper and talk about very particular situations you are likely to face,and the options you have to deal with them.                                                                                                                                                                                           

In this article, we will talk about the classic Self-Hosted vs SaaS doubt: which option is a better fit for my needs? Do I have the knowledge and resources required for a self-hosted approach?We will structure the article into key points, and inside those points, we’ll be covering the differences between one approach and the other.

Learn about implementing contract testing at scale in the “Road to Pactflow Enterprise” series on Sngular QE Blog. Topics include workflows, on-premise vs SaaS, contract testing and CI, development, and SSO configuration.                                                                                                                                                                                                   

Learn how to define workflows for contract testing in real-world scenarios. Gain insights to cover basic workflows, adapt tips to your enterprise, and understand common changes.

In this post, you'll learn how to apply bi-directional contract testing when we only have a few tests performed in Postman to test the provider side with PactFlow.

In this article we will cover the basic aspects of SoapUI. We use SoapUi as a tool to automate the functional tests of our APIs.                                 

 In this article we will talk about Karate, an open source testing framework that facilitates the development of automatic API tests in a fast, clear and maintainable way.

In this article, we will look at how to properly integrate contract testing into a continuous integration workflow. Specifically, we will look at the case of integrating PACT into a Jenkins pipeline, using the Pact Broker tool.

A virtue of our automatic tests has always been the speed of execution. To get fast results, tests must be executed in the shortest possible time. This lead to quick analysis and decision making.     

When we work in partnership with other companies to search for specific technological solutions, we rely on the experience of our team and only partner with companies that will provide the greatest value for our clients.                          

In this article we discuss how to approach the quality of software development in DevOps. We will talk about a continuous integration model. Specifically in regard to changing code in a final environment without errors, taking the shortest time and having the minimum impact on the available infrastructures.