You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Loggers today allow customizing specific elements of the final report with information available within a test run. E.g., MethodFormat, TestCaseName and earlier TestSuiteName.
Can we provide a way to customize any of these with a set of well-known tokens?
E.g. dotnet test logger:"junit;$testsuite.name={assembly}{framework}" will modify name attribute in <testsuite> element.
Every config parameter that starts with a $ is considered as an element in the report. Logger will attempt to replace it with values of the token.
List of tokens
{assembly} represents name of the test assembly
{framework} is the target framework moniker used for the run, e.g., net80, net461
Loggers today allow customizing specific elements of the final report with information available within a test run. E.g.,
MethodFormat
,TestCaseName
and earlierTestSuiteName
.Can we provide a way to customize any of these with a set of well-known tokens?
E.g.
dotnet test logger:"junit;$testsuite.name={assembly}{framework}"
will modifyname
attribute in<testsuite>
element.Every config parameter that starts with a
$
is considered as an element in the report. Logger will attempt to replace it with values of the token.List of tokens
{assembly}
represents name of the test assembly{framework}
is the target framework moniker used for the run, e.g., net80, net461{arch}
is the target architectureRelated
The text was updated successfully, but these errors were encountered: