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

@novaedge_apps/qa-toolkit

v0.1.13

Published

Cypress QA Toolkit for logging, cleanup, and Jira reporting

Downloads

39

Readme

@novaedge/qa-toolkit

Lightweight helper package for Cypress QA automation.
It provides a consistent logging structure for test runs and simple tools to manage logs across multiple feature files.


🚀 Installation

npm install @novaedge/qa-toolkit

or if you're using yarn:

yarn add @novaedge/qa-toolkit

🧩 Features

  • 🧹 Automatic log cleanup between runs
  • 🧾 Consistent log structure (per spec/feature)
  • ⚙️ Utility tasks for tracking test results
  • 🧠 Ready for integration with Cypress plugins and tasks

🪄 Usage

Register log tasks in Cypress

In your Cypress plugins/index.js or e2e.js (depending on Cypress version):

import { registerLogTasks } from '@novaedge/qa-toolkit';

export default (on, config) => {
  registerLogTasks(on);
  return config;
};

Log results per test

In your test files:

import { afterEachLogger } from '@novaedge/qa-toolkit';

afterEachLogger();

This ensures that each test result is appended to a structured log file for later analysis.


🧰 Command-line utilities

You can also run toolkit utilities directly from your terminal:

npx qa-toolkit clean

This will remove old logs and prepare a clean structure for a new run.


🧾 Logs

By default, logs are created under:

<your-project>/dist/logs/test-results.json

You can override this location with an environment variable:

CYPRESS_LOG_PATH=./custom-logs npm run cypress:run

🧑‍💻 Development

Clone this repository and build locally:

npm install
npm run build

Pack locally for testing:

npm pack

Then install the resulting .tgz in another project:

npm install ./novaedge-qa-toolkit-0.1.0.tgz

🧠 Troubleshooting

If logs appear in the wrong location (e.g. inside node_modules),
ensure that the logger uses process.cwd() as base directory instead of __dirname.
This guarantees logs are written to the calling project, not the package folder.


📄 License

MIT © NovaEdge