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 🙏

© 2026 – Pkg Stats / Ryan Hefner

casper-parallel

v1.0.25

Published

Generate basic structure for modular casperjs tests running in parallel

Downloads

22

Readme

Casper-parallel

Run it or import it and call createProject();

Ex:

$ node casper-parallel/generate.js

This code will create a directory called casper-parallel for your tests. Inside it will put some basic files like a casper script to save screenshots, a casper configuration file, a server configuration file for multiple servers, a lib with some helpful functions and a node script called run.js.

The run.js file need a list of directories as parameter and will start a group of tests inside this directories in parallel using subproccess.

Ex: $ ./run.js MyFirstTestCase or $ ./run.js testDir1 testDir2 or $ ./run.js testDir*

This will create a folder for each test directory in your tmp, and will put all logs there.

To run a single test you can use the line: $ casperjs test --cookies-file=/tmp/mycookies.txt testFolder/testname.js --includes=conf.js --verbose --log-level=debug --post=screenshot.js

This will run your test in debug mode and save an image with your's test last screen.

Tips

  • To keep organization put all your data in the map.js file, never write any xpath or css selector in your test file.
  • Never write any "if" in your test file
  • If you have two cases in your test, write two tests
  • Never write a test with logic, put your logic in the lib.js
  • Try to keep your tests using a single line using casper.testElement() or casper.testElements()
  • Write more and smaller tests. They will run in parallel and this will be better and faster.