Operations | Monitoring | ITSM | DevOps | Cloud

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.

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.

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!

Most Operational Readiness Testing (ORT) programs follow the same ritual. A checklist gets filled out. Someone runs a load test in a war room the week before launch. A failover drill gets scheduled, and everyone hopes it goes cleanly. Then the release is shipped, and testing is done. But with Harness, you can make this process continuous, and your service resilience is protected by the same ORT checklist for every small change in your SDLC.