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

browserstack-testem-integration

v1.0.1

Published

Helps integrating browserstack with your testem configuration

Downloads

6

Readme

Testem with BrowserStack

Run your tests on various browsers hosted on Browserstack!

Instructions

  1. Get a BrowserStack account.
  2. Install this package npm install --save-dev browserstack-testem-integration
  3. Add start/stop and launcher configuration to your testem configuration, see instructions below and the examples in testem.json
  4. For BrowserStack Authentication export the environment variables for the username and access key of your BrowserStack account. These can be found on the automate accounts page on BrowserStack export BROWSERSTACK_USERNAME=<browserstack-username> && export BROWSERSTACK_KEY=<browserstack-access-key>

Start/Stop

You need to run the scripts start-BrowserStackLocal and stop-BrowserStackLocal, respectively when starting/stopping the test run. Put this configuration in your testem.json:

"on_start": {
  "command": "kill -9 $(ps -A | grep BrowserStackLocal | grep -v grep | cut -d ' ' -f2); $(npm bin)/start-BrowserStackLocal &",
  "wait_for_text": "Tunnel started",
  "wait_for_text_timeout": 300000
},
"on_exit": "$(npm bin)/stop-BrowserStackLocal.js `cat browserStackLocal.pid`; rm browserStackLocal.pid",

The command in on_start kills any running session of browserstack if there is one. Note: This means that you cannot run 2 concurrent test runs by the same time. Configure your CI system accordingly!

Launcher

You need to configure the launchers manually in your testem configuration. Examples are given in testem.json. It is basically using the script run_on_browserstack.js with the name of the browser as argument.

"launchers": {
  "bs_chrome": {
    "command": "$(npm bin)/run_on_browserstack Windows 10 chrome latest nil <url>",
    "protocol": "browser"
  }
}

<url> gets replaced with the proper test URL by testem.

The arguments of run_on_browserstack are

node run_on_browserstack <OS> <OS-Version> <browser> <browser-version> <device> <url>

You need to add quotes if one of the arguments contains a space (e.g. 'OS X' 'Mountain Lion'). You'll find further examples in testem.json of this repository.

Testem

Install testem globally by running npm install testem -g. This might be optional depending on your project's test suite setup.

Use testem ci -l bs_chrome to test out the setup with just the Chrome browser, configured above. Run testem ci to run it on all configured browsers - see testem launchers for the full list.

Optional: browserstack-cli

You can optionally install browserstack-cli in order to get a list of all available browsers (as opposed to testem launchers which only lists the browsers, you have configured in testem.json), devices and operating systems.

npm install -g browserstack-cli
browserstack setup # asks for your credentials and stores the information in $HOME/.browserstack
browserstack browsers | less -r