Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • 4
    Does this answer your question? Where is the line between unit testing application logic and distrusting language constructs? Commented Apr 15, 2020 at 13:09
  • 17
    Dont. This class does not have any behaviour. When you are unit testing you are testing behaviour. There is none here, so there should not be any tests specifically for this class. However this class may be used in unit tests covering other classes, and as such you should probably be getting coverage from those tests? If you dont get any such coverage, then that is a sign that you either have an unused class that can be safely deleted or that you are not covering some other class with tests. Commented Apr 15, 2020 at 13:18
  • 2
    "I'm asking about this because the CodeCoverage tool is reporting 0% on all these DTO methods" - What methods? I only see properties. Commented Apr 15, 2020 at 13:19
  • @Graham, the get and sets can have code, so even though they are properties it's still a decision point. In this case it's like an empty method that doesn't have any code. Commented Apr 15, 2020 at 17:54
  • @Graham Exactly what Jon Raynor said. There's default code on the gets and sets. Granted it's not being modified from the default but I wonder if I shouldn't (as someone suggested below) add a test for a null being passed to the set. Commented Apr 16, 2020 at 15:32