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

testinha

v0.1.5

Published

Testing library for Node.js by Alexandria

Downloads

22

Readme

Testinha

npm version install size npm downloads

Routes tester for node.js

Created by: Alexandria


Installing

Using npm:

npm install testinha

Using npm as dev dependence:

npm install testinha --save-dev

Using yarn:

yarn add testinha

Using yarn as dev dependence:

yarn add testinha -D

Dependencies

How to use it

  • Starting an instance of Testinha

    const test = Testinha("https://google.com", 80);
  • Changing the base url

    test.changeBaseUrl("https://google.com");
  • Changing the port

    test.changePort("80");
  • Testing a route

    test.testOne({
      answer: { error: "No data provided" },
      url: "test",
      method: "GET",
      comparation: "EQUAL",
      params: { data: "no data" }
    }).then(res => console.log(res))
  • Testing many routes

    test.test([
      {
        answer: { error: "No data provided" },
        url: "test",
        method: "GET",
        comparation: "EQUAL",
        params: { data: "no data" }
      },
      {
        answer: "",
        url: "login",
        method: "POST",
        comparation: "TYPE",
        body: {
          email: "[email protected]",
          password: "123",
        },
      },
      {
        answer: {
          user: { name: "string", email: "string", age: "number" },
          access: "string"
        },
        url: "user",
        method: "GET",
        comparation: "INTERFACE",
        params: { email: "[email protected]" }
      }
    ])

Params explanation

  • baseURL:

    • The consistent part of the web address you want to test
  • port:

    • The port of the web address you want to test
  • answer:

    • The expected answer for the route
  • url:

    • The route you want to test
  • method:

    • The method used for the route
    • Accepted methods: GET, POST, PUT, DELETE
    • Defaults to: GET
  • comparation:

    • The type of comparation between the expected answer and the received answer
    • Accepted comparations: EQUAL, TYPE, INTERFACE
    • Defaults to: EQUAL
    • EQUAL: compares if the answers are exact the same
    • TYPE: compares if the answers are the same type (objects are considered the same no matter theirs keys)
    • INTERFACE: compares if the answer received has the exact same type as the expected answer defined (each objects keys are compared, unless the expected answer is "object")