-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Customize Test Run Name #122
Comments
Thanks @sbellmercuryworks for filing this request. This is currently in our backlog, and we will share an update as soon as possible. |
@vvs11 any ETA for this feature? My company has been using this managed service in Azure since day 1 and would love to see this rolled out soon. |
I don't have an ETA yet, but this is in our near-term roadmap. I will share an update as soon as possible |
@sbellmercuryworks Thank you for reaching out to us. We have recently added the capability to customise the test run name when using the reporting feature. Please give it a try and see if it meets your needs. In parallel, we are also working on adding the capability to customise the test run name even when the reporting feature is not in use. We will keep you updated on our progress and let you know once this enhancement is available. |
To add a custom test run name, you can pass the getServiceConfig(config, {
runName: "Typescript V1 - Sample Run", // Run name for the test run
}), |
Is your feature request related to a problem? Please describe.
When looking through the list of test runs on the overview it is not clear which are tied to which run of CI or run manually. When not connected to the Microsoft Reporting feature the test run looks to follow a format of "TestRun#". When connected to Microsoft Reporting it uses the message of the last commit.
Describe the solution you'd like
I would like to pass in a custom name for a test run that will be displayed as the test run title on the overview page. This way we can use build Ids or a short name of the group of tests running and be able to quickly associate a test run to a CI run.
Describe alternatives you've considered
I have looked through the documentation to see if there is an existing feature like this but have not been able to find one at the test run level.
Additional context
Screenshot of current naming
The text was updated successfully, but these errors were encountered: