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

@universal-packages/core-jest

v1.3.17

Published

Jest tooling for universal core

Downloads

10,865

Readme

Core Jest

npm version Testing codecov

Jest tooling for Universal Core testing.

Install

npm install @universal-packages/core-jest

npm install @universal-packages/core

Setup

Add the following to your jest.config.js or where you configure Jest:

module.exports = {
  setupFilesAfterEnv: ['@universal-packages/core-jest']
}

Jest Global

coreJest.runApp(name: string, [options: Object])

Run an app for all test cases in file and stop it after all tests are done.

coreJest.runApp('web-server')

it('should return the todo list', async () => {
  const result = fetch('http://localhost:4000/todos')

  expect(result.json()).toEqual({ todos: [] })
})

Options

  • args Object Arguments to pass to the app.
  • coreConfigOverride Object Override the core config for the run.

coreJest.runBare([options: Object])

Load core modules and let them be available for code that can be tested without running an app or task.

coreJest.runBare()

it('should be able to use global modules', async () => {
  const result = await MyService.doSomething()

  expect(result).toEqual('something')
})

Options

  • coreConfigOverride Object Override the core config for the run.

coreJest.execTask(name: string, [options: Object])

Runs a task on the spot use this per test case that needs to test what the task did.

it('should do something', async () => {
  await coreJest.execTask('maintain', 'deleted-users', ['fast'])

  expect(User.deleted().count()).toEqual(0)
})

Options

  • args Object Arguments to pass to the task.

  • directive string The directive to run the task with.

  • directiveOptions string[] The directive options to run the task with.

  • coreConfigOverride Object Override the core config for the run.

coreJest.runInitializer(name: string, [options: Object])

Runs an initializer on the spot use this per test case that needs to test what the initializer did.

it('should do something', async () => {
  await coreJest.runInitializer('library-initializer')

  expect(fs.existsSync('file.txt')).toEqual(true)
})

Options

  • args Object Arguments to pass to the initializer.

  • coreConfigOverride Object Override the core config for the run.

  • locationOverride string Initializers are fetched from the node_modules folder by default. For testing this is change to the ,/src folder. Since this is used for library development.

Typescript

In order for typescript to see the global types you need to reference the types somewhere in your project, normally ./src/globals.d.ts.

/// <reference types="@universal-packages/core-jest" />

This library is developed in TypeScript and shipped fully typed.

Contributing

The development of this library happens in the open on GitHub, and we are grateful to the community for contributing bugfixes and improvements. Read below to learn how you can take part in improving this library.

License

MIT licensed.