API consumers have high expectations and API providers know they need to standardize their services to provide the best possible developer experience.

Nowadays performance is everything. It only takes one second of lag time to lose 7% of the conversions you would have had if your performance met the standards of your users. So how can agile teams keep up with their continuous delivery cycles and ensure they execute all the necessary performance tests? One way to do this is to integrate performance testing into your CI/CD pipeline.

Performance testing is critical if you want to scale web applications. Poor performance is a major reasons why digital companies lose users, which is why it’s imperative to ensure your application infrastructure is able to handle the anticipated load without compromising on your end user experience.

All of us want to create reliable and effective API tests. We are here to help you with this! We are starting a series of interviews to analyze the most common mistakes that occur when testing APIs. We will tell you how to avoid such mistakes and change your testing methodology. Today, we will discuss why focusing only on the most common messages when preparing tests is bad.

We invited a well-known test automation trainer and consultant, Bas Dijkstra, to talk about combining UI testing and API testing.