node-red-contrib-wdio 1.3.6
WebdriverIO nodes for Node-RED
node-red-contrib-webdriverio
Node Red nodes for Webdriver IO test framework.
Usage
The "new session" node creates a Selenium Webdriver session with the configured provider, or local Webdriver server. The session is stored at the Flow level, so can be reused by downstream webdriverIO nodes in the same flow.
If any nodes encounter an error, for example unable to locate a given element on a page, an error will be thrown. This can be caught by a global catch node and actioned appropriately.
After a flow completes, close the Selenium session using the "delete session" node. Alternatively, when Node Red exits, any open Selenium sessions will be closed.
Example flow
Basic flow example: https://github.com/rmbrich/node-red-contrib-wdio/blob/master/examples/basic.json
Local development
Follow these steps to use the nodes locally while developing or making changes (i.e. not as an npm package). This assumes you have a separate local NodeJS project that has Node Red as a dependency.
- Clone this repository locally.
- Run
yarn linkinside the project root folder. This will register "node-red-contrib-wdio" in the Yarn link registry. - Switch to your Node Red test project, then run
yarn link node-red-contrib-wdio. - Start Node Red. The Webdriver IO nodes will be available in the palette.
- After making changes in the node-red-contrib-wdio project, simply restart Node Red in your test project and the changes will be live.
To add a new node,
- Node naming should line up to the Webdriver IO Webdriver Protocol.
- Create the corresponding .html and .js files in the
srcdirectory. - If introducing a new method that could be used across multiple nodes, consider using the
wdio-common.jsmodule. - Add the new nodes to the
"nodes"object inpackage.json.
Contributing
Pull requests are welcomed for bug fixes, new nodes, and new features. Please push your changes in a branch and initiate a Pull Request against master.
Make sure the package version is incremented in package.json according to Semantic Versioning. Once a commit is merged to master, CI will automatically publish the new version to NPM.
