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

@berlund/openapicoverage

v0.0.5

Published

A simple tool for measuring test coverage on OpenApi specifications

Downloads

6

Readme

OpenApiCoverage for NodeJS

Measures code coverage in terms of calls being made to an API specified by an OpenAPI specification.

Installation

  npm install -D @berlund/openapicoverage

Usage

Just import the Code coverage class and hand over your Axios instance to it. Then point it to your OpenApi specification and you're good to go:

const axios = require('axios');
const { OpenApiCoverage } = require('@berlund/openapicoverage');

const axiosInstance = axios.create();
const coverage = OpenApiCoverage.use(axiosInstance).withSpecificationFromFile('./openapi.yaml');

Run your tests as usual, e.g.

  it('should run', async() => {
      await axiosInstance.get('https://example.com/some/path');
      await axiosInstance.get('https://example.com/some/path');
      await axiosInstance.post('https://example.com/path/to/post', {data: 'foo'});
  })

Multiple Axios instances

Multiple Axios instances can be chained:

OpenApiCoverage.use(firstAxiosInstance).use(anotherAxiosInstance)

Options for API definition

In case the path of your API calls isn't entirely defined in the API's paths but in the base path of your specification, a path prefix is accepted:

.withSpecification(path, { pathPrefix: '/v1' })

Report generation

Console

After your tests have been run, you can print a coverage report on the console.

 afterAll(() => {
    coverage.printCoverage();
  })

This will result in something like the following.

    ╔══════════════════════════════════╤════════╤════════╤═══════╗
    ║ Path                             │ Method │ Status │ Count ║
    ╟──────────────────────────────────┼────────┼────────┼───────╢
    ║ https://example.com/some/path    │ get    │ 200    │ 2     ║
    ╟──────────────────────────────────┼────────┼────────┼───────╢
    ║ https://example.com/path/to/post │ post   │ 202    │ 1     ║
    ╚══════════════════════════════════╧════════╧════════╧═══════╝

The following options will output all combinations of path, method and response status, even if they haven't been called:

coverage.printCoverage({ showZeroCounts: true })

File report

Another option is to configure a file output which is updated on every Api call:

OpenApiCoverage.use(axiosInstance, options)

where options can have the following properties:

| Property| type| Description | |------------|-------|-------------------------| | outputFormat | none | html | none disables file output (default) or simple HTML formatted output | | outputPath | string | A file path where output should be written to. Ignored if output format is set to none. Will default to the current working directory