Test Suite

Test suite for Keyv API compliance

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

Table of Contents

• Usage
  • Install
  • Create Test File
• Example for Storage Adapters
• Storage Adapter Tests
  • Storage Test Options
  • TTL Granularity
• Testing Compression Adapters
• Migrating from v5
• License

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:

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