When is a Test not a Unit-test?

by

See Michael Feathers’ definition

A test is not a unit test if:

  • It talks to the database
  • It communicates across the network
  • It touches the file system
  • It can’t run at the same time as any of your other unit tests
  • You have to do special things to your environment (such as editing
    config files) to run it.

More Related Contents:

  1. What Makes a Good Unit Test? [closed]
  2. Should unit tests be written for getter and setters?
  3. What is unit testing? [closed]
  4. Mock functions in Go
  5. Should Private/Protected methods be under unit test? [closed]
  6. How to RowTest with MSTest?
  7. Visual Studio 2015 or 2017 does not discover unit tests
  8. Unit Tests not discovered in Visual Studio 2017
  9. Unit testing Anti-patterns catalogue
  10. Configuring IntelliJ IDEA for unit testing with JUnit
  11. How does mockito when() invocation work?
  12. Do MSTest deployment items only work when present in the project test settings file?
  13. Updating input html field from within an Angular 2 test
  14. Is it possible to mock a function imported from a package in golang?
  15. How do you mock a Sealed class?
  16. How can I unit test a GUI?
  17. Mock framework vs MS Fakes frameworks
  18. Should it be “Arrange-Assert-Act-Assert”?
  19. Adding unit tests to legacy code [closed]
  20. Mocking AngularJS module dependencies in Jasmine unit tests
  21. Resharper runs UnitTest from different location
  22. How to mock specific methods but not all of them in Rust?
  23. How to specify test directory for mocha?
  24. Is it possible to mock a function imported from a package?
  25. Writing “unit testable” code?
  26. Rhino Mocks – Difference between GenerateStub & GenerateMock [closed]
  27. Why is it hard to unit test a system that depends on singletons?
  28. Example code for testing the filesystem in Golang
  29. Is duplicated code more tolerable in unit tests?
  30. Why should unit tests test only one thing?

Leave a Comment