Sometimes you want to correlate the data you see in Launchable with the CI process that it came from. Usually, this involves navigating your CI system, which takes time.
Build and test session links are one solution to this. However, if you run multiple test sessions against a single build and they are all associated with the same URL in your CI system, it's hard to tell each session apart.
To solve this problem, you can now give each test session a unique name for easier disambiguation.
To name a test session, pass the
--session-name option to whichever command you use that creates a test session. This is either:
(We suggest using built-in CI environment variables to set this value.)
Then, that name will show up in the Launchable webapp in place of its ID: