vitest-iterator

Additional vitest matchers for iterators and generators.

Installation

Pnpm: pnpm i -D vitest-iterator

Yarn: yarn add -D vitest-iterator

Npm: npm i -D vitest-iterator

Setup

Add to vitest.config.ts

1import { defineConfig } from 'vitest/config';
2
3export default defineConfig({
4  // ...
5  test: {
6    setupFiles: ['vitest-iterator'],
7  },
8});

TypeScript

Add a .d.ts file with the following triple-slash directive:

1/// <reference types="vitest-iterator/assertion" />

Alternatively, add a types entry in compilerOptions:

1{
2  "compilerOptions": {
3    "types": ["vitest-iterator/assertion"]
4  }
5}

Usage

1test('counts to three', () => {
2  const iterator = [0, 1, 2].values();
3  expect(iterator).next.toBe(0);
4  expect(iterator).next.toBe(1);
5  expect(iterator).next.toBe(2);
6  expect(iterator).next.toBeDone();
7});

.toBeDone() can be used on IteratorResult directly.

1test('counts', () => {
2  const iterator = [1, 2, 3].values();
3  const result = iterator.next();
4  expect(result).toHaveProperty('value', 0);
5  expect(result).not.toBeDone();
6});

This can be used to test generators as well since they implement the iterator protocol.

1function* exampleGenerator() {
2  yield 1;
3}
4
5test('testing generator', () => {
6  const iterator = exampleGenerator();
7  expect(iterator).next.toBe(1);
8  expect(iterator).next.toBeDone();
9});

API

.next

Also under the alias: .yields.

Use the .next modifier to unwrap the value in the IteratorResult so that any other matcher can be chained. This can be called with generators as well since they implement the iterator protocol.

Calling expect(iterator).next.toBe() is equivalent to expect(iterator.next().value).toBe().

1test('count to three', () => {
2  const iterator = [0, 1, 2].values();
3  expect(iterator).next.toBe(0);
4  expect(iterator).next.toBe(1);
5  expect(iterator).next.toBe(2);
6});

Since this modifier calls .next() on the iterator, call .next() manually instead if you want to use the result for the same iteration in any other matchers.

1test('count to three', () => {
2  const iterator = [0, 1, 2].values();
3  const result = iterator.next();
4  expect(result).toHaveProperty('value', 0);
5  expect(result).not.toBeDone();
6});

---

.toBeDone()

Use .toBeDone() to check whether an iterator is done.

1test('count is done', () => {
2  const iterator = [0].values();
3  expect(iterator).next.not.toBeDone(); // 0 is consumed here
4  expect(iterator).next.toBeDone();
5});

The IteratorResult can also be passed directly into the matcher.

1test('count is not done', () => {
2  const iterator = [0].values();
3  expect(iterator.next()).not.toBeDone();
4});