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

a1-test

v2.0.4

Published

test html files in one line

Downloads

9

Readme

a1-test

test html files in one line

Testing web apps is a tedius task. Automate web tests can consume a lot of effort. This package saves precious time by allowing a really easy way to test a set of web pages.

The test will take a folder of html pages as input and it will run a headless chrome on them. If any console.error is captured on the page, the test is failed.

The test can also check external urls, use the depth parameter to browse around related pages. For devs: use https://developers.google.com/web/updates/2017/04/headless-chrome as tutorial and https://chromedevtools.github.io/devtools-protocol as reference

To test all the html files in a local folder:

const test = require('a1-test')
try {
  const folder = '/home/steven/myApp' // index.html, landing.html, details/index.html ...  
  await test.folder(folder) // also test.folder(folder, '/usr/lib/chromium-browser/chromium-browser')
  assert.ok(true,'tests passed')
} catch (e) {
  assert.fail(e.toString())
}

To test url and related pages, use the url(). The test will look for related tags, so use a depth parameter to limit the pages to test.

const test = require('a1-test')
try {
  await test.url('http://google.com', '/usr/lib/chromium-browser/chromium-browser', 1)
  assert.ok(true,'tests passed')
} catch (e) {
  assert.fail(e.toString())
}

For devs:

Fork the github project and customize by following these links:

  • https://developers.google.com/web/updates/2017/04/headless-chrome
  • https://chromedevtools.github.io/devtools-protocol/