|Re: Tab switch on MultiPageEditorPart / CTabFolder [message #757126 is a reply to message #757109]
||Wed, 16 November 2011 15:49
| Alexandra Schladebeck
Registered: July 2009
As far as I'm aware, the "select tab" actions used in the unbound_modules_concrete should also work on multi tab editors. The behaviour you describe in the object mapping mode is correct, as we map the whole component and select the tabs based either on name or index - excerpt from the FAQs:
Why isn't there a green border around individual tree nodes/table cells/tabbed panes/list items?
GUIdancer and Jubula support various components, e.g. trees, tables, combo boxes. When you are in the object mapping mode, these components have a green border, and can be mapped. You can only map the components supported by GUIdancer / Jubula.
If you specify a Test Step to execute an action on a tree, for example, you have to map the ''tree'' component from the application. How you navigate through the tree (where to click, what to select) is given as parameters for Test Steps.
Similarly, tabbed panes are mapped as the whole pane. To select a specific tab, enter the tab name as a parameter for a Select Tab Test Step.
The documentation for the tab actions is in the reference manual:
There is currently no dedicated action to close a tab via the X. If you don't want to write one or wait for someone else to, I'd recommend building a reusable module that selects the tab then selects close from the context menu.
Hope that helps,
Powered by FUDForum
. Page generated in 0.01756 seconds