In the process of developing software, designing and performing testing is a critical aspect of ensuring high software reliability, improving software quality, and deploying strong fit and function. The shift-right testing approach moves testing to later in your production cycle as a way of doing this with more accurate user data and post-production testing practices. Also known as “testing in production,” with shift-right, you test software after it has been deployed.

It’s impossible to learn about containerization without hearing about Docker and Kubernetes. These two tools together dominate the world of containers, both being the de facto standard in what they each do. When you’re first getting started learning about containers, it can be quite a challenge to figure out the differences between these two tools.

A software update failure led to one of the most infamous outages of the year: the Crowdstrike Outage. The incident is estimated to have cost Fortune 500 companies more than USD 5 billion. Per the congressional testimony by Crowdstrike’s officials, the downtime wasn’t attributed to a malicious attack but a configuration and software update failure. Incidents like these make us question how we deal with our digital ecosystems - the configurations, the monitoring, the testing, etc.

Today’s complex, dynamic applications demand rigorous resilience testing. A common hurdle is accurately mimicking real user behavior. This post discusses a possible solution: production traffic replication (PTR), a technique that captures actual user interactions to enhance chaos testing, and the principle of intentionally introducing failures to evaluate application recovery.

Kubernetes is an incredibly powerful solution, but testing the Kubernetes Ingress resources themselves can prove to be quite tricky. This can lead to significant frustration for developers – bugs can pop up in production that weren’t caught during testing, workflows that make sense on paper might fail in practice, and so forth.

Platform engineering is a software development approach that combines DevOps principles to elevate the developer experience. It focuses on designing and constructing toolchains and workflows that promote self-service capabilities for software engineering teams. By addressing security, compliance, and operational efficiency, platform engineering enables organizations to build robust internal systems tailored to the needs of both developers and operations teams.

Local preview environments are transforming how developers test and validate code changes before merging them into the main codebase. Acting as temporary cloud environments, they provide a production-like setting where new features and bug fixes can be tested in isolation, catching issues early and streamlining the development code review process. These environments are crucial for enhancing development velocity, especially in CI/CD workflows used by DevOps engineers and QA teams.

We’re happy to announce that Codemagic has received a perfect SOC 2 Type 2 report! We received our SOC 2 Type 1 report earlier this year and now we have received our Type 2 report with no exceptions noted! At Codemagic, we take the security and privacy of your data seriously. That’s why we went through the tough process of getting audited with the SOC 2 framework. “We’re proud to have achieved a perfect SOC 2 Type 2 report!

App Center, a popular CI/CD platform from Microsoft, announced it will close its doors on March 31st 2025. This has left many mobile developers and teams looking for an alternative. Probably the most affected is the React Native community who have relied on App Center because of its OTA updates with CodePush.

Today’s software testing trends show the growing demand for more efficient and automated API testing. Manual testing is not only time-intensive for internal testing teams, it can also lead to poor customer experiences. When manual testing processes cannot proactively discover issues, your customers may inevitably be the ones finding them. Many of the current test automation solutions today focus on the UI, while most API-level testing is still done manually.