Skip to content

Change test display names in Azure Dev Ops #10002

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

Closed
vzarytovskii opened this issue Aug 25, 2020 · 1 comment
Closed

Change test display names in Azure Dev Ops #10002

vzarytovskii opened this issue Aug 25, 2020 · 1 comment
Labels
Area-Testing Impact-Low (Internal MS Team use only) Describes an issue with limited impact on existing code.

Comments

@vzarytovskii
Copy link
Member

vzarytovskii commented Aug 25, 2020

Right now, in Azure DevOps all the test categories look like "NUnit_TestResults_xxxxx_x", which is quite unreadable, and hard to see what's failing and where.
It needs to be fixed to have following structure (or close to it):

 Windows
 ├── netcoreapp3.1
 │      ├──  TestSuite1 (e.g. FSharp.Test.Compiler.ComponentTests)
 │      ├──  TestSuite2
 │      └──  ...          
 └── net472

 Linux
 └── netcoreapp3.1
        ├──  TestSuite1 (e.g. FSharp.Test.Compiler.ComponentTests)
        ├──  TestSuite2
        └──  ...          

 macOS
 └── netcoreapp3.1
        ├──  TestSuite1 (e.g. FSharp.Test.Compiler.ComponentTests)
        ├──  TestSuite2
        └──  ...          

This will allo wto easier pinpoint which test is failing on which platform.

@vzarytovskii vzarytovskii added this to the Testing Overhaul milestone Aug 25, 2020
@KevinRansom KevinRansom added the Impact-Low (Internal MS Team use only) Describes an issue with limited impact on existing code. label Jul 21, 2021
@dsyme dsyme changed the title [Test Framework] Change test display names in AzDo Change test display names in Azure Dev Ops Apr 20, 2022
@vzarytovskii vzarytovskii moved this to Not Planned in F# Compiler and Tooling Jun 17, 2022
@majocha
Copy link
Contributor

majocha commented Apr 28, 2025

This is more or less done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Testing Impact-Low (Internal MS Team use only) Describes an issue with limited impact on existing code.
Projects
Archived in project
Development

No branches or pull requests

4 participants