npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

webtest

v0.8.3

Published

Execute browser test in plain English

Downloads

143

Readme

webtest

Build Status Join the chat at https://gitter.im/allenhwkim/webtest

Run Web Page Test In Plain English

Principle

  1. Web browser test in plain English

    Not Javascript nor other language

  2. Test visible sections.

    Not variable, attributes, nor properties

Goal

The web browser test script should be like this;

open browser '/login'
enter text 'John' into 'username'
submit
close browser

Instead of;

var webdriver = require('selenium-webdriver'),
    until = webdriver.until;

var driver = new webdriver.Builder().forBrowser('chrome').build();

driver.get('/login');
driver.findElement({css:'input[placeholder="username"'})
  .then(function(element) {
    element.sendKeys('John');
  })
});

... even more javascript here ...

driver.quit();

Features

  • Run web browser test in plain English from command line or a file
  • Built-in chromedriver, firefox driver, and reporter
  • No need to run a selenium-server standalone jar file
  • Ability to control execution speed
  • No protractor, just test web page
  • Angular1-friendly, Angular2-friendly, Or, any framework friendly

Install

  • npm install webtest

Usage

  1. Run webtest in command line

    webtest (master)$ node index.js 
    webTestDriver is initialized as { browser: { name: 'chrome' }, timeout: 10000 }
    ? > open browser chrome
    OK
    ? > go to https://www.google.com
    OK
  2. Or, write tests in plain English. e.g., my-test-scenario.txt

    My Google
      Test Case 1
        open browser chrome
        go to http://google.com
        enter 'Allen Kim' into 'Search'
        submit
        see 'allenhwkim'
Then, and run the test file

    $ webtest my-test.txt

Core Commands

  • click link <link-text>

  • click <selector>

  • close browser

  • enter text <string> into <selector>

  • go to <url>

  • open browser <browser-name>

  • see "<text>"

  • set window position <left> <top>

  • set window size <width> <height>

  • submit

  • verify element <selector> is disabled

  • verify element <selector> is enabled

  • verify element <selector> is not selected

  • verify element <selector> is not visible

  • verify element <selector> is selected

  • verify element <selector> <style-name> is "<style-value>"

  • verify element <selector> text matches "<string>"

  • verify element <selector> text is "<string>"

  • verify element <selector> is visible

  • verify title matches "<title>"

  • verify title is "<title>"

  • verify url matches <string>

  • wait for page load

  • save value of expression <js-expression> to <variable>

  • save value of element <selector> to <variable>

  • print variable <variable>

  • verify expression <js-expression>

NOTE:

  • If webtest is run on TRAVIS CI environment, the browser is always firefox although user specify the browser in open browser command

Developer Note

$ npm install -g # to install this to run on local environment e.g., $ webtest