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

advanced-testing-kit

v1.0.1

Published

An advanced testing suite of tools. Machine Learning enhanced testing kit.

Downloads

5

Readme

atk22

JS/Node/ES - Advanced Test Kit 22

Under Development

I'm writing a test kit that can be passed a function in Node, and using a series of tools, create tests for the code.

So for instance if you want to know that a function, like isPrime from numbers-logic on npm, is running correctly, you would do something like this:

const atk = require("atk22");
const nl = require("numbers-logic").NumberTools;

nl.isPrime(3); // returns true - but is that a prime number?
nl.isPrime(4); // returns false - but is that correct?

// const atkIsPrime = atk.harness(nl.isPrime);
const testIsPrime = atk.makeTests(isPrime, {
	// The testkit will test these values FIRST to make sure your input is returning your expected output.
	returns: {
		true: [[2], [3], [5], [7]],
		false: [[0], [1], [4], [6], [8], [9]],
	},
	// The testkit will then move onto performing programatic tests using the rules you have dictated for the input
	input: [
		{
			// Uses ML to apply the rules, range and type to give a representative sample of possible inputs.
			type: [Number, String],
			// Rules are EVAL-uated
			rules: ["> 0"],
			range: ["0..10000"],
		},
	],
	advanced: {
		// If you harness the function, you will get feedback that coresponds to every variable update inside the function, allowing an in-depth examination of the function if something is going wrong, like perhaps one of the functions inside your function is failing, and not your function directly.
		harness: false,
	},
});

try {
	const testOutput = testIsPrime();
	console.log("Function isPrime is running as expected");
	console.log(testOutput); // Returns input and result values;
} catch (e) {
	console.error("Function isPrime is not running as expected");
}