How to compare Lists in Unit Testing

by

To make assertions about collections, you should use CollectionAssert:

CollectionAssert.AreEqual(expected, actual);

List<T> doesn’t override Equals, so if Assert.AreEqual just calls Equals, it will end up using reference equality.

More Related Contents:

  1. Unit testing private methods in C#
  2. Unit Testing: DateTime.Now
  3. How can we run a test method with multiple parameters in MSTest?
  4. How do I use Assert to verify that an exception has been thrown?
  5. How do I ignore the UTF-8 Byte Order Marker in String comparisons?
  6. How can I write output from a unit test?
  7. MSTest Equivalent for NUnit’s Parameterized Tests?
  8. How do I use Assert to verify that an exception has been thrown with MSTest?
  9. MSTest cannot find the assembly
  10. Why does TestInitialize get fired for every test in my Visual Studio unit tests?
  11. How can I get “Copy to Output Directory” to work with Unit Tests?
  12. Error Message is not clear to me
  13. Using IoC for Unit Testing
  14. Interop type cannot be embedded
  15. Mocking Static Methods
  16. Mock static property with moq
  17. How to mock the new HttpClientFactory in .NET Core 2.1 using Moq
  18. Mock HttpContext for unit testing a .NET core MVC controller?
  19. How to write to Console.Out during execution of an MSTest test
  20. Visual Studio designer in x64 doesn’t work
  21. Moq + Unit Testing – System.Reflection.TargetParameterCountException: Parameter count mismatch
  22. Assert an Exception using XUnit
  23. I’m getting the “missing a using directive or assembly reference” and no clue what’s going wrong
  24. How to test method call order with Moq
  25. visual studio 2010 conditional references
  26. Test method is inconclusive: Test wasn’t run. Error?
  27. Shared AssemblyInfo for uniform versioning across the solution
  28. Using DI container in unit tests
  29. Using Moq to override virtual methods in the same class
  30. Xamarin (Android) Unit Tests in Visual Studio 2017

Leave a Comment