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*

2
  • Yeah, basically the whole later looks like this with the only difference the amount of parameters the methods have and forward. My main idea was, do the "good" programmers keep writing tests for every single class, however short/simple/easy it is. I have done the model so far, I will also do the db layer as all the magic happens there - I/O of data. Thank you for your answer :) Commented May 31, 2013 at 10:39
  • Having a 100% code coverage of tests is a feather in your project's cap, but you'll spend a lot of time on getting coverage for that last 30 or 40 percent that. That less 30 percent is often boilerplate or property bag code that could be time better spent on more features or cleaning up the less trivial sections through further, deeper refactoring. Definitely thoroughly test any 'magic' code you write. Commented May 31, 2013 at 11:30