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

@aatxxe/simple-unit-test

v1.3.0

Published

the live, love, laugh of unit tests

Downloads

10

Readme

Simple Unit Test

Simple unit tests, for simple people like me.

Note:

You're probably better off using a real testing suite. I just wanted to see if I can write my own since I've never really thought about how these things are made.

With that being said, if you insist on using this, then read on my adventurous friends...

Here's some examples:

/*
Let's run some tests baby!!!
*/
import { describe, it, expects } from '@aatxxe/simple-unit-test'
import simpleSum from './simpleSum.js'

describe('Random Math Tests', () => {
  it('1+3 should equal 4', () => {
    // you can use that sweet, sweet function you made
    expects(simpleSum(1, 3)).toBe(4)
  })
  it('1+1 should equal 2', () => {
    expects(simpleSum(1, 1)).toBe(1)
  })
  it('1+1 should not equal 1', () => {
    // or you can make a new function here and never use it again anywhere
    const sum = (a, b) => a + b
    expects(sum(1, 1)).toNotBe(1)
  })
  it('10+1 should equal 11', () => {
    const sum = (a, b) => a + b
    expects(sum(10, 1)).toBe(9)
  })
})

describe('Random Object Tests', () => {
  console.log('You can run stuff before your test block start.')
  it('should return the object {test: true}', () => {
    console.log('Even do stuff before a test runs.')
    expects({ test: true }).toBe({ test: true })
  })
  it('should not return the object {test: true}', () => {
    expects({ test: true }).toNotBe({ test: false })
    console.log('Maybe do stuff after a test runs.')
  })
  it('should not return the object {test: true}', () => {
    console.log('You can even do stuff before the test...')
    expects({ test: true }).toNotBe({ test: true })
    console.log('...and then continue that stuff after the test.')
  })
  console.log(`Maybe do stuff after the test block runs, you do you.`)
})

Run test with your pancakes.jason scripts:

{
  ...
  "scripts": {
    "test": "node node_modules/@aatxxe/simple-unit-test/run-tests.js"
  }
}

If your machine is still intact you should see some output: