Should unit tests be written for getter and setters?

by

I would say no.

@Will said you should aim for 100% code coverage, but in my opinion that’s a dangerous distraction. You can write unit tests that have 100% coverage, and yet test absolutely nothing.

Unit tests are there to test the behaviour of your code, in an expressive and meaningful way, and getters/setters are only a means to an end. If you tests use the getters/setters to achieve their goal of testing the “real” functionality, then that’s good enough.

If, on the other hand, your getters and setters do more than just get and set (i.e. they’re properly complex methods), then yes, they should be tested. But don’t write a unit test case just to test a getter or setters, that’s a waste of time.

More Related Contents:

  1. What is Mocking?
  2. What Makes a Good Unit Test? [closed]
  3. What’s the difference between unit tests and integration tests? [duplicate]
  4. What is the purpose of mock objects?
  5. Should one test internal implementation, or only test public behaviour?
  6. What is unit testing and how do you do it? [duplicate]
  7. What is unit testing? [closed]
  8. What are the differences between unit tests, integration tests, smoke tests, and regression tests? [closed]
  9. How to Unit Test React-Redux Connected Components?
  10. Does Selenium support headless browser testing?
  11. Fill os.Stdin for function that reads from it
  12. How to test my servlet using JUnit
  13. Configuring IntelliJ IDEA for unit testing with JUnit
  14. Do MSTest deployment items only work when present in the project test settings file?
  15. Junit5 mock a static method
  16. How to avoid multiple asserts in a JUnit test?
  17. Unit testing with singletons
  18. Is it bad practice to have more than one assertion in a unit test? [closed]
  19. Service mocked with Jest causes “The module factory of jest.mock() is not allowed to reference any out-of-scope variables” error
  20. What is the best way to unit-test SLF4J log messages?
  21. How to unit test a Go Gin handler function?
  22. Example invalid utf8 string?
  23. Should it be “Arrange-Assert-Act-Assert”?
  24. Dependency Injection: Turtles all the way down?
  25. Is it possible to mock a function imported from a package?
  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. When is a Test not a Unit-test?

Leave a Comment