-
Notifications
You must be signed in to change notification settings - Fork 255
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
Test: use product resource string instead of hard-coded en-US string #12820
Comments
One way to solve that could be to add |
Team Triage: Tests should use resource strings when possible to allow them to be runnable on machines with different locales. |
To give more context: My machine is setup with non-English language (Polish) and non-us regional format. To get those tests run successfully without any code changes I need to:
Interestingly enough, setting environment variable |
|
I've submitted NuGet/NuGet.Client#5442 and NuGet/NuGet.Client#5441 fixing all but one tests that have been failing on my machine. The last test failing is PackageUpdateResource_SymbolSourceOnlyPushingAsync which fails due to method under test expecting exception message in English. In this case not sure if the test itself or rather method under test should be updated. |
It should be easy to clone the repo, build and test, irrespective of the current user's locale. There's at least one report that this workflow was not possible without first changing the locale to en-US. While the report lacks detail, I suspect that the problem is that some tests use hard-coded en-US strings (example) instead of using the product's resource string.
The text was updated successfully, but these errors were encountered: