This blog post is part of a series about legacy coderetreat<\/a> and legacy code techniques you can apply during your work. Please click to see more sessions<\/a> about legacy code.<\/p>\n This is a codecast in Java.<\/p>\n In the previous episodes we reach the moment when we extracted one simple class. We used the The Rule of Three<\/a> and pure functions<\/a>. This newly extracted class is covered with characterization tests. Then we wrote some unit tests in the following episode. But some of the behavious seemed strange, and we thought they might be bugs.<\/p>\n Because we are never sure when working on existing code if some behavior is a bug or a feature, we want to document all the suspicious cases. In order to do that, I am presenting three methods: use an annotation, prefix the test, use a different class.<\/p>\n Bug or feature? Check out the codecast to see all of them in action.<\/p>\n Read here<\/a> more about this concept in my blog post.<\/p>\nCode Cast<\/h3>\n
\n