Systems | Development | Analytics | API | Testing

Test Your MySQL 8.4 Upgrade With Real App Queries

Before you start, paste this into Claude Code, Cursor, Codex, Gemini CLI, Kiro, or any assistant that can read a URL and run commands: The install-speedscale skill installs proxymock for your operating system and walks you through proxymock init. It stops when you need to complete browser sign-in, keeps your recordings on your machine, and connects the proxymock MCP server so your assistant can run the prompts later in this article.

Test PostgreSQL With the Queries Your App Actually Runs

The first number from my local PostgreSQL 16 test was roughly 1,600 statements per second. It looked impressive. It was also the least useful result in the run. The useful part was the workload. It came from queries the demo app had actually sent: the same prepared statements, parameters, reads and writes. A synthetic benchmark tells you how PostgreSQL handles a synthetic workload. It does not tell you whether your migration just broke the UPDATE your app depends on.

$4.48 a Gallon: Your Holiday Checkout Is the New Mall

Remember when “going shopping” meant getting in the car? This fall, filling the tank feels like applying for a small loan. U.S. regular gasoline averaged about $4.48 a gallon for the week of September 21, 2026. A round trip to the store starts competing with free shipping. And free shipping never needs a parking spot. That doesn’t tell us how many shoppers will move online this holiday season.

How Will Software Engineers Interface with AI in the Future? aicoding #devops #techdebate #aiagents

A breakdown of the three potential ways software engineers will interact with AI coding assistants, ranging from local desktop setups to fully automated software delivery factories. Learn more: speedscale.com.
Sponsored Post

Imaginary Test Data. Real Token Bill.

Ask an AI for K-pop concert advice without saying the group, city, date, or budget. It may confidently send you to a BLACKPINK tribute night in Cleveland with a $400 resale ticket. The AI was plenty confident. It just had nothing real to go on. That is exactly what happens when developers test AI applications with invented traffic. The test may look reasonable. The result may even pass. But when real users arrive, with messy histories, incomplete inputs, odd request sequences, and unpredictable timing, the application has to improvise. And improvising is expensive.

Claude and Codex Are Slowing Your Engineering Team Down #speedscale #devops #aicoding #claude #codex

While AI coding tools dramatically slash development time, they are quietly inflating testing and maintenance burdens because teams no longer fully understand their codebase. Discover how leading engineering teams are shifting focus to testing and context packages to eliminate bottlenecks and unlock true AI efficiency.

Team-Based DLP: Give Each Group Its Own Redaction Rules

A shared Kubernetes cluster rarely belongs to one team. Payments runs checkout in one namespace, search runs search-api in another, and a risk team runs a scorer somewhere else. One Speedscale forwarder captures API traffic for all of them. Redacting that traffic before it leaves the cluster is what makes it safe to use for testing (the background is in The PII Testing Dilemma). Until now, that forwarder ran exactly one DLP rule. Every team that needed a field redacted had to edit the same JSON document.

Use AI and traffic replay to test AI-generated code

When I ask an AI agent to change code, I also want it to run the application and test what it changed. Asking it to write some tests is a start. But if it invents the expected responses from the same assumptions it used to write the code, those tests can miss the same mistake. Traffic replay gives the agent something concrete to test against: requests and responses captured from a working application.

Why Mocks Fail at Scale #softwareengineering #devops #softwaretesting #api #aicoding

Mocking for testing starts off easy, but once you scale to multiple teams and AI agents, handcrafted mocks become a serious form of technical liability. Instead of treating mocking as an individual software engineering task, shift your mindset to treat it as a platform engineering task focused on automation and continuously refreshed modern data. Watch to see how adopting technologies like traffic replay to simulate realistic backend sandboxes can transform your modern testing workflow!