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,
      },
    }
  }]
}

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

Full guides live in docs/ — writing tests, expecting errors, scenarios, shared context (withAspect), and the API reference.

For the underlying runner internals, refer to gwt-runner.