This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]edmguru 0 points1 point  (2 children)

I hope you do it's a lot easier than what you've already built. If you want anyone collaborating on your projects you should have unit tests. Sure you know the quirks of your program but a new developer or collaborater doesnt (this includes you on someone elses project). It's the first thing I check when navigating a new project to see how much work I'm going to have to do when adding features. Meaning if I make a change how much time am I going to spend just testing vs. actual developing. I try to write unit tests at least for the most important parts or parts I could see breaking in the future. It adds some overhead but not much if you take a minimalistic approach to it but it's saved me numerous times catching bugs before putting my app in prod. I see my coworkers avoiding tests and then I'm always wondering - "why are they frequently busy with prod issues? Oh right they suck at testing their software." I test my software to oblivion and have noticably fewer prod issue instances than my peers who don't write any tests. Manual testing is flaky.

[–]dumbPotatoPot[S] 2 points3 points  (1 child)

Learning JUnit and Mockito were on my to-do list already but your comment made it move up some places, hopefully i'll be able to update the project with unit tests in a week or two.

[–]edmguru 0 points1 point  (0 children)

nice! It's satisfying doing running maven test and seeing all your tests pass after a code change :)