I think these ones should be testable quite easily - I wrote (when prompted by Stef) a series of tests for the text selection expansion commands which use a similar ast/node based inferencing - so the refactorings should be written with an ast passed to them along with cursor and text selection positioning and that is all testable. (if its not this way, we should change it so it is unit testable like this).
If I can get some time (hopefully my newish job starts to lighten up a bit), I will try and have a look if no-one else has stepped in. I'm quite passionate in making pharo more "intellij fluid-like" so we can have an enjoyable keyboard centric, and fast modern refactoring experience as we have all the right tooling to do this really well. Tim On Sun, 2 Aug 2020, at 3:45 PM, tbrunz wrote: > I found the same problem only yesterday when I tried "Extract method" in > Pharo 8 (for the first time). > > Comprehensive UI tests would be a great thing. But complicated to create. > Like writing tutorials for GUI-based applications. ;^) > > Is there a way to emulate a GUI user and the actions of mouse moves & clicks > (as well as keypresses)? And to capture the results of pointing, clicking, > right-click menu selections, etc? > > Is there a UI testing framework for Pharo that includes this? If not, > should we start building one? > > How much of the above is tied directly to Spec2 and how much is part of the > core elements of Pharo? > > -t > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >
