Smarter Testing is here
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.
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
CircleCI Smarter Testing Tutorial: Run Fewer Tests and Get Faster Feedback
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 software playbook doesn't work anymore
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.
More Prompts Won't Fix Your CI Failures
Turns out telling coding agents what to do over and over again doesn't actually make them better at fixing CI failures.
Our CEO is writing specs again
When the industry moves this fast, the only way to figure it out might be by doing it yourself.
Intent-driven development: How to guide agents from idea to implementation
Intent-driven development (IDD) is an approach to AI-assisted software development where teams make the desired behavior, constraints, and criteria for success explicit, then give an agent freedom to determine how to achieve the result. As agents take on larger and more autonomous development and maintenance tasks, the implementation itself becomes easier to replace. The important question is whether the software still behaves the way the team intended.
Smarter Testing is here: 9,716 tests 44
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.
How to Connect Cursor to CircleCI: AI-Powered CI/CD Debugging
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.
Being Uncomfortable Is the New Normal
CircleCI’s CRO on why this moment calls for learning faster, getting better, and embracing a little discomfort.
How to improve agent experience (AX) with CI
Improving agent experience (AX) is one thing. Keeping it good as your product changes is harder. A renamed field, different error response, or overlapping tool can turn a workflow that worked yesterday into extra retries, wasted tokens, or human intervention. CI gives teams a way to catch AX regressions as part of the development process. You can test the interfaces agents depend on, run representative agent workflows against product changes, and preserve fixed failures as regression cases.