@csstools/pack-test

Pack Test

Verify that the published contents of your node package will pass a basic smoke test.
This tests creates a pack of your node modules just like npm publish and tries to import it.

Why do static analysis when you can brute force it?

API

Read the API docs

Usage

See test/_tape.mjs in the base plugin for a minimal example.

• Install this package as a dev dependency.

npm install @csstools/pack-test --save-dev

• Create a test directory in your project.

• Write some CSS that will be processed by your plugin.

/* test/basic.css */
.foo {
	color: oklch(40% 0.268735435 34.568626);
}

• Describe your test cases in a JavaScript file.

/* test/_tape.mjs */
import { postcssTape } from '@csstools/pack-test';
import plugin from '<your plugin package name>';

postcssTape(plugin)({
	basic: {
		message: "supports basic usage",
	},
	'basic:color': {
		message: "supports { color: '<a color>' }",
		options: {
			color: 'purple'
		}
	},
});

• Run the tests.

# See https://nodejs.org/docs/latest/api/test.html for more usage details.
node --test

{
	"scripts": {
		"test": "node --test"
	}
}

Browse the source code and tests here or see tests in plugins for more usage details.

[!NOTE] We use test/_tape.mjs for our tests, but you can use any file name you want.
We like to group things in a test directory and we use a leading underscore to sort it before the css files.

File name format and test case naming

Test source files and test case names are related.
The test case name is expected to be the relative file path with the .css extension removed.

Test variants (with different plugin options) are separated by a colon :.

All test files are expected to be in a test directory in the current working directory.

test case name	file name	result file name	notes
basic	test/basic.css	test/basic.result.css
basic:color	test/basic.css	test/basic.color.result.css	A variant test for basic. Everything after : is ignored.
foo/bar	test/foo/bar.css	test/foo/bar.result.css	A test file in a directory

.gitignore

We recommend adding *.result.css to your .gitignore file.
This is not functionally required, but it will reduce noise in your git history.

Quickly update all expect.css files.

Set env variable REWRITE_EXPECTS to true to update all expect.css files.

example :

{
	"scripts": {
		"test": "node --test",
		"test:rewrite-expects": "REWRITE_EXPECTS=true node --test"
	}
}