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

htest.dev

v0.0.12

Published

<header>

Downloads

151

Readme

hTest

Declarative, boilerplate-free unit testing, for everyone.

https://htest.dev

What the hTest? Do we really need another unit testing framework?

hTest is a unit testing framework that focuses on making unit testing as quick and painless as possible. Forget copy-pasting 10 lines of boilerplate to write a single test. TDD is hard enough as it stands — the more friction in writing tests, the fewer are written. hTest aims to eliminate all boilerplate, so you can focus on the tests themselves.

hTest can be used in one of two ways: HTML-first or JS-first:

  • In JS-first mode you write your tests in nested object literals, and you can run them either in Node or in the browser. Tests inherit values they don’t specify from their parents, so you never have to repeat yourself.
    • More suitable for pure JS code.
    • Compatible with CI and other automated test running processes.
    • Code must be compatible with Node to use the Node test runner.
  • In HTML-first mode you write your tests in HTML files and run them only in the browser.
    • More suitable for UI-heavy code.
    • Pass-criteria extends beyond value matching or error catching, and could even be things like what CSS selectors match or what the DOM looks like.
    • Reactive evaluation: if the HTML changes or the user interacts with the UI, relevant tests are re-evaluated.
    • Mock interactions like click or focus with HTML attributes.

You can even mix and match the two modes in the same testsuite! E.g. even a UI-heavy library has many JS-only functions that are better tested via JS-first tests.

It is still a work in progress (soft launched), but stable enough to be used in production. The main things that still need to be done before launch are:

  • Fix CLI output glitches and improve usability (ideal would be an interactive tree that starts off collapsed)
  • Improve documentation
  • Ensure we're not missing essential things (setup/teardown?)

Sample terminal output

hTest in the wild

JS-first testsuites

HTML-first testsuites

Testsuites

Single page tests