Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
@rpii/chai-webdriverio
Advanced tools
Readme
Provides webdriverio sugar for the Chai assertion library. Allows you to create expressive integration tests:
expect('.frequency-field').to.have.text('One time')
expect('.toggle-pane').to.not.be.displayed()
All assertions start with a WebdriverIO-compatible selector, for example:
expect('.list')
(CSS selector)expect('a[href=http://google.com]')
(CSS Selector)expect('//BODY/DIV[6]/DIV[1]')
(XPath selector)expect('a*=Save')
(Text selector)Then, we can add our assertion to the chain.
expect(selector).to.be.there()
- Test whether [at least one] matching element exists in the DOMexpect(selector).to.be.displayed()
- Test whether or not [at least one] matching element is displayedexpect(selector).to.have.text('string')
- Test the text value of the selected element(s) against supplied string. Succeeds if at least one element matches exactlyexpect(selector).to.have.text(/regex/)
- Test the text value of the selected element(s) against the supplied regular expression. Succeeds if at least one element matchesexpect(selector).to.have.count(number)
- Test how many elements exist in the DOM with the supplied selectorexpect(selector).to.have.value('x')
- Test that [at least one] selected element has the given valueexpect(selector).to.have.focus()
- Test that [at least one] selected element has focusYou can also always add a not
in there to negate the assertion:
expect(selector).not.to.have.text('property')
Setup is pretty easy. Just:
var chai = require('chai');
var chaiWebdriver = require('chai-webdriverio').default;
chai.use(chaiWebdriver(browser));
// And you're good to go!
browser.url('http://github.com');
chai.expect('#site-container h1.heading').to.not.contain.text("I'm a kitty!");
As an optional argument to the initializer, you can add an options
object in this format:
var options = {defaultWait: 500} // 500ms
chai.use(chaiWebdriver(browser, options));
The defaultWait
parameter will cause chai-webdriverio to wait the specified number of milliseconds
for a given selector to appear before failing (if it is not yet present on the page). You can use immediately
to skip this default wait time:
expect(selector).to.immediately.have.text('string'); // fails immediately if element is not found
Beware: For immediately
to work, your implicit wait time in WebdriverIO
must be set to 0. The immediately flag has no way to skip WebdriverIO's implicit wait.
WebdriverIO version | Compatible chai-webdriverio version |
---|---|
5.x.x | >= 1.0.0 |
4.x.x | 0.4.3 |
chai-webdriverio
version >= 1.0.0 requires Node.js 8.x
so easy.
npm # download the necessary development dependencies
npm transpile # compile ES6 into javascript
npm test # build and run the specs
Contributors:
exist
, text
assertions, documentation & test adjustmentsApache 2.0
Thanks to goodeggs for creating: chai-webdriver which inspired this module.
FAQs
Chai assertions for use with webdriverio
The npm package @rpii/chai-webdriverio receives a total of 5 weekly downloads. As such, @rpii/chai-webdriverio popularity was classified as not popular.
We found that @rpii/chai-webdriverio demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.