This post originated from an RSS feed registered with Java Buzz
by Simon Brown.
Original Post: When you don't run your JUnit tests...
Feed Title: Simon Brown's weblog
Feed URL: http://www.simongbrown.com/blog/feed.xml?flavor=rss20&category=java
Feed Description: My thoughts on Java, software development and technology.
Here's my tip for the day. If you have a set of JUnit tests, always run them when delivering new code or changes to existing code. Brown's 1st law of JUnit testing says that when you don't run them for even the smallest of changes, bad things will happen. And that's exactly what happened to me today.
2 lines of code changed + a quick delivery that skipped the JUnit tests = a broken system
Note to self : always run your JUnit tests regardless of how trivial the change is. ;-)