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

@koalati/dev-tool-tester

v2.1.0

Published

A CLI tool tester for Koalati tool developers

Downloads

8

Readme

Functional testing and debugging helper library for Koalati Tools

NPM version of @koalati/dev-tool-tester

This package allows you to easily build functional test for Koalati tools using both local files and remote web pages.

It also includes a utility executable to help Koalati tool developers run and debug their tools straight from the command line.

Getting started

If you have built your tool with the Koalati's Tool Template, this package is already specified as a dev dependency.

If you have started your tool from scratch, start by adding this package as a dev dependency:

npm i @koalati/dev-tool-tester --save-dev

Using runTool() for functional tests

To get started with your functional tests, simply require the package's runTool function in your script and provide the two following parameters:

  • Tool: your tool's class
  • url: the URL (or path to local file) you want to test your tool with

Here's a sample code snippet for a test located in the tool's /test/ directory, which also contains a sample.html file for testing purposes:

const path = require('path');
const assert = require('assert');
const runTool = require('@koalati/dev-tool-tester');
const Tool = require('../tool.js');
const testFileName = path.join(__dirname, 'sample.html');

describe('my tool', async () => {
    it('Should receive the expected results from the test tool\'s execution', async () => {
        const results = await runTool(Tool, `file:${testFileName}`);
        const expectedResults = [
			// ...
        ];
        
        assert.deepStrictEqual(results, expectedResults);
    });
});

Running and debugging your tools from the command line

If you want to run and/or debug a Koalati tool you're working on from the command line, simply navigation to that tool's directory and run the following command:

npx @koalati/dev-tool-tester --url="https://koalati.com/"

Your tool will be executed on the page provided with the --url argument, and the results will be displayed in your terminal.

If any errors occur, either during your tool's execution or because your tool's results are deemed invalid, an error message will appear to help you debug it.

Testing with local files

Both the utility executable accept local filepaths as an URL, in addition to supporting remote URLs. This can be especially useful for unit / functional tests that are bundled with your tool.