Skip to content
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

Repos\moq4\tests\Moq.Tests\MatchExpressionFixture.cs:row 21 #828

Closed
connywesth opened this issue May 12, 2019 · 2 comments
Closed

Repos\moq4\tests\Moq.Tests\MatchExpressionFixture.cs:row 21 #828

connywesth opened this issue May 12, 2019 · 2 comments

Comments

@connywesth
Copy link

This is an errormessage I got out-of-the-box when i run run moq.tests in Visual Studio Community 2017. I have just downloaded the latest version from GitHub (May 12, 2019).
MoqErroeSnapShot

ERROR MESSAGE (Some phrases translated from Swedish to English for clarity):
Test Name: Moq.Tests.MatchExpressionFixture.Prevents_compilation
Test FullName: Moq.Tests.MatchExpressionFixture.Prevents_compilation
Test Source: F:\Timecut\Repos\moq4\tests\Moq.Tests\MatchExpressionFixture.cs : line 17
Test Outcome: Failed
Test Duration: 0:00:00,031

Result StackTrace:
vid Xunit.Assert.Contains(String expectedSubstring, String actualString) i C:\Dev\xunit\xunit\src\xunit.assert\Asserts\StringAsserts.cs:row 22
vid Moq.Tests.MatchExpressionFixture.Prevents_compilation() i F:\Repos\moq4\tests\Moq.Tests\MatchExpressionFixture.cs:row 21
Result Message:
Assert.Contains() Failure
Not found: reducible
In value: must be a reduceable node

@stakx
Copy link
Contributor

stakx commented May 12, 2019

Some phrases translated from Swedish to English for clarity

Unfortunately, this obscures the precise cause of the error you're reporting:

Not found: reducible
In value: must be a reduceable node

Was the last line translated by you? What was the original error message?

If the error is caused by a Swedish installation of .NET, which reports errors in the Swedish language, do you have any suggestions how to deal with this error source in general (other than simply not testing the messages at all)?

@stakx
Copy link
Contributor

stakx commented May 27, 2019

Closing to due lack of a response.

@stakx stakx closed this as completed May 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants