August 2025 updates

Smart subset optimization targets

As a part of the launchable subset command, we have introduced Smart subset optimization targets - giving teams more flexibility in how to compose subsets and which tests they would like to run. Now build your own subset by using tools like optimization targets, sorting rules, and filters to control which tests you would want to be a part of the generated subset.

Modify the subset command using these tools, based on your specific goals, such as:

• Ensure maximum coverage while still saving time - A mix of most likely to fail tests and the ones which haven’t been run at all recently

• Reduce noise by ignoring flaky tests - Automatically de-prioritize tests marked as flaky so they fail runs unnecessarily and distort feedback

• Prioritize recently failed tests first - Give higher weight to tests that failed in recent runs, increasing the chance of catching regressions quickly

• Pre-define important tests to include with Rule-Based Mapping - Always include tests provided by attaching a test prioritization file as a part of the command

This makes it easier to align test execution with your project’s priorities, whether that’s fast feedback, broad coverage, or reliability.

Refer our documentation on which commands are supported and how to use them.

CSV export: Flaky & Most failed tests

We also added the ability to export from the Unhealthy tests dashboard. Teams can now download a CSV of weekly lists of flaky and most failed tests, including the number of failures per test, in that selected timeframe. This makes it simpler to track recurring problematic tests and take targeted action to improve overall test suite health.

Have any questions or want to try these in your workspace? Reach out to us on smart-test-support@cloudbees.com, we’d love to walkthrough and demo these features with your team.

— The Launchable team