$
The $
command is a short way to call the findElement
command in order
to fetch a single element on the page similar to the $
command from the browser scope. The difference when calling
it from an element scope is that the driver will look within the children of that element. You can also pass in an object as selector
where the object contains a property element-6066-11e4-a52e-4f735466cecf
with the value of a reference
to an element. The command will then transform the reference to an extended WebdriverIO element.
Note: chaining $
and $$
commands only make sense when you use multiple selector strategies. You will otherwise
make unnecessary requests that slow down the test (e.g. $('body').$('div')
will trigger two request whereas
$('body div')
does literally the same with just one request)
info
For more information on how to select specific elements, check out the Selectors guide.
Usage
$(selector).$(selector)
Parameters
Name | Type | Details |
---|---|---|
selector | String , Function , Matcher | selector, JS Function, or Matcher object to fetch a certain element |
Examples
- Asynchronous Mode
- Synchronous Mode
<ul id="menu">
<li><a href="/">Home</a></li>
<li><a href="/">Developer Guide</a></li>
<li><a href="/">API</a></li>
<li><a href="/">Contribute</a></li>
</ul>
it('should get text a menu link', async () => {
const text = await $('#menu');
console.log(await text.$$('li')[2].$('a').getText()); // outputs: "API"
});
it('should get text a menu link - JS Function', async () => {
const text = await $('#menu');
console.log(await text.$$('li')[2].$(function() { // Arrow function is not allowed here.
// this is Element https://developer.mozilla.org/en-US/docs/Web/API/Element
// in this particular example it is HTMLLIElement
// TypeScript users may do something like this
// return (this as Element).querySelector('a')
return this.querySelector('a'); // Element
}).getText()); // outputs: "API"
});
it('should allow to convert protocol result of an element into a WebdriverIO element', async () => {
const activeElement = await browser.getActiveElement();
console.log(await $(activeElement).getTagName()); // outputs active element
});
it('should use Androids DataMatcher or ViewMatcher selector', async () => {
const menuItem = await $({
"name": "hasEntry",
"args": ["title", "ViewTitle"],
"class": "androidx.test.espresso.matcher.ViewMatchers"
});
await menuItem.click();
const menuItem = await $({
"name": "hasEntry",
"args": ["title", "ViewTitle"]
});
await menuItem.click();
});
<ul id="menu">
<li><a href="/">Home</a></li>
<li><a href="/">Developer Guide</a></li>
<li><a href="/">API</a></li>
<li><a href="/">Contribute</a></li>
</ul>
it('should get text a menu link', () => {
const text = $('#menu');
console.log(text.$$('li')[2].$('a').getText()); // outputs: "API"
});
it('should get text a menu link - JS Function', () => {
const text = $('#menu');
console.log(text.$$('li')[2].$(function() { // Arrow function is not allowed here.
// this is Element https://developer.mozilla.org/en-US/docs/Web/API/Element
// in this particular example it is HTMLLIElement
// TypeScript users may do something like this
// return (this as Element).querySelector('a')
return this.querySelector('a'); // Element
}).getText()); // outputs: "API"
});
it('should allow to convert protocol result of an element into a WebdriverIO element', () => {
const activeElement = browser.getActiveElement();
console.log($(activeElement).getTagName()); // outputs active element
});
it('should use Androids DataMatcher or ViewMatcher selector', () => {
const menuItem = $({
"name": "hasEntry",
"args": ["title", "ViewTitle"],
"class": "androidx.test.espresso.matcher.ViewMatchers"
});
menuItem.click();
const menuItem = $({
"name": "hasEntry",
"args": ["title", "ViewTitle"]
});
menuItem.click();
});
caution
Synchronous Mode will depcrecated with Node.js v16. With an update to the underlying Chromium version it became technically impossible to provide the same synchronous behavior. We recommend to start transition to asynchronous command execution. For more information, see our RFC.