Systems | Development | Analytics | API | Testing

Shipping software fast is easy. Shipping it fast without bugs? That’s the real test. Modern systems are API-driven, distributed, and constantly deploying – every release brings new risks. To keep defects out of production, teams rely on software quality assurance tools that automate testing, validate APIs, measure performance, and secure applications across environments.

If your 2026 resolution is to finally get AI costs under control, we've got you covered. Every January, the same resolutions show up: eat better, exercise more, finally learn that language, finally figure out that production use case for AI agents (OK, this one isn’t so typical unless you operate in our universe). But if you're responsible for your organization's AI strategy, we'd like to suggest a different one for 2026: stop letting AI be a cost center.

Consider the following: You go to the Apple Store to pick up the latest iPhone. You get home and turn it on, only to find that the screen is defective, the buttons aren’t working, and every one of the built-in apps is glitching. Thanks to QA tools, this is an extremely unlikely scenario. Before the iPhone reaches your hands, both its hardware and software have been tested repeatedly by a Quality Assurance (QA) team.

In September 2015, CareFusion issued emergency Class 1 recalls for its Alaris Syringe pumps. The pump was supposedly programmed to administer scheduled medical infusions to patients. As per official reports, due to a software code error (leading to a malfunction), the infusion pump could (or might already) have wrongly administered the scheduled medication, putting patient lives at risk. In response, the company issued recalls, regulators got involved, and the reputation damage was immediate.

AI is fundamentally reshaping software quality, and the organizations leading this shift aren’t waiting to adapt. In October 2025, we brought together over 1,000 quality engineering leaders, practitioners, and innovators for Transform, our annual conference exploring what’s next in software delivery.

When you’re building analytics for users, you quickly realize something: not every definition belongs on the Model. A lot of business logic sits in an awkward middle ground, too context-specific to hardcode into the Model but too important to leave scattered across one-off formulas. And in most tools, if the logic doesn’t live on the Model, every team ends up rebuilding the same thing over and over again. That’s where Query Sets and Column Sets in ThoughtSpot come in.