Link Details

Link 1151515 thumbnail
User 450924 avatar

By darthdeus
via blog.jakubarnold.cz
Published: May 09 2014 / 11:07

Before you start making any changes, make sure you have an integration test covering the part of the application you're changing. While unit tests might be useful on a small scale refactorings, they usually break if you change the layout of your code, even a little bit. This is mostly because a big portion of the unit tests will depend on the exact API of your classes, instead of their behavior.
  • 8
  • 0
  • 828
  • 764
User 1245183 avatar

tylerstrauss replied ago:

0 votes Vote down Vote up Reply

I totally agree. Unit tests are completely useless when you change the code!

User 560397 avatar

sbp_romania replied ago:

0 votes Vote down Vote up Reply

Depending on the changes done for the code, new unit tests must be created, otherwise you'd have a very bad testing outcome.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Apache Hadoop
Written by: Piotr Krewski
Featured Refcardz: Top Refcardz:
  1. Play
  2. Akka
  3. Design Patterns
  4. OO JS
  5. Cont. Delivery
  1. Play
  2. Java Performance
  3. Akka
  4. REST
  5. Java