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

testdown

v0.2.0

Published

Human-readable smoke tests for single-page web apps

Downloads

6

Readme

Testdown: browser smoke testing made easy

License: MIT

Testdown is a kind of QA robot that clicks around in your web app, following simple instructions to verify that the thing basically works.

You provide instructions in plain English. The following paragraph is an example.

Enter "banana" into the recipe search box. Wait. See some recipes. Click the recipe "banana smoothie". Look at the recipe pane. See some ingredients. See some ingredients: "banana", "peanut butter", "honey".

This approach promotes a simple kind of medium-level smoke testing that we think is valuable in addition to more rigorous testing. You can quite easily define a suite of basic tests formulated from the perspective of user expectations.

To make that paragraph work as a test for your recipe app, you only need to annotate the component nodes with a "role" attribute, like <article data-role=recipe>, and so on for each concept.

Giving definite names to user interface concepts has several benefits. Tests become cleaner from not being cluttered with arcane selector syntaxes, and by writing tests on this semantic level, you avoid coupling the suite to implementation details. Plus, it can help with establishing a ubiquitous language for talking about interface components.

Documentation

Will write more here...