Mr. Eli Lopian, Typemock founder, shows how to triumph over legacy code with automated unit testing. You will learn the secrets to testing legacy code, how to introduce changes into legacy code with confidence, improve code design and write better code – faster! Unit testing legacy code may sound impractical, but that is only because you haven’t heard this session yet!
Unit testing is an effective way to achieve better code structure, long-term code efficiency and, ultimately, a faster rate of innovation. However, many projects don’t materialize out of thin air, and they are based, to some degree, on code that has been previously developed without tests. In order to achieve a good level of test coverage across the entirety of your project, tackling the issue of testing legacy code is inevitable. The good news is that Typemock, in anticipation of this industry-wide problem, has introduced the Isolator to assist coders to write pragmatic unit tests for all of their codebase.
Many developers are skeptical of unit tests, agreeing with the theoretical value but objecting to the practicality of adding a significant amount of work. Many testing approaches only feed that skepticism. Writing tests that require code changes, that tangle methods and assertions, that run inefficiently or avoid distinctly testing units, results in tests just for the sake of testing. Only an effective testing method that does not bloat your code base, does not place a high burden on the developers and does not unnecessarily slow down the process, will have a shot at wide adoption by developers. The answer is to fake dependencies, isolate the code and verify that we are making the right calls.
In this session, Eli will introduce participants to the methods of code isolation, automated testing and using unit tests to gain a better understanding of your legacy code. The session will conclude with a demonstration of how to properly, pragmatically and cost-effectively test legacy code.