The CmdLine step within CI AzDo pipelines should be called something like ctest to indicate it is running unit tests

[ahsonkhan]

https://dev.azure.com/azure-sdk/public/_build/results?buildId=1184446&view=logs&j=e109b754-e5a4-58aa-96d5-f28daf32bc3c&t=b284fc23-d415-5680-f742-99295c9bb1ab

ctest -C Debug -V --tests-regex azure-core. --no-compress-output -T Test

It took some digging to realize this is the step that was running unit tests, and the leg name wasn't self-descriptive.

For example, in Embedded C, we call this step ctest:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1184185&view=logs&j=bd7cfc7a-9e05-507b-5103-65c9a747e93d&t=fc133eb2-b3d7-538b-7035-e429cbd6b68c

cc @danieljurek

[ahsonkhan]

For some reason the display name is not being picked up:

azure-sdk-for-cpp/eng/pipelines/templates/jobs/ci.tests.yml

Line 140 in 198327e

displayName: Test

azure-sdk-for-cpp/eng/pipelines/templates/jobs/archetype-sdk-tests.yml

Lines 201 to 203 in 52e0eeb

	- script: ctest -C Debug --tests-regex ${{ parameters.CtestRegex }} --no-compress-output -T Test
	workingDirectory: build
	displayName: ctest

[ahsonkhan]

Re-running the legs in CI, now I do start seeing Test from the display name:
https://dev.azure.com/azure-sdk/public/_build/results?buildId=1185097&view=logs&j=117dcd10-cb90-5257-bbaf-0e8ca4e59cfe&t=dcc291b6-090f-5e15-b262-6c0eab2f9bdc

Looks like this PR fixed the issue, by adding the missing displayName field :)
#3079

Feel free to close, if fixed 😊