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

nest-tsb

v0.1.1

Published

[![codecov](https://codecov.io/gh/donnyroufs/nest-tsb/branch/main/graph/badge.svg?token=T219TST5W9)](https://codecov.io/gh/donnyroufs/nest-tsb)

Downloads

5

Readme

codecov

NestJS Test Suite Builder

The goal of this library is to eliminate the necessity of duplicating setup and teardown procedures in your tests. During the development process, I found that utilizing a custom test runner greatly enhanced the API. However, I prefer to wait for native support of top-level async/await in Jest to avoid potential issues or incompatibilities that may arise in the future.

Getting Started

yarn add nestjs-tsb

Create a fixture

A fixture serves as a container for your shared configuration. Additionally, you can utilize Jest hooks within the fixture to execute top-level operations. However, please keep in mind the behavior of Jest's describe grouping when working with fixtures.

class MyFixture extends TestFixture {
  public constructor() {
    super({
      providers: [MyFakeService, Gateway],
    });
  }

  public override configureProviders = (
    builder: ITestingModuleBuilder): VoidType => 
      builder
        .overrideProvider(Gateway)
        .useClass(FakeGateway);
}

Setup your Test Suite

const myFixture = new MyFixture();
const suite = new TestSuiteBuilder(myFixture).compile();

describe("test suite should", () => {
  test("include the dependencies from the fixture", async () => {
    const service = suite.getProvider(MyFakeService);

    expect(service).toBeDefined();
    expect(service).toBeInstanceOf(MyFakeService);
  });
});

Customize your current Fixture

Please be aware that by using this approach, your other configuration will be overridden.

class CustomizedFixture extends MyFixture {
  public override configureProviders = (
    builder: ITestingModuleBuilder): VoidType => 
      builder
        .overrideProvider(Gateway)
        .useClass(NewGateway);
}

Upcoming Features

The APIs displayed here are not yet finalized; they are provided for contextual purposes.

TestContext extensions

Add metadata to your test context.

Customize your current Fixture through the builder

const myFixture = new MyFixture();
const suite = new TestSuiteBuilder(myFixture)
  .subsitute(Gateway, NewGateway)
  .compile();

Get your overrides from the suite directly

const newGateway = suite.get('gateway')
// or with some magic
const newGateway = suite.newGateway