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

vitest-gwt

v0.0.3-alpha.2

Published

A small library to help Vitest support given-when-then style testing without a bunch of overhead

Downloads

6

Readme

vitest-gwt

A small library to help Vitest support given-when-then style testing without a bunch of overhead

Compatibility Chart

vitest-gwt stays in lockstep with vitest's MAJOR VERSION. If you're using [email protected], use [email protected]

Usage

  1. Install the package
    npm i --save-dev vitest-gwt
  2. In your test files, import test
    import test from 'vitest-gwt';
  3. Write a test!
    describe('test context', () => {
      test('has no expected errors', {
        given: {
          mock_vitest_test_function,
          GOOD_test_case,
        },
        when: {
          executing_test_case,
        },
        then: {
          all_GIVENS_called,
          all_WHENS_called,
          all_THENS_called,
        },
      });
    });

Scenario Test

Sometimes a GWT flow doesn't make sense. You might be writing integration tests. Or something that needs to assert something, then do another thing, then assert something else.

In these cases, you can use the scenario definition style which allows chaining when and then, followed by then_when and then blocks.

{
  given: {
    mock_vitest_test_function,
    GOOD_test_case,
  },
  scenario: [{
    when: {
      executing_test_case,
    },
    then: {
      assert_something,
    },
  }, {
    then_when: {
      user_submits_form,
    },
    then: {
      something_else_happens,
      yet_another_thing_is_true,
    },
  }, {
    then_when: {
      something_happens,
    },
    then: {
      expect_error: some_check,
      and: {
        something_is_still_true,
      },
    }
  }]
}

Disabling a test

Sometimes you want a test to be disabled in code. Vitest offers this functionality with the xtest method, and we've duplicated this logic, but with strong typing so you can disable your gwt style tests.

import test, { xtest } from 'vitest-gwt';

describe('test context', () => {
  test('this test will run', {
    then: {
      CANARY,
    },
  });

  xtest('this test will NOT run', {
    when: {
      oops_we_broke_this,
    },
  });
});

withAspect

withAspect wraps up vitest's beforeEach and afterEach to allow preparing and cleaning up the context before running tests.

withAspect(
  // this is the beforeEach. Do your prep work here
  function(this: Context) {
  },
  // this is the afterEach. It is OPTIONAL. If you need to do clean up of
  // external resources you allocated in the beforeEach, do it here
  function(this: Context) {
  }
)

The afterEach has access to whatever values you put on the Context in the beforeEach. It does NOT have access to the values put on the Context during the specific test.

Detailed Usage

Please refer to gwt-runner for detailed usage on how to write tests and clauses.