@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-toolkitor 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 cleanThis 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.jsonYou 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 buildPack locally for testing:
npm packThen 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
