3.13.6 Understanding the component hierarchy

The component hierarchy in Jubula is designed to allow flexible test specification and robust tests. For a graphical overview of the component hierarchy, see the reference manual -->Reference Manual [*].


Abstract components

Jubula lets you write tests very abstractly at the beginning, only adding detail later. You will notice that the library contains categories such as Component with Text Input and Graphics Component.

These are abstract components - actions in these categories can be used on a wide range of actual components in the AUT . You can use a Click action on the Graphics Component to click any component in the AUT . You just need to enter different component names for it in the Component Names View .


Using the same component name for different component types

What happens if you want to specify a test that clicks in a table and then selects a cell in the table?

The click action is on the Graphics Component and the select cell action is on the Table component - but you don't want to have two different component names.

This isn't a problem for Jubula . You can use the same component name for different components as long as these are compatible. So, in this case, the Graphics Component and the Table component can both use the component name e.g. TableView_MainTable_tbl.

\includegraphics[height=2cm]{danger} You cannot use the same component name for incompatible types, for example, trees and tables.

An overview of the component hierarchy can be seen in: -->Reference Manual [*].



Copyright BREDEX GmbH 2013. Made available under the Eclipse Public License v1.0.