Systems | Development | Analytics | API | Testing

Writing Tests from Requirements often starts with the same decision: how many scenarios does this change actually need? The number of Tests needed for a Requirement depends on the behavior it describes. A small change may require only a few Tests, while a feature with several acceptance criteria, user roles, and possible outcomes may need a broader set. AI Test Case Generation in Xray now lets testers account for that difference before generation begins.

Every release brings new capabilities to help QA teams work more efficiently, improve collaboration, and adapt to the evolving demands of software testing. The Xray Summer '26 Product Release Webinar introduced the latest innovations across the platform, from AI-powered capabilities to usability improvements and a preview of what's coming next. Whether you joined the live session or are catching up now, this article highlights the key announcements from the webinar.

You're preparing for a release readiness meeting. The Test Plan contains hundreds of Tests. Development continued until late yesterday, several Defects were resolved overnight, and only a few hours remain before stakeholders need an update. There is enough time to execute part of the Test suite, but not all of it. The question isn't whether testing should continue. It's which Tests should be executed first. Every release forces QA teams to make prioritization decisions.