Difference between revisions of "How do you unit test legacy systems?"

From CitconWiki
Jump to navigationJump to search
 
Line 1: Line 1:
 
context: organizations want to do CI and unit testing with legacy systems
 
context: organizations want to do CI and unit testing with legacy systems
  
problem: these legacy systems were not built with unit testability in mind (e.g. no IoC), scope of re-factoring/re-engineering if very limited due to constraints
+
problem: these legacy systems were not built with unit testability in mind (e.g. no IoC), scope of re-factoring/re-engineering is limited due to resource constraints
  
 
solution: use PowerMock to test the untestable
 
solution: use PowerMock to test the untestable
Line 7: Line 7:
 
Haowei talked about how [[http://www.powermock.org/][PowerMock]] can help by mocking hardwired dependencies, static methods, private methods.
 
Haowei talked about how [[http://www.powermock.org/][PowerMock]] can help by mocking hardwired dependencies, static methods, private methods.
  
sorry we didn't have a scribe or tape recorder running, please edit this with your input if you attended this session.
+
Unfortunately we didn't have a scribe or tape recorder running, please edit this with your input if you attended this session.

Latest revision as of 01:26, 26 June 2010

context: organizations want to do CI and unit testing with legacy systems

problem: these legacy systems were not built with unit testability in mind (e.g. no IoC), scope of re-factoring/re-engineering is limited due to resource constraints

solution: use PowerMock to test the untestable

Haowei talked about how [[1][PowerMock]] can help by mocking hardwired dependencies, static methods, private methods.

Unfortunately we didn't have a scribe or tape recorder running, please edit this with your input if you attended this session.