Data quality testing is a subset of data observability. It is the process of evaluating data to ensure it meets the necessary standards of accuracy, consistency, completeness, and reliability before it is used in business operations or analytics. This involves validating data against predefined rules and criteria, such as checking for duplicates, verifying data formats, ensuring data integrity across systems, and confirming that all required fields are populated.

Although GoMock is one of the most popular ways to create mocks in Golang, it’s important to understand the broader landscape of mocking methods in the language to fully leverage its potential value in testing. Mocking is a powerful technique that allows developers to isolate their code, improve test reliability, and ultimately enhance overall code quality.

In software development, load testing plays a critical role in ensuring that applications perform optimally under any imaginable load condition. To do this, developers subject applications to several types of load tests, including scalability, spike, endurance, and stress testing. The ultimate goal of these performance tests is to pinpoint potential bottlenecks and ensure the reliability of the overall system where the software application runs before reaching production.

The benefits of API mocking extend beyond just speeding up development. It enables developers to work independently of external APIs, eliminating delays caused by dependencies that may be out of their control. This independence is crucial for maintaining workflow efficiency, especially in complex projects involving multiple APIs. API mocking is invaluable for testing edge cases and error scenarios that might be difficult to reproduce with a live API.

As part of our recent failure testing project, we ran into an interesting failure mode involving the OpenTelemetry SDK for Go. In this post, we’ll show you why our apps stopped sending telemetry for over 15 minutes and how we enabled keepalives to prevent this kind of failure from happening in the future.

You probably know that Microsoft’s Playwright is a solid tool for end-to-end testing, enabling you to control headless browsers and check essential user flows. But did you know that you can also use Playwright for API testing? If you didn’t, then this guide is for you. In this post, we’ll explore how Playwright can be used to test a GraphQL API (but don’t worry if you’re using REST; Playwright can handle any HTTP-based API).

You can write Playwright end-to-end testing code using JavaScript or TypeScript. Which one should you choose? When I started writing my first automated browser tests, I went with JavaScript because I couldn't be bothered with the type wrangling. I just wanted to get something off the ground quickly. YOLO, right? Today, though, there are two reasons why I last wrote a JavaScript-first Playwright test a very long time ago.