Question 1

How to set up WD.js with Sauce Labs for cloud testing?

Accepted Answer

Use wd.remote with your Sauce Labs credentials via indexed parameters or a URL string, and set environment variables SAUCE_USERNAME and SAUCE_ACCESS_KEY for authentication. Ensure desired capabilities match your target browser and OS.

Question 2

WD.js vs webdriver.io: which is better for Node.js automation?

Accepted Answer

WD.js offers more flexibility and low-level control over WebDriver, ideal for custom scripts. Webdriver.io is more opinionated with built-in test runners and reporters, better for teams wanting an all-in-one framework.

Question 3

How to handle asynchronous waits in WD.js tests?

Accepted Answer

Use built-in methods like waitFor with asserters or waitForConditionInBrowser for JavaScript conditions. First set async script timeouts with setAsyncScriptTimeout to avoid hanging, as described in the waiting utilities section.

Question 4

Can WD.js be used for mobile app testing with Appium?

Accepted Answer

Yes, it supports mobile testing via Appium for Android and iOS, locally or on cloud services like Sauce Labs. Refer to the mobile testing examples in the documentation for setup and usage.

Question 5

How to add a custom click method in WD.js?

Accepted Answer

Use wd.addPromiseChainMethod to define a new method that returns a promise for element interaction. This allows chaining similar to built-in methods, as shown in the custom method examples.

Question 6

Is WD.js compatible with Mocha and Chai assertions?

Accepted Answer

Yes, it integrates seamlessly with Mocha for test structure and Chai for assertions, especially with chai-as-promised for promise-based tests, as illustrated in the Mocha integration examples.

WD

What is WD?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions