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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@granito/vitest-marbles

v1.0.0-dev.4

Published

Marble testing helpers library for RxJs and Vitest

Downloads

374

Readme

Build Latest Version

Vitest Marbles

A set of helper functions and Vitest matchers for RxJs marble testing. This library will help you to test your reactive code in easy and clean way.

Features

  • Typescript;
  • marblized error messages.

Prerequisites

Not supported

  • time progression syntax.

Usage

npm install --save-dev @granito/vitest-marbles

In the test file:

import { cold, hot, time, schedule } from '@granito/vitest-marbles';

Inside the test:

expect(stream).toBeObservable(expected);
expect(stream).toBeMarble(marbleString);
expect(stream).toHaveSubscriptions(marbleString);
expect(stream).toHaveSubscriptions(marbleStringsArray);
expect(stream).toHaveNoSubscriptions();
expect(stream).toSatisfyOnFlush(() => {
    expect(someMock).toHaveBeenCalled();
});

Examples

toBeObservable()

Verifies that the resulting stream emits certain values at certain time frames.

    it('merges two hot observables and start emitting from the subscription point', () => {
        const e1 = hot('----a--^--b-------c--|', {a: 0});
        const e2 = hot('  ---d-^--e---------f-----|', {a: 0});
        const expected = cold('---(be)----c-f-----|', {a: 0});

        expect(e1.pipe(merge(e2))).toBeObservable(expected);
    });

Sample output when the test fails (if change the expected result to '-d--(be)----c-f-----|').

Expected notifications to be:
  "-d--(be)----c-f-----|"
But got:
  "---(be)----c-f-----|"

toBeMarble()

Same as toBeObservable() but receives marble string instead.

    it('concatenates two cold observables into single cold observable', () => {
        const a = cold('-a-|');
        const b = cold('-b-|');
        const expected = '-a--b-|';

        expect(a.pipe(concat(b))).toBeMarble(expected);
    });

toHaveSubscriptions()

Verifies that the observable was subscribed in the provided time frames. Useful, for example, when you want to verify that particular switchMap() worked as expected.

    it('Should figure out single subscription points', () => {
        const x = cold('        --a---b---c--|');
        const xsubs = '   ------^-------!';
        const y = cold('                ---d--e---f---|');
        const ysubs = '   --------------^-------------!';
        const e1 = hot('  ------x-------y------|', { x, y });
        const expected = cold('--------a---b----d--e---f---|');

        expect(e1.pipe(switchAll())).toBeObservable(expected);
        expect(x).toHaveSubscriptions(xsubs);
        expect(y).toHaveSubscriptions(ysubs);
    });

The matcher can also accept multiple subscription marbles.

    it('figures out multiple subscription points', () => {
        const x = cold('                    --a---b---c--|');
        const y = cold('                ----x---x|', {x});
        const ySubscription1 = '        ----^---!';
        //                                     '--a---b---c--|'
        const ySubscription2 = '        --------^------------!';
        const expectedY = cold('        ------a---a---b---c--|');
        const z = cold('                   -x|', {x});
        //                                 '--a---b---c--|'
        const zSubscription = '            -^------------!';
        const expectedZ = cold('           ---a---b---c--|');

        expect(y.pipe(switchAll())).toBeObservable(expectedY);
        expect(z.pipe(switchAll())).toBeObservable(expectedZ);
        expect(x).toHaveSubscriptions([
            ySubscription1,
            ySubscription2,
            zSubscription
        ]);
    });

Sample output when the test fails (if change ySubscription1 to '-----------------^---!').

Expected observable to have the following subscription points:
  ["-----------------^---!", "--------^------------!", "-^------------!"]
But got:
  ["-^------------!", "----^---!", "--------^------------!"]

toHaveNoSubscriptions()

Verifies that the observable was not subscribed during the test. Especially useful when you want to verify that certain chain was not called due to an error:

    it('verifies that switchMap() was not performed due to an error', () => {
        const x = cold('--a---b---c--|');
        const y = cold('---#-x--', {x});
        const result = y.pipe(switchAll());

        expect(result).toBeMarble('---#');
        expect(x).toHaveNoSubscriptions();
    });

Sample output when the test fails (if remove error and change the expected marble to '------a---b---c--|').

Expected observable to have no subscription points
But got:
  ["----^------------!"]

toSatisfyOnFlush()

Allows you to assert on certain side effects/conditions that should be satisfied when the observable has been flushed (finished).

    it('verifies mock has been called', () => {
        const mock = vi.fn();
        const stream$ = cold('blah|').pipe(tap(mock));

        expect(stream$).toSatisfyOnFlush(() => {
            expect(mock).toHaveBeenCalledTimes(4);
        });
    });

schedule()

Allows you to schedule task on specified frame.

    it('verifies subject values', () => {
        const source = new Subject();
        const expected = cold('ab');

        schedule(() => source.next('a'), 1);
        schedule(() => source.next('b'), 2);

        expect(source).toBeObservable(expected);
    });

Credits

This repository has been forked from https://github.com/just-jeb/jest-marbles by Jenia "JeB" Barabanov and updated to use Vitest instead of Jest.