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

@batterii/generator-ts-test

v0.2.0

Published

Integration test generator for Batterii TypeScript projects

Downloads

38

Readme

@batterii/generator-ts-test

A yeoman generator for creating integration test blocks in Batterii TypeScript projects.

Usage

  yo @batterii/ts-test [options]

Options:
  -h,   --help           # Print the generator's options and usage
        --skip-cache     # Do not remember prompt answers             Default: false
        --skip-install   # Do not automatically install dependencies  Default: false
        --force-install  # Fail on install dependencies error         Default: false
  -n,   --name           # Name for the test block
  -f,   --filename       # Name for the test file (no extension)

The Test Block Name

Like all mocha tests, integration tests must be placed in a describe block. When running this generator, use the --name option to provide the name of this block.

You can name the block whatever you like, but ideally it should provide some context for the tests that will go inside it. If the tests will be exercising the API of some public class, for example, you should name the block after that class. If, on the other hand, you're applying various API's to a particular use case, you should name it after that use case.

Only letters, digits, dashes, spaces, and underscores are allowed in the test block name, simply because this subset of characters is much easier to convert to a name for the file that will be created.

You can use the the --filename option to provide the name for the test file that will be created. If you provide it, you will want to omit the extension as .ts will be appended automatically. This will default to a name based on the test block name and should not usually need to be changed.

The Created Test File

When the generator has finished, a new file will have been created in the test/integration directory. The file's name will the same as the test block name, except converted to satisfy file naming conventions. The test block name will also have '(Integration)' appended to it in the actual describe block. Both of these measures are to ensure that tests are easy to find based on the mocha reporter output alone.

Write your tests inside the generated describe block, using the already-imported chai expect API.

What about Unit Tests?

Unlike integration tests, unit tests are directly associated with a particular class or static module, so unit test files do not have their own generator. To create them, use @batterii/generator-ts-class or @batterii/generator-ts-module.