question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

dotnet test doesn't respect DOTNET_CLI_UI_LANGUAGE env variable

See original GitHub issue

dotnet --info obeys the environment variable, but dotnet test doesn’t.

Steps to reproduce

I have 1251 as system default, and I want to enforce en-US for automated grepping of the test results. So your setup nessesary for issue reproduction can differ

$ export DOTNET_CLI_UI_LANGUAGE=en-US

$ echo $DOTNET_CLI_UI_LANGUAGE en-US

Expected behavior

$ dotnet test Auth.Test Build starter, please wait…

Actual behavior

$ dotnet test Auth.Test Сборка начата, подождите… Попытка отменить сборку… Попытка отменить сборку… Попытка отменить сборку… Попытка отменить сборку…

Environment data

dotnet --info output:

$ dotnet --info .NET Core SDK (reflecting any global.json): Version: 2.1.300 Commit: adab45bf0c

Runtime Environment: OS Name: Windows OS Version: 6.3.9600 OS Platform: Windows RID: win81-x64 Base Path: C:\Program Files\dotnet\sdk\2.1.300\

Host (useful for support): Version: 2.1.0 Commit: caa7b7e2ba

.NET Core SDKs installed: 2.1.200 [C:\Program Files\dotnet\sdk] 2.1.201 [C:\Program Files\dotnet\sdk] 2.1.300 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed: Microsoft.AspNetCore.All 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All] Microsoft.AspNetCore.App 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 2.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs: https://aka.ms/dotnet-download

PS: You can notice that dotnet --info respects the environmental variable.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:8 (7 by maintainers)

github_iconTop GitHub Comments

2reactions
rainersigwaldcommented, Jul 24, 2018

I’m willing to consider supporting DOTNET_CLI_UI_LANGUAGE in MSBuild – @cdmihai what do you think? Good idea/bad idea?

1reaction
nguerreracommented, Jul 31, 2018

I think there may also be a change needed in vstest. I just commented on https://github.com/Microsoft/vstest/issues/821

cc @smadala

Read more comments on GitHub >

github_iconTop Results From Across the Web

dotnet test doesn't respect DOTNET_CLI_UI_LANGUAGE ...
I have 1251 as system default, and I want to enforce en-US for automated grepping of the test results. So your setup nessesary...
Read more >
Force dotnet CLI in English on a French Windows
You can use the DOTNET_CLI_UI_LANGUAGE environment variable to override the language used by the dotnet CLI: > set DOTNET_CLI_UI_LANGUAGE=en ...
Read more >
dotnet test command - .NET CLI
The dotnet test command is used to execute unit tests in a given project. ... must be in the PATH or PROCDUMP_PATH environment...
Read more >
Most Complete MSTest Framework Tutorial Using .Net Core
Learn about the MSTest Framework using .Net Core in Selenium C# and the aspects related to cross browser testing and parallel testing in ......
Read more >
Welcome 2000 - Jan 2000 - Page 2 - Google Books Result
That's the HEST test # baby Berryman's High Energy Solvent Technology ... Preserve your future riding opportunities by showing respect for the environment, ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found