Relevant for: GUI tests and components and API testing
Any testing document or resource file, including:
For GUI testing:
For API testing:
Note: In ALM, UFT One assets are referred to by the more general term entities.
Any asset stored in the ALM Test Resources module that is used by a test or component. For example, a GUI test or component may contain calls to functions in associated function libraries, and it may reference test objects stored in shared object repositories that are associated with the test or component's application area. An API test or component may contain references to a data table file or use a custom testing activity.
GUI testing resources include:
API testing resources include:
Note: In some cases, a resource can be used by another resource. For example, a GUI test's recovery scenario can use functions in a function library.
The linked relationship between a resource or external GUI action and a particular test or application area. Associated resource files and GUI actions are linked to each test or GUI component's application area that uses these resources or calls these GUI actions.
In some cases, a resource can also be linked to another resource. For example, a GUI test's recovery scenario can call functions in a function library.
Assets are considered dependencies if they are associated using absolute paths, and they are stored in the following modules:
Note: Tests or components stored in the Unattached or Obsolete folders in the Test Plan or Business Components module, respectively, are not considered dependencies because they are not associated with any test or component.
A test that is set to run from ALM with an optional data resource file and optional data filter settings. In ALM, you can define various configurations for the same test or business process test.
For tests, see Test parameterization and configurations
For components, see the Business Process Testing User Guide.