#111 allow lifting interactions into a test
Story:
The user enters a series of commands to a fresh interactions
window. The definitions pane is open to a file containing a public
class extending TestCase. He then pushes a "make into test"
button in the interactions pane, and the interactions history is
lifted into a new JUnit test method in the TestCase class in the
definitions pane. All import and package statements are
reconciled with those at the top of the source file. All
incompatibilities between DynamicJava and regular Java syntax
are detected and reported (or fixed) before continuing. A dialog
box appears asking the user to name the new test method.
The user continues entering commands into interactions without
resetting. He then hits the "make into test" button again. All
interactions since the last time he hit the button are lifted into a
new test method, again in the open TestCase class.
If the currently open document does not contain a public class
extending TestCase, a new document is created with a new
extension of TestCase. The user is prompted to name the new
class, and the new test method is inserted into it.
It make be advisable to break this story up into a series of smaller
ones.
-- Eric
Logged In: YES
user_id=697810
What could be considered a first step in this is now
committed. There is now an action (available through the
context menu in the interactions pane or through the tools
menu) that will take the current input in the interactions
pane and write it to the definitions pane at the current
caret position.