Inspecting the Contents of the Page
The Selenium namespace contains a number of functions which manipulate the browser in various ways (see the next section for details).
R←IsVisible id
The boolean result R indicated whether or not the control with the given id is visible or not.
Note
It might be interesting to combine IsVisible and Retry to wait until a dynamic element becomes visible.
html←PageSource
You can verify whether the page has been correctly loaded by inspecting the PageSource, for example:
∨/'<link href="/Styles/tryapl.css"'⍷Selenium.BROWSER.PageSource
{ok}←(fn Retry) arg
Following any action, an unknown amount of time may pass before the server responds and a response is detectable in the browser. The Retry operator is provided to allow waiting for an expected effect. The time to wait is controlled by the variable Selenium.DEFAULTRETRYLIMIT . Retry invokes fn on arg, and retries until the result is true, or DEFAULTRETRYLIMIT seconds have passed.
For example:
{(Find 'result').Text=⍵} Retry 'You pressed the button!'
Retry returns the result of the final application of the function.
SaveScreenshot filename
see separate page
R←Text id
Returns the text displayed in control id. In contrast to Selenium's internal functions this works for all types of controls.
{msg}←element WaitFor text [message]
The left argument can be the id or a reference to an element to be tested or a two element vector containing the left and right arguments of the Find function. WaitFor will use Retry to wait until the element in question contains the specified text anywhere within its Text property. If the element is of type input, (element.GetAttribute⊂'value') is tested instead.
For example:
'result' WaitFor 'Welcome!'