Systems | Development | Analytics | API | Testing

The latest News and Information on Software Testing and related technologies.

What challenges was the customer facing before Katalon, and how were they testing then?

They struggled with constant production bugs, poor quality, and low automation, so much so that the VP of Engineering couldn’t unplug on weekends for fear the website might break. With only ~20% automation and frequent releases across web, mobile, and APIs, they lacked the coverage and resilience needed to prevent defects from leaking into production. — Daisy Hoang, SVP Revenue at Katalon Follow Katalon for more insights in our series!

What is an MCP? Breaking Down the Model Context Protocol

70% of teams are already integrating generative AI tools into their daily workflows, according to our 2025 State of Game Technology Report. Now more than ever, teams are looking to connect their AI tools to the services and applications they rely on to get work done. To address this issue, the industry has begun to standardize using the Model Context Protocol (MCP) to connect their existing tools and LLMs like Claude, GPT, and Gemini.

Best Practices for AI in CI/CD QA Pipelines

AI transforms CI/CD testing from reactive bug detection into proactive quality assurance that accelerates release cycles while improving software reliability. Start embedding AI into your testing workflows now because teams that wait will struggle to match the velocity of competitors who already have. Continuous integration and continuous deployment pipelines have become the backbone of modern software delivery.

Can We Still Trust the Code? #speedscale #qualityassurance #digitaltwin #trust #devops

The "Velocity Gap" is real. AI like Claude and GitHub Copilot are pumping out code faster than ever, but there’s a catch: Engineers don't trust it yet. We’re moving away from the old days of "clicking around" in a test environment, but how do we verify code at the speed of light? Ken breaks down why the future of QA isn't just "testing," it’s simulation. Video collab with @ScottMooreConsultingLLC Learn More: speedscale.com.

Top 25 Test Generating Tools

Software testing was once a slow and repetitive process that developers accepted as unavoidable, often consuming significant time without delivering proportional value. Traditional manual testing struggled to scale with growing application complexity and rapid release cycles. In 2026, test generating tools have reshaped this landscape by introducing automated test generation, AI-driven logic, and intelligent coverage strategies.

Top 9 Visual Testing Tools

Every team has experienced it at least once. A new feature ships on time, all functional tests pass, and yet users start reporting broken layouts, missing buttons, and unreadable text. The problem isn’t your business logic. The problem is your UI and functional tests can’t see it. This is where Visual Testing Tools step in as the last line of defense before your users do.

Top 45 Test Management Tools

Have you ever managed test cases in spreadsheets and struggled to track what was tested and what was missed during a release? This is exactly why modern QA teams rely on powerful test management tools to bring structure, visibility, and control into their testing process. As applications grow with microservices and CI/CD pipelines, testing becomes harder to manage. This is where test management software brings structure, visibility, and control.

Stop wasting time on Postgres migrations. #speedscale #postgresql #postgres #database #programming

If you're spinning up a whole container just for one test, you’re doing it wrong. Old way: Full DB container + pg_restore New way: speedscale + proxymock It records actual DB traffic and mocks it "on the wire." Test smarter, not harder.

The next step in your data quality program is data integrity

Many organizations run data quality programs that, on the surface, serve teams well enough. They validate data, flag missing fields, remove duplicates, and reconcile reports. Most of the time, that feels secure enough. When teams collaborate and compare datasets, discrepancies often appear but are dismissed as negligible. Fixing them is built into workflows and job descriptions, even if it takes hours or days. This approach is starting to show its age.