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

opentok-test-scripts

v3.9.0

Published

Testing scripts for OpenTok applications

Downloads

174

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

aullmanaullman

Keywords

karmaprotractortravisopentokwebrtcsaucelabsbrowserstackwebdriver

Readme

Build Status

OpenTok Test Scripts

This is a set of scripts which I use for various projects for testing. I use it in conjunction with travis-multirunner to test OpenTok applications. It has various helpers in there for testing WebRTC and particularly OpenTok applications.

The run-tests script uses travis-multirunner to install Chrome and Firefox on Travis based on BROWSER and BVER environment variables. If SAUCECONNECT env variable is set then it starts SauceConnect. If the BROWSERSTACK env variable is set then is starts BrowserstackLocal. It then runs your unit and integration tests. If you set the UNIT_CMD env variable then it will run that, if you set the INTEGRATION_CMD env variable then it will run that. The tests pass if both of these commands pass.

The packageSauceLabsInstaller script is used to package up a self executing plugin installer for SauceLabs. It downloads the OpenTok IE plugin and packages it up and enables fake devices (if FAKE_DEVICES is not set to 'false') and tells IE to always allow access to devices. Usage is: ./packageSauceLabsInstaller.sh PATH_TO_OPENTOK FAKE_DEVICES, eg. ./packageSauceLabsInstaller.sh https://static.opentok.com/v2 true. The idea is that this is supposed to be used as a pre-run executable for SauceLabs. An example of using it with Protractor is here. For more information on SauceLabs pre-run executables see the SauceLabs documentation.

There are some examples of karma and protractor configuration files included.

Then you can setup your .travis.yml file to look something like the .travis.yml in this repo and it will run the tests for every combination in your build matrix.

OpenTok Requirements

  • opentok-test-scripts v2 requires opentok.js v2.7+
  • opentok-test-scripts v3 requires opentok.js v2.8+