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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@keyv/test-suite

v6.1.0

Published

Test suite for Keyv API compliancy

Readme

@keyv/test-suite

Test suite for Keyv API compliance

build codecov npm npm

Complete Vitest test suite to test a Keyv storage adapter for API compliance.

Usage

Install

Install vitest, keyv and @keyv/test-suite as development dependencies.

npm install --save-dev vitest keyv @keyv/test-suite

Then update keyv and @keyv/test-suite versions to * in package.json to ensure you're always testing against the latest version.

Create Test File

test.js

import { keyvTestSuite, storageTestSuite } from '@keyv/test-suite';
import { Keyv } from 'keyv';
import { test } from 'vitest';
import KeyvStore from './src/index.js';

const store = () => new KeyvStore();
keyvTestSuite(test, Keyv, store);
storageTestSuite(test, store);

Where KeyvStore is your storage adapter. keyvTestSuite tests the adapter through a Keyv instance, and storageTestSuite tests it directly (see Storage Adapter Tests). If your adapter implements iterator(), also import and call keyvIteratorTests(test, Keyv, store).

Set your test script in package.json to vitest.

"scripts": {
  "test": "vitest"
}

Example for Storage Adapters

Take a look at keyv/redis for an example of an existing storage adapter using @keyv/test-suite.

Storage Adapter Tests

To test a storage adapter directly (without the Keyv wrapper), use storageTestSuite. It runs basic CRUD, batch, iterator, TTL, namespace, and disconnect tests against the adapter:

import { it } from 'vitest';
import { storageTestSuite } from '@keyv/test-suite';
import KeyvStore from './src/index.js';

const store = () => new KeyvStore();
storageTestSuite(it, store);

Storage Test Options

storageTestSuite (and the individual storage*Tests functions) accept an options object as the third argument:

| Option | Type | Default | Description | |--------|------|---------|-------------| | missingValue | undefined \| null | undefined | Value returned by get() for missing or expired keys | | basic | boolean | true | Enable basic CRUD tests (set/get/delete/has/clear) | | batch | boolean | true | Enable batch operation tests (setMany/getMany/hasMany/deleteMany) | | iterator | boolean | true | Enable iterator tests | | ttl | boolean | true | Enable TTL tests | | ttlGranularity | 'milliseconds' \| 'seconds' | 'milliseconds' | TTL granularity used by the TTL tests | | namespace | boolean | true | Enable namespace getter/setter test | | disconnect | boolean | true | Enable disconnect test |

TTL Granularity

By default the TTL tests use sub-second TTL values (300ms TTL with a 600ms expiry wait). Storage backends such as etcd (leases) and DynamoDB only support TTLs at second-level resolution, so they can't honor sub-second TTLs. For those adapters, set ttlGranularity: 'seconds' and the TTL tests will use second-scale values instead (1 second TTL with a 3 second expiry wait):

import { it } from 'vitest';
import { storageTestSuite } from '@keyv/test-suite';
import KeyvStore from './src/index.js';

const store = () => new KeyvStore();
storageTestSuite(it, store, { ttlGranularity: 'seconds' });

Use ttl: false only when the adapter has no storage-level TTL support at all.

Testing Compression Adapters

If you're testing a compression adapter, use compressionTestSuite instead of keyvTestSuite. It checks compress/decompress round trips and that the adapter works with a Keyv instance.

import { compressionTestSuite } from '@keyv/test-suite';
import { it } from 'vitest';
import KeyvGzip from '@keyv/compress-gzip';

compressionTestSuite(it, new KeyvGzip());

Migrating from v5

Keyv v5 adapters used @keyv/test-suite 2.x. To move to the v6 test suite:

  • There is no default export. Import keyvTestSuite and the other suites by name.
  • The first argument is Vitest's test (or it) function. Version 2.x took the whole Vitest module (import * as test from 'vitest').
  • keyvNamespaceTest is now keyvNamespaceTests.
  • keyvCompresstionTests is now compressionTestSuite.
  • New suites: storageTestSuite tests an adapter directly, without Keyv. It runs storageBasicTests, storageBatchTests, storageIteratorTests, storageTtlTests, storageNamespaceTests and storageDisconnectTests, which are also exported. encryptionTestSuite(test, adapter) and serializationTestSuite(test, adapter) test encryption and serialization adapters.

License

MIT © Jared Wray