Page ​

A page in the object repository is a named path used by navigation steps. It lets multiple autotests reuse one project path instead of storing the path inline in every step.

Relations ​

Fields ​

Rules ​

• Pages and elements use separate catalogs. A folder has kind PAGE or ELEMENT and cannot mix both.
• Create folders in the Pages tree. A page may sit in a folder or have no folder.
• At the tree root the table lists all pages in the project. Open a folder to list only pages in that folder.
• Drag a page from the table onto a folder in the tree to move it, including onto an empty folder. After the drop the page stays visible inside that folder.
• The stored path follows the same rules as the Value of goto.
• A relative path starts from the team domain and protocol selected for the autotest run (the starting domain), even if a previous COMMON step already opened a subdomain.
• Use a full URL when the target screen lives on a different host than the starting domain (a team subdomain when the run starts on the root). The host must be covered by a verified team domain.
• When an autotest step selects a catalog page, the worker resolves it to the stored path at run time.
• A page cannot use the TEST_ACCOUNT value source on the same step.

Limits ​

• The page stores navigation data. It does not store element locators.
• localhost and similar reserved hosts are not accepted as starting domains.
• Navigation to another host requires a matching verified team domain.