Unit Tests not discovered in Visual Studio 2017

by

In my case, it turned out that I simply had to upgrade my test adapters and test framework. Done.

Example using the NuGet Package Manager:

enter image description here

More Related Contents:

  1. Visual Studio 2015 or 2017 does not discover unit tests
  2. What’s the difference between faking, mocking, and stubbing?
  3. What is the difference between integration and unit tests?
  4. How deep are your unit tests?
  5. When should I mock?
  6. Should unit tests be written for getter and setters?
  7. NUnit vs. MbUnit vs. MSTest vs. xUnit.net [closed]
  8. Unit test naming best practices [closed]
  9. How to start working with GTest and CMake
  10. Should Private/Protected methods be under unit test? [closed]
  11. How do I unit-test saving file to the disk?
  12. How to RowTest with MSTest?
  13. Unit testing Anti-patterns catalogue
  14. Configuring IntelliJ IDEA for unit testing with JUnit
  15. How does mockito when() invocation work?
  16. Updating input html field from within an Angular 2 test
  17. How to avoid multiple asserts in a JUnit test?
  18. Is it possible to mock a function imported from a package in golang?
  19. How do you mock a Sealed class?
  20. How can I unit test a GUI?
  21. Mock framework vs MS Fakes frameworks
  22. Adding unit tests to legacy code [closed]
  23. Mocking AngularJS module dependencies in Jasmine unit tests
  24. Resharper runs UnitTest from different location
  25. How to mock specific methods but not all of them in Rust?
  26. Unit testing code with a file system dependency
  27. What is a “Stub”?
  28. F# development and unit testing? [closed]
  29. Testing route configuration in ASP.NET WebApi
  30. how do I mock sqlconnection or should I refactor the code?

Leave a Comment