---
title: Knowledge check | WebdriverIO Tutorial for Web Testing
description: Nine questions on the decisions that matter most in a real WebdriverIO
  suite. Each answer comes with a short explanation, so a wrong answer points you
  back…
source_url:
  html: https://testingbot.com/resources/courses/webdriverio/knowledge-check
  md: https://testingbot.com/resources/courses/webdriverio/knowledge-check.md
---

Course

[WebdriverIO Tutorial for Web Testing](https://testingbot.com/resources/courses/webdriverio)

Chapter 11 of 11

1. [1 WebdriverIO Tutorial: Web Testing in TypeScript](https://testingbot.com/resources/courses/webdriverio)
2. [2 Set Up a WebdriverIO Project in TypeScript](https://testingbot.com/resources/courses/webdriverio/project-setup)
3. [3 WebdriverIO Selectors: CSS, Text, Role and $$](https://testingbot.com/resources/courses/webdriverio/selectors)
4. [4 Async/Await, Auto-Waiting and Explicit Waits](https://testingbot.com/resources/courses/webdriverio/waiting)
5. [5 Assertions with expect-webdriverio](https://testingbot.com/resources/courses/webdriverio/assertions)
6. [6 Page Objects in WebdriverIO](https://testingbot.com/resources/courses/webdriverio/page-objects)
7. [7 Run WebdriverIO on TestingBot Across Browsers](https://testingbot.com/resources/courses/webdriverio/run-on-testingbot)
8. [8 Parallel Runs, Suites and Running a Subset](https://testingbot.com/resources/courses/webdriverio/parallel-and-suites)
9. [9 Reporters, Screenshots on Failure and CI](https://testingbot.com/resources/courses/webdriverio/reporters-and-ci)
10. [10 Debugging WebdriverIO Tests](https://testingbot.com/resources/courses/webdriverio/debugging)
11. [11 Knowledge check](https://testingbot.com/resources/courses/webdriverio/knowledge-check)

[Exit course](https://testingbot.com/resources/courses)

 Chapter 11 of 11 Intermediate 5 min read Updated Nov 2026 

# Knowledge check
[Watch this chapter Starts at 8:42 in the 9:06 course video.](https://www.youtube.com/watch?v=kgScgamfIDc&t=522s)

Nine questions on the decisions that matter most in a real WebdriverIO suite. Each answer comes with a short explanation, so a wrong answer points you back to the right chapter.

1. `npm init wdio` stops with "Unsupported Node.js Version" on a machine with Node.js 22.18. What do you do?

 Install an older `create-wdio` and keep the Node.js version Switch to Node.js 23, the next release Update to Node.js 22.23.4 or newer, or to a supported 24.x release Set `engines` in `package.json` to accept 22.18

WebdriverIO 10 requires recent releases of the 22, 24 and 26 lines; odd-numbered lines such as 23 are not supported. An older starter would install an older WebdriverIO, and `engines` does not change what the runtime supports.

2. A menu has three links with the class `nav-link`. `await $('.nav-link').click()` throws a `StrictSelectorError`. You want the link labelled "Pricing". What do you write?

 `await $('a=Pricing').click()` `await $('.nav-link', { strict: false }).click()` `await $$('.nav-link')[0].click()`

A tag-qualified text selector names the one element you mean and survives a reorder of the menu. Turning strictness off or indexing clicks whichever link happens to be first.

3. A selector works in Chrome but matches two elements in Firefox: the input and its label. Which kind of selector is most likely involved?

 An id selector such as `#password` An accessible name selector such as `aria/Password` A tag-qualified text selector such as `button=Login`

`aria/` matches any element with that accessible name, and how a label is counted can differ between browsers. An id or a tag-qualified selector also states what kind of element you want.

4. After clicking "Delete", a row should disappear from a table within a few seconds. Which assertion fits?

 `expect(await $('tr=Conway').isDisplayed()).toBe(false)` `await browser.pause(3000)` followed by a count of the rows `await $('tr=Conway').waitForExist()` `await expect($('tr=Conway')).not.toBeDisplayed()`

A negated WebdriverIO matcher retries until the row is gone. Reading `isDisplayed()` once checks a single moment, a pause guesses, and `waitForExist()` waits for the opposite.

5. Which page-object getter follows the WebdriverIO convention?

 `get btnSave () { return (async () => await $('#save'))() }` `btnSave = browser.findElement('css selector', '#save')` `get btnSave () { return $('#save') }`

Returning an un-awaited `$` keeps the lookup lazy: it runs, with auto-waiting, when the spec calls a command or passes it to `expect`. The protocol-level `findElement` skips all of that.

6. Your cloud config has three capabilities and four spec files, and `maxInstances: 2`. How many TestingBot sessions does a full run create, and how many run at once?

 3 sessions, all at once 12 sessions, at most 2 at a time 4 sessions, at most 2 at a time 12 sessions, all at once

Each spec file runs in its own worker for each capability, and each worker is one session: 3 times 4. `maxInstances` caps how many workers run at the same time.

7. Sessions on TestingBot are grouped correctly into a build, but all of them show an unknown result. What is missing?

 `@wdio/testingbot-service` in `services` A `name` in `tb:options` The JUnit reporter

The grid cannot see your assertions. The service reports each spec file's result to the TestingBot API when the file finishes. A name or a reporter does not change the session's state.

8. A pull request's check is red. In the TestingBot dashboard every CI run lands in the same build, so you cannot tell which sessions belong to this pull request. What do you change in the workflow?

 Add the branch name to each `describe` title Run CI with `TB_PARALLEL=1` Upload the JUnit files as an artefact Set the build name per run, for example `TB_BUILD: gha-${{ github.run_id }}`

A build name that is unique per workflow run gives each run its own build in the dashboard. Describe titles become session names, parallelism changes nothing about grouping, and the artefact lives in GitHub, not in the dashboard.

9. You are in a `browser.debug()` REPL and type `await $('h2').getText()`. You get a SyntaxError. What do you type instead?

 `browser.$('h2').getText().then(console.log)` is the only way You cannot read text in the REPL; use the video `$('h2').getText()`: the REPL resolves the promise and prints the result

The WebdriverIO REPL evaluates each line and waits for a returned promise itself, so commands are typed without `await`.

Check answers

[Previous · Chapter 10 Debugging WebdriverIO Tests](https://testingbot.com/resources/courses/webdriverio/debugging)
## You finished WebdriverIO Tutorial for Web Testing

Put what you learned into practice. Run your tests on 6100+ real browsers and physical iOS and Android devices.

[Start free trial](https://testingbot.com/users/sign_up) [See pricing](https://testingbot.com/pricing) [Browse other courses](https://testingbot.com/resources/courses)

## TestingBot WebdriverIO Certification

Turn this course into a free, resume-worthy credential: pass the exam, run the course suite on TestingBot, and get a verifiable certificate for your LinkedIn profile.

[How it works](https://testingbot.com/resources/courses/webdriverio/certification)
