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

chrome-test

v0.0.1

Published

web page auto test use chrome

Downloads

6

Readme

NPM

Chrome Tester

web page auto tester on chrome

Use

const Tester = require('chrome-tester');
const tester = new Tester();
await tester.init();
const job = {
  url: 'https://ke.qq.com',
  tests: [
    {
      des: 'succ test',
      script: `return true`
    },
    {
      des: 'fail test',
      script: `throw 1`
    }
  ]
}
const executor = await tester.exec(job);
executor.on('test-pass', (test, value) => {
  console.log('test-pass');
  assert.equal(test.des, 'succ test');
  assert.equal(value, true);
});
executor.on('test-failed', (test, exceptionDetails) => {
  console.log('test-failed');
  assert.equal(test.des, 'fail test');
  assert.equal(exceptionDetails.exception.value, 1);
});
await executor.wait();
await tester.destroy();
  • tester.init(): await tester be ready
  • tester.exec(job): run a test job, this will return a executor used to listen on some events
  • await executor.wait(): await until this test job has done
  • tester.destroy(): destroy this tester, close chrome, release resource

tester.exec options

  • url {string}: web page url
  • referrer {string}: http request referrer header
  • cookies {Object}: http request cookies
  • headers {Object}: http request headers
  • injectScript {string}: inject script to exec after domContentEventFired
  • tests {Array}: unit tests will run after injectScript has been inject, tests will be run one by one in order element in tests should be:
      {  
        script {string}: unit test script content,
        ... other props
      }

executor events table

  • log: chrome console out
  • test-pass: unit test exec complete
  • test-failed: unit test exec complete
  • done: exec complete
  • load-failed: page cant load
  • network-failed: Network.loadingFailed event
  • network-received: Network.loadingFailed event

see unit test for more use case.