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

resus-ride-runner

v0.9.38

Published

Run Resus IDE projects in cli

Downloads

45

Readme

Resus RIDE Runner

Runs exported Resus IDE tests in command line

Installation

Node.js is required to use resus-ride-runner.
The project guarantees support for the active LTS major version (e.g. 10 & 12).

NOTE: The minimum supported version of Node is now 10.15.0 LTS

yarn global add resus-ride-runner
or
npm install -g resus-ride-runner

Usage

resus-ride-runner project.ride project2.ride *.ride

Passing capabilities

resus-ride-runner -c "browserName=chrome platform=MAC"

Passing nested capabilities

resus-ride-runner -c "chromeOptions.binary='/Applications/Google Chrome.app/Contents/MacOS/Google Chrome'"

Chrome specific list capabilities (headless)

resus-ride-runner -c "chromeOptions.args=[disable-infobars, headless]"

Running on remote WebDriver server

resus-ride-runner --server http://localhost:4444/wd/hub

Filter tests

Will only run tests matching the filter resus-ride-runner --filter mytest

Changing the base URL

Change the base URL that the tests were recorded with, note that it will not affect tests that used absolute URLs. resus-ride-runner --base-url https://www.seleniumhq.org

.ride.yml

All of the configuration can be written in the .ride.yml file, the runner will load it from the current working directory automatically.

Example usage

capabilities:
  browserName: "firefox"
baseUrl: "https://www.seleniumhq.org"
server: "http://localhost:4444/wd/hub"

Advanced features

Running on multiple workers

Running tests faster through the use of multiple workers
resus-ride-runner -w 4
The runner will automatically set the number of workers to the amount of cores available, for most cases this is the best result.
Note: unless you specified that a suite is parallel, it will still run the contained tests sequentially, though the runner will run suites in parallel by default.
To mark a suite's tests as parallel, set that in the suite's settings in the IDE.

Using a proxy server

resus-ride-runner can pass proxy capabilities to the browser using the following schemes.

direct proxy

Configures WebDriver to bypass all browser proxies.
resus-ride-runner --proxy-type=direct

proxyType: direct
manual proxy

Manually configures the browser proxy.
resus-ride-runner --proxy-type=manual --proxy-options="http=localhost:434 bypass=[http://localhost:434, http://localhost:8080]"

proxyType: manual
proxyOptions:
  http: http://localhost:434
  https: http://localhost:434
  ftp: http://localhost:434
  bypass:
    - http://localhost:8080
    - http://host:434
    - http://somethingelse:32
pac proxy

Configures WebDriver to configure the browser proxy using the PAC file at the given URL.
resus-ride-runner --proxy-type=pac --proxy-options="http://localhost/pac"

proxyType: pac
proxyOptions: http://localhost/pac
socks proxy

Creates a proxy configuration for a socks proxy.
resus-ride-runner --proxy-type=socks --proxy-options="socksProxy=localhost:434 socksVersion=5"

proxyType: socks
proxyOptions:
  socksProxy: localhost:434
  socksVersion: 5
system proxy

Configures WebDriver to use the current system's proxy.
sresus-ride-runner --proxy-type=system

proxyType: system

FAQ

I'm getting an error similar to Unknown locator ${vars.something}

When running your projects make sure that the command is aware of the locator strategy before variables are evaluated.
For example click | id=${myButton} vs click | ${idOfMyButton}.
Always use the first one, since the strategy is hardcoded in the command, the second would yield an error.

But it works in the IDE.

That is because the IDE calculates locator strategies differently than the runner, it is a known current issue.