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

yaatt

v0.0.0-test.1

Published

__

Downloads

1

Readme

Yet another api testing toolkit

Easy tests and documentation for your http api

Install

Add it globally or locally

sudo yarn global add yaatt

OR if you are barbaric,

sudo npm i -g yaatt

Usage

Creating a test suite

  • Create a file your-test.js. It is reccommended that you follow a specific directory structure for these tests.

  • The general format of a test suite is as follows

module.exports = {
    label: 'Httpbin Get call', // A label for your test suite
    url: 'http://httpbin.org/get', // API endpoint
    method: 'get', // HTTP method
    tests: {
        'should do stuff': { /* Test case */ },
    },
};

Write your first test

  • A simple test case for getting user information would look like this
module.exports = {
    label: 'Get user data',
    url: 'https://some-domain.com/api/user',
    method: 'get',
    tests: {
        'should fetch Waluigi\'s information from api': {
            params: { // Query parameters
                userid: 'ZnVjayB5b3U=',
            },
            onResponse: response =>
                response
                    .matchProp([ 'result', 'id' ], 'ZnVjayB5b3U=') // Check if user id is correct
                    .matchProp([ 'result', 'name' ], 'Waluigi')    // Check if the name is correct
                    .assert(({ data, headers, status }) => {
                        // Manual test cases go here
                    })
        },
    },
};

Running your tests

yaatt ./path/to/yourtest1.test.js ./path/to/yourtest2.test.js

You can even use glob paths

yaatt ./path/**/*.test.js