intake
Refresh TestArchitect’s cache of controls of a window.
| Name | Description | Type | Modifier |
|---|---|---|---|
| entity | TA name of a window, dialog or web page. | Interface Entity | None |
None
This action may be used within the following project items: test modules and user-defined actions.
entity
intake interface viewer
 
window tree node path
check tree node not exists interface viewer trv_aut #{.*"& interface entity name & ".*" & aut name &".*}/label/{.*"& unmatched entity &".*}"
 
window tree node path
check tree node exists interface viewer trv_aut #"{.*"&_interface entity name &"." & aut name1&".*}/label/{.*User name<.*}"
- Whenever your test first encounters a window that it needs to interact with, TestArchitect performs an automatic intake on the window’s controls, storing their native properties and values in cache. Under some circumstances your test may need to refresh that cache. This may occur when some action has been taken which is expected to modify the controls present in the window, or modify their properties (such as making a control visible). Use the intake action to force a refresh of the cached controls for a given window.
- For more on the intake process and what factors may warrant invoking an intake action in your test module, see Intake.
- This action supports the <ignore> modifier. If the string
<ignore>is present as the value of the argument, or the argument contains an expression that evaluates to<ignore>, the action is skipped during execution.
Tel:
Email: