Browsed by
Category: API test automation

woman in white shirt showing frustration
Do your tests fail the right way?

Do your tests fail the right way?

This entry is part 3 of 3 in the series Writing automated API tests

It’s not much help failing unless they tell you what went wrong. A while back I wrote an article about the challenges of authentication for Automated API tests. At work we have also recently started rolling out the first API tests on a new framework with all new Authorisation code. The rollout went fine until literally the last production environment and then bam: The tests failed throwing a random de-serialisation exception. Worse still, the exception was thrown in a library…

Read More Read More

A mobile phone app offering Authentication options
It’s all about the “Auth”

It’s all about the “Auth”

This entry is part 2 of 3 in the series Writing automated API tests

In the first post in this series I shared my horror in discovering that my process for Authenticating my API tests was broken. Suddenly I had no means to make the API calls required to test that my services were responding as expected. So what exactly do I mean by an Auth service? The two “Auths” I have gone to great lengths to build up my super new data service, the best in the world. Now I want to release…

Read More Read More

Supported Feature Configuration code
Feature switching for release testing.

Feature switching for release testing.

When your cloud deployments do not all have the same features enabled, running the same tests calls will generate different reponses. How can you ensure that the tests for each individual release verifies the expected functionality for that deployment? The problem It is not uncommon to deploy code to production servers that is hidden behind a feature switch. When the moment comes to go live, the configuration is changed to enable the feature. If it is just new functionality, you…

Read More Read More