Skip to main content

Blog

AI & Automation

AI now writes a large share of the code that reaches production, and it is starting to plan, write and run the tests as well. The articles in this category look at what that changes for quality teams.

Some of them are buyer's guides. They explain how agentic AI testing platforms plan, run and maintain tests, why AI testing tools differ on two separate axes, autonomy and how much of the delivery lifecycle they cover, and what Selenium, Playwright, Cypress and Appium are each genuinely good at, including where automation cost really comes from. Others look at the governance gap that opens when software is produced faster than anyone can review it: vibe coding at enterprise scale, and code whose behaviour no human ever specified.

The thread running through all of them is that speed without verification moves risk downstream rather than removing it. Automation pays off when it starts from approved requirements, is measured against coverage and stays under human review, with every critical decision left to your team.

On RabbitQA that is the work of the Planning Agents, which generate test cases from approved requirements and show what a release actually covers, and of the Technical Agents, which run suites in parallel with self-healing and build API tests from an OpenAPI specification.