Tomas Fernandez

For a company like Semaphore that consists of small and agile teams where every individual counts, finding the right engineers is crucial to success.

Tests enforce requirements and provide feedback, telling us when something breaks. But are they always necessary?

Test automation allows developers to get continuous feedback and spot problems very early in the production cycle. Quick iteration results in improved design, better quality, and safer launches.

Tests should help development, not block it. Optimize them to keep you development cycle fast and stay competitive.

Change is inevitable, and while commits on Dockerfiles are easy to control, the impact of those changes on the resulting image are not. Fortunately, where there’s a need, there’s a tool.

In this article, I’d like to talk about one of the most complex forms of testing, one that will tell us when we have met our software design goals: Acceptance Testing.

Without security in your CI/CD, sooner or later, a vulnerability will sneak in, and before you know it, someone will be mining at your expense.

A recent survey by Red Hat found that more than half of the Kubernetes environments are misconfigured. Even worse, about 90% of respondents had at least one security incident last year, leading to the very first wave of Kubernetes-native malware. In this tutorial, we present three tools to validate and secure your Kubernetes deployments.

We don't pay attention to containers — until something breaks. Structure tests let us check container vital before deployment.