Operations | Monitoring | ITSM | DevOps | Cloud

Rob Zuber on why getting hands-on can give every team a better understanding of developers and the problems they’re solving.

One file changed. 9,716 tests in the suite. Only 44 needed to run. See how Smarter Testing uses Test Impact Analysis to cut the unnecessary tests and get to feedback faster.

CircleCI Smarter Testing is now generally available. In this tutorial, we’ll show you how Smarter Testing helps you run fewer tests, get faster feedback, and reduce unnecessary CI compute with three capabilities: Then, we’ll put it to the test. For the same code change, a traditional pipeline ran all 9,716 tests across 15 nodes. With Smarter Testing, CircleCI identified just 44 impacted tests and skipped the other 9,672, cutting test runtime from 3 minutes and 56 seconds to 22 seconds.

The old model: build the product, then build the machine to sell it. Now? The tools might change in 48 hours. Time to learn them all over again.

Turns out telling coding agents what to do over and over again doesn't actually make them better at fixing CI failures.

When the industry moves this fast, the only way to figure it out might be by doing it yourself.

One file changed. 9,716 tests in the suite. Only 44 needed to run. See how Smarter Testing uses Test Impact Analysis to cut the unnecessary tests and get to feedback faster.

Stop manually pushing branches, hunting for logs, and pasting errors back into your editor. This video shows you how to connect Cursor to CircleCI using the CircleCI CLI so your AI agent can trigger pipelines, read build output, and fix failures autonomously without you ever leaving the IDE. In this demo, we introduce a bug, let CI catch it, and watch the agent diagnose and fix it on its own, monitoring the pipeline until it comes back green. No tab-switching. No copy-pasting logs.