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

auto-test-file

v1.2.3

Published

Auto-generate test files in a watched folder

Downloads

16

Readme

Auto Test File

  • Auto-generate test files in a watched directory for matching extensions.
  • Ask for test specs and insert into the generated test.
  • Generate test files based on default templates or define custom templates.

atf-demo

Getting Started

Installing

  • npm install auto-test-file
  • This will provide access to the atf command which can be used to start the file watcher.

Setup

  • Add a watcher script to your package.json file, eg "atf": "atf -d 'src' -e 'ts' 'tsx'"
  • Add config settings either directly in the command line or using a config file. (See below.)
  • Use the default test file templates or replace with custom templates. (See below.)
  • Run the script, which will launch the watcher.
  • Files will be auto-generated while the script is running.
  • Index files and dot files are ignored.

Using the config file

auto-test-file can be configured either directly via the command line or using a config file. Settings passed into the command line will override config file settings.

By default, auto-test-file will look for a file named atf.config.js in the root of the project directory. The path to the file can be changed using the --config option.

Below is a sample config file:

module.exports = {
  directory: "src",
  extensions: ["ts", "tsx"],
  noSpecInput: true
};

Using Custom Test File Templates

  • Test files are generated using two templates, the describeBlock and the specBlock template.
  • The default templates, found in /src/lib/templates, can be overridden by adding a corresponding template in the config file, eg
module.exports = {
  directory: "src",
  extensions: ["ts", "tsx"],
  specTemplate: `
    test('<%= spec %>', () => {
       expect.hasAssertions();
    });
`
};
  • For templates to function, they must include the necessary properties. See the documentation in each template file for properties that are used.
  • Templates use Lodash Template - see their documentation for supported syntax.

Config Options

--config/ -c: point to a different config file than the default (atf.config.js) eg '/Users/bobsmith/my_project/foo.config.js'.

--directory/ -d: name of directory to be watched eg 'src'.

--extensions / -e: extensions for which to create test files eg 'js' 'jsx'.

--noSpecInput: do not ask for specs on add of a file.

describeTemplate: config file only. See "Using Custom Test File Templates".

specTemplate: config file only. See "Using Custom Test File Templates".

License

MIT © Anders Ramsay