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

@terrajs/mono-test-utils

v1.0.4

Published

Mono Test Utils

Downloads

8

Readme

mono-test-utils

Utils for testing your Mono project.

npm version Travis Coverage license

Installation

npm install --save-dev @terrajs/mono-test-utils

Utils

const { start, stop, $get, $post, $put, $del } = require('@terrajs/mono-test-utils')

Start a Mono project from dir directory with NODE_ENV=test:

const { app, server, conf } = await start(dir, options = {})

Default options:

{
  env: 'test',
  monoPath: '@terrajs/mono'
}

Stop Mono server:

await stop(server)

Make HTTP requests to the API:

await $get(path, options = {})
await $post(path, options = {})
await $put(path, options = {})
await $del(path, options = {}) // alias: `$delete`

Also available: $head, $options and $patch

INFO: The options are the same as request.

Every of the following methods return an object with these properties:

{
  statusCode, // HTTP status code
  headers, // Headers sent back
  body, // Body of the response
  stdout, // Logs written on stdout during the request
  stderr // Logs written on stderr during the request
}

Example

Example of test/index.js with ava:

const test = require('ava')
const { join } = require('path')

const { start, stop, $get, $post } = require('@terrajs/mono-test-utils')

let ctx

// Start server
test.before('Start Mono app', async (t) => {
	ctx = await start(join(__dirname, 'fixtures/example/'))
})

// Test API Endpoints
test('Call GET - /example', async (t) => {
	const { stdout, stderr, statusCode, body } = await $get('/example')
	t.true(stdout[0].includes('GET /example'))
	t.is(stderr.length, 0)
	t.is(statusCode, 200)
  // Imagine that GET - /example returns { hello: 'world' }
	t.deepEqual(body.body, { hello: 'world' })
})
test('Call POST - /example', async (t) => {
	const { statusCode, body } = await $post('/example', {
		body: { foo: 'bar' }
	})
	t.is(statusCode, 200)
})

// Close server
test.after('Close Mono server', async (t) => {
	await close(ctx.server)
})