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

Shouldly.ShouldAssertException: [AzurePipelines.TestLogger.Tests.ClientMessage (x)] should be [AzurePipelines.TestLogger.Tests.ClientMessage (y)] #4

Closed
icnocop opened this issue Jan 16, 2020 · 2 comments

Comments

@icnocop
Copy link
Owner

icnocop commented Jan 16, 2020

Hi Dave.

I forked and cloned the project, but I get the following error when the tests are run:

  X CreateParents [73ms]
  Error Message:
   Shouldly.ShouldAssertException : [AzurePipelines.TestLogger.Tests.ClientMessage (-971002351)]
    should be
[AzurePipelines.TestLogger.Tests.ClientMessage (1542145733)]
    but was not
    difference
[*AzurePipelines.TestLogger.Tests.ClientMessage (-971002351)*]
  Stack Trace:
     at Shouldly.ShouldlyCoreExtensions.AssertAwesomely[T](T actual, Func`2 specifiedConstraint, Object originalActual, Object originalExpected, Func`1 customMessage, String shouldlyMethod)
   at Shouldly.ShouldBeTestExtensions.ShouldBe[T](IEnumerable`1 actual, IEnumerable`1 expected, Boolean ignoreOrder, Func`1 customMessage)
   at Shouldly.ShouldBeTestExtensions.ShouldBe[T](IEnumerable`1 actual, IEnumerable`1 expected, Boolean ignoreOrder)
   at AzurePipelines.TestLogger.Tests.LoggerQueueTests.CreateParents() in C:\github\icnocop\AzurePipelines.TestLogger\tests\AzurePipelines.TestLogger.Tests\LoggerQueueTests.cs:line 201

build.txt

The error messages aren't very helpful and so I had to debug the test to figure out which properties are actually different.

Actual Client Message Not As Expected

Windows 10 Enterprise Version 1909 (OS Build 18363.535) 64-bit
Visual Studio Enterprise 2019 16.4.1
TimeZone: PST
Locale: English - US

Thank you.

@daveaglick
Copy link
Collaborator

Finally getting around to merging these in! Thanks a lot for running this to ground all the way to a fix.

@daveaglick
Copy link
Collaborator

I was able to reproduce the failures locally and confirmed the fix - thanks again!

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