Optional configurations for your use-case

CloudBees Smart Tests uses log files from test runs to further analyze test results and help diagnose failures.

Implementation: Logs produced during test sessions can be submitted as attachments.

Here’s how the command works.

Value unlocked: - Issues dashboard (identifies new, resolved, and ongoing issues across multiple runs)

If you plan to use PTS, sending build information is critical to correlate commit data with test failures.

Implementation: To record a build, run CloudBees Smart Tests record build before creating a build in your CI script.

Here’s how the command works.

Value unlocked: - Predictive Test Selection factors in commit information to predict what tests to run.

For cases where your test results depend on the browser or runtime environment.

Implementation: When submitting test results using CloudBees Smart Tests record tests, you can submit additional metadata as key-value pairs using the --flavor option.

Here’s how the command works

Value unlocked: - Predictive Test Selection can find tailored tests to run for specific environments.

If different test suites are run against the same build, separate them into distinct “test suites” to improve data analysis across the system.

Implementation: When invoking the CloudBees Smart Tests record tests command, specify the --test-suite option and assign it a test suite name.

Here’s how the command works

Value unlocked: - Improved quality of data analysis through the platform - UI allows drill-down by test suite for detailed analysis

If builds are created by combining code from multiple repositories, this setup applies.

Implementation: Invoke CloudBees Smart Tests record build with multiple --source options to denote them.

Here’s how the command works

Value unlocked: - Enables multi-repo data correlation within a single build.

Implementation: You’ll need to manually create a test session ID to run tests.

Read this help doc further to understand setup

Implementation: Some pipelines execute multiple test runs against a build, outputting separate reports across several machines. Depending on your setup (see Test Session), you may want to merge these into a single test session.

Read this help doc further to understand setup

Implementation: Some teams run regression tests against environments where multiple services have been deployed. Each service is built from code in its own repository (or set of repositories).

Read this help doc further to understand setup