Systems | Development | Analytics | API | Testing

Last week, industry leaders gathered at the Game Technology Summit during GDC 2025 to explore emerging trends and challenges in game development. The panel discussion, moderated by Jase Lindgren (Sr. Solutions Engineer and P4 Evangelist, Perforce), featured insights from Colin Walder (Engineering Director, CD PROJEKT RED), Joshua Orellana (Head of Animation and Games, Halon Entertainment), and Matt Ellis (Game Dev Advocate, JetBrains).

Playwright is a Microsoft-created NodeJS package with capabilities that are quite similar to Puppeteer. Both libraries enable you to automate browser-based tasks. With Playwright, you can launch or connect to a Chrome, Edge, Safari, or Firefox browser and exchange instructions. The DevTools protocol (for Chrome browsers) and a bespoke protocol (for Firefox and WebKit browsers) are used for these messages.

When running tests in a CI/CD pipeline, relying on external APIs can introduce instability, slow down execution, and even lead to failed builds due to rate limits or API downtime. Fortunately proxymock provides a solution by capturing API interactions and running a local mock server, enabling fully isolated and repeatable tests. In this blog, we’ll demonstrate how to integrate proxymock into a GitHub Actions CI pipeline using a demo app called outerspace-go.

If you’re looking for an alternative to Microsoft App Center, this article will cover the top considerations, and how Sauce Labs handles these in its Mobile App Distribution offering.

APIs power everything—from your favorite apps to critical business systems. But what happens when your API is subjected to large or unexpected traffic, security threats, or plunges under load? One weak link can destroy UX, destroy data or take down your service. API testing serves as your safety system beyond being a mandatory requirement. Faster development schedules and increased user demands during 2025 require organizations to make essential testing tool choices.

Volume testing is a type of software performance testing that evaluates a system’s capacity to process massive data volumes within a specific timeframe. It identifies bottlenecks, crashes, or inefficiencies under high data loads, ensuring performance, accuracy, and stability.

Regulated industries – from healthcare to finance – face a dual challenge: delivering high-quality software at speed while maintaining strict compliance with industry regulations. The stakes are high, with non-compliance leading to massive fines, reputational damage, loss of customer trust and operational disruptions. The good news? Compliance doesn’t have to be a bottleneck. With the right tools, it can become a seamless part of your development process.

In coding land, it’s really important to ensure that your app behaves as it should, isn’t it? One of the ways people do this is by doing something called assertion testing. Assertion testing is about creating checkpoints in the form of assertions. They’re small tests that verify everything’s going as expected while the program’s executing its task.

From the technical perspective of QAs, investing in test automation is no longer a nice-to-have, but a necessity. However, the problem arises when they seek alignment with the non-technical stakeholders. To secure leadership buy-in, it is important that you translate the value of test automation into business value. More than just faster releases, it is also about having lower risk, better customer experience, and a stronger competitive edge.