| Re: [imp-dev] Writing a function to call move method refactoring |
| Hi there, Generally, refactorings are implemented in two layers: the lower "engine" layer, and the upper UI layer. The lower layer is typically what gets tested by the regression suite. This is the approach taken by the JDT, for example. See the plugin org.eclipse.jdt.ui.refactoring.tests (on eclipse.org CVS). Yes, that plugin has "ui" in the name, but that's because it does actually spin up a runtime workbench. All the same, the refactoring tests all have the same basic flow: (1) populate workspace with resources, i.e. projects and source files, (2) instantiate an instance of the Refactoring-derived class and set any parameters, (3) apply the refactoring, and (4) check results. The dialogs/wizards/etc are not involved in the tests. For your second question, passing around an IJavaProject from the JUnit test method to the various workspace-manipulating helper methods is entirely reasonable. Hope that helps! On Feb 20, 2010, at 10:55 PM, lehmia kiran wrote: Hi all -- Cheers, - Bob ------------------------------------------------- Robert M. Fuhrer Research Staff Member Programming Technologies Dept. IBM T.J. Watson Research Center IMP Project Lead (http://www.eclipse.org/imp) X10: Productivity for High-Performance Parallel Programming (http://x10-lang.org) |