From: Timothy W. <tw...@oc...> - 2004-01-24 00:11:39
|
On Jan 23, 2004, at 6:07 PM, Tom Roche wrote: > Timothy Wall <tw...@us...> 01/23/2004 05:09:42 PM: > > If I can finally get around to a last few things on my TODO list, we > > can put the combined package out as 1.0 in a month or two. > > Just wondering: what's on the list? I notice the following bugs: > > 730450 Incorrect Component IDs leading to Exceptions > 785426 Actions referring to wrong components > 788830 Error recording button click These are related and should go into 1.0. The other stuff is a bit more esoteric. > > and the following FRs > > 627069 Conditional Sequence Execution/Exception Handling Maybe. Not so concerned about the how as the why, though. > 647303 Add code generation support Some Jemmy folks wanted the latter. Doesn't seem particularly useful to me, though. > 682647 right click: access to script options > 682822 copy paste steps in sequence > 683065 Time Measurement and Logging > 794838 Add ability to selectively disable portions of a script These are editor conveniences. While nice, hardly critical. Referring to the TODO list: * handle dynamic components (changing labels on JLabel, dynamically-generated menus). see the first set of bugs above * testers/recorders for remaining components. I'd like to have at least basic coverage for the things that aren't yet implemented: AWT: List, Scrollbar/Pane, TextArea/Field Swing: JColorChooser, JFileChooser, JOptionPane, JScrollbar/Pane, JSpitPane, JTableHeader, JToolBar * sensible fixture concept for running multiple scripts under the same GUI fixture. you can kinda do it now but it'd be nice to be able to run one test or many with a single fixture specification. * repair component references. update refs to reflect changes in the hierarchy. * better support for managing/editing component references in the editor The first one is the most important. The others have less widespread applicability. There will be a round of changes shortly which make component reference tags/attributes more explicit, and which make looking up components within a unit test much simpler (you won't need to construct a component reference, but rather can do something like the following): getFinder().find(new Matcher() { public boolean matches(Component c) { return c instanceof JLabel && ((JLabel)c).getText().startsWith("eat"); } }); |