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

@bandf/framework-testing

v1.8.1

Published

Test runners and suites for the bandf framework: unit, smoke, component, a11y, e2e, and api phases.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

bandfbandf

Keywords

Readme

@bandf/framework-testing

@bandf/framework-testing supplies BandF's six test phases and the shared test API used by app specs. The framework command runs the phases in a fixed order and keeps going after a failed phase so one failure does not hide later results.

Contents

Run the suite

From a BandF workspace:

yarn test <app> <stage> <port>

The app, stage, and port are resolved through the same CLI conventions as local development. Workspace scripts may expose individual phase commands for focused work.

Test phases

| Order | Phase | What it covers | | ----- | --------- | ---------------------------------------------------------------------- | | 1 | Unit | Framework and selected-app unit and integration specs; no live server. | | 2 | Smoke | Fast browser and route checks against a live app server. | | 3 | Component | React component mounts through Playwright Component Testing. | | 4 | A11y | Browser accessibility checks with Axe. | | 5 | E2E | Browser journeys against the live app. | | 6 | API | OpenAPI linting plus generated and common Newman collections. |

Each phase runs in its own subprocess. The combined runner records a failure and continues with the remaining phases. Coverage is produced by the workspace's c8 wrapper after the subprocesses exit. There is no separate visual-regression phase.

App-owned tests

App specs live below the selected app:

apps/<app>/tests/
├── unit/
├── integration/
├── smoke/
├── component/
├── a11y/
└── e2e/

The Japa runners combine package-owned coverage with the selected app's matching directory. Component testing uses automatic discovery by default and can run manual specs from tests/component/ with the manual-mode flag.

The API phase does not require an app-owned API spec. It always exercises framework routes; when api/api.yml exists it also lints that document, generates requests for its operations, and verifies that the live endpoints remain below 500 for the baseline collection.

Live-server behavior

Smoke, accessibility, E2E, and API phases start the app through PM2 and Serverless Offline, then stop that process after the phase. These phases test the server artifact directly; they do not start Parcel or BrowserSync.

Readiness accepts any non-5xx response because authentication and route policy can legitimately return 4xx during boot probes. Persistent gateway-style 502, 503, and 504 responses are treated as a failed handler boot rather than a healthy listener.

Test API

App Japa specs import from the package root:

import { test } from "@bandf/framework-testing";

The root entry re-exports the package's @japa/runner instance. Importing through this boundary ensures specs register with the same singleton that the BandF runner executes.

@bandf/framework-testing/runner is the combined command entry. Runner subpaths are framework orchestration internals rather than the normal app-spec API.

Related links