API Testing Kubernetes: Transparent Remoting Using HCL OneTest
Chris Haggan, Head of Product – DevOps, HCL Software and Martin Lescuyer, HCL OneTest Product Manager
Testing in a cloud and containerized world is often very difficult. One of the painful tasks that testers have to face is that once the containers are deployed, some of their APIs might remain accessible but others — the internal ones — are not reachable anymore. Even if a part of their APIs remains accessible, the requests sent from outside the application must fly through several management layers. Testers might want to remove these layers and send requests straight to the service they want to test.
A typical Kubernetes application is usually made of several containers, and services within those containers. These are usually located behind an Egress/Ingress controller and many security layers, so interactions with the application are restricted to the overall application APIs, whether they are published or not. HCL OneTest offers a solution to these restrictions. Transparent remoting using HCL OneTest addresses individual services in the Kubernetes cluster directly–as if they were local. Rather than going through the Ingress controller, testers can interact with the containerized services directly.
Listen to Chris Haggan, HCL Software Head of Product- DevOps, and Martin Lescuyer, HCL OneTest Product Manager, on the latest TestGuild automation podcast as they discuss how Transparent Remoting using HCL OneTest works, what it looks like in practice, and why it’s so important for your users.