Blog Post by Itzik Saban

Writing tests for legacy code may seem risky, even daunting: will we break our code? Will we need to rewrite extensive parts of our code in order to test it? Not many know that by following fairly simple practices we can start unit-testing our codebase with minimal risks. Here are two examples of how to overcome a well known obstacle - the “initializer blocks”.

Initializer blocks

Consider the following example:


I’ve had this thought for a while now of demonstrating how can people and organizations deal with everyday situations and present an analysis of them based on my personal views, while some might find this judgmental, others may find this an interesting reflection of their behavior and explore alternatives.

For the sake of the following scenarios I will assume that we are discussing a Large Scale Scrum product, 6 feature teams, one product owner (That is you!)


Site search


Register to get notified about new blog posts

Join our long list of happy customers...

  • dt.png
  • softwareag.png
  • 3M.jpg
  • esperis.png
  • whipclip.png
  • Payoneer_logo.jpg
  • intel.png
  • logo_mellanox11.gif
  • CyberArk_logo.jpg
  • upsider.png