One of the challenges using an automated testing tool is to organize things in a way that it
is logical enough to find something quickly, structured enough to avoid
duplication and simple enough to maintain and upgrade.
This statement is also true for Rapise objects. A common
requirement is to deal with the same objects within a flow of different test cases.
For instance, if an application has “Log In” functionality then many, many
tests will require logging-in and logging-out. Each test will have this object in
its own object tree. However this causes trouble if a change in
the application affects the recognition of the Log In object. All of the test cases will need to be updated. In
such situations it is much more convenient to have the “Log In” objects placed into their
own file and re-used by other tests.