tailwindcss/tests/plugins/backdropBrightness.test.js

import { quickPluginTest } from '../util/run'

quickPluginTest('backdropBrightness', {
  safelist: [
    // Arbitrary values
    'backdrop-brightness-[.12]',
    'backdrop-brightness-[var(--my-value)]',
  ],
}).toMatchSnapshot()
Reduce `quickPluginTest` and `quickVariantPluginTest` snapshot size (#12170) * sync package-lock.json * reduce generated examples By default we use the default config when creating the quick tests for a given plugin. However, this can result in _a lot_ of changes. For example, when you update the opacity values, then these values will be generated for each color, and for each plugin that uses that color. You can see that behaviour in Adam's PR (https://github.com/tailwindlabs/tailwindcss/pull/11832). He added 6 values to the opacity configuration. This resulted in a diff that looked like this: ``` +219,436 −9 ``` This reduces the amount of examples for plugins that generate _a lot_ of output otherwise. * use `toMatchSnapshot` This way all the `quickPluginTest` and `quickVariantPluginTest` implementations are the same. This also allows us to update tests after config changes in an easier way because they use snapshot tests right now. * use real colors for reduced red This will make it a tiny bit easier to debug what's going on if we need it in the future since it's using the same values as the real colors. 2023-10-09 16:49:20 +02:00			`import { quickPluginTest } from '../util/run'`
Ensure all built-in plugins have tests (#11618) * move `preflight` tests to `plugins` test folder * move `container` tests to `plugins` test folder * add a test that ensures that all built-in plugins have tests This is based on a few assumptions: 1. All plugins exist in the `corePlugins.js` file and are exported as `corePlugins` 2. Each exported plugin in that object has a file with a corresponding name in the current (`tests/plugins/`) folder * add dedicated plugin tests in the `plugins` folder * add a test that ensures that all built-in variant plugins have tests This is based on a few assumptions: 1. All variant plugins exist in the `corePlugins.js` file and are exported as `variantPlugins` 2. Each exported plugin in that object has a file with a corresponding name in the current (`tests/plugins/variants/`) folder * add dedicated variant plugin tests in the `plugins/variants` folder * cleanup basic usage test * move existing animation tests to animation plugin tests * move `apply-important-selector` tests to more appropriate location 2023-07-24 11:41:52 +02:00
			`quickPluginTest('backdropBrightness', {`
			`safelist: [`
			`// Arbitrary values`
			`'backdrop-brightness-[.12]',`
			`'backdrop-brightness-[var(--my-value)]',`
			`],`
Reduce `quickPluginTest` and `quickVariantPluginTest` snapshot size (#12170) * sync package-lock.json * reduce generated examples By default we use the default config when creating the quick tests for a given plugin. However, this can result in _a lot_ of changes. For example, when you update the opacity values, then these values will be generated for each color, and for each plugin that uses that color. You can see that behaviour in Adam's PR (https://github.com/tailwindlabs/tailwindcss/pull/11832). He added 6 values to the opacity configuration. This resulted in a diff that looked like this: ``` +219,436 −9 ``` This reduces the amount of examples for plugins that generate _a lot_ of output otherwise. * use `toMatchSnapshot` This way all the `quickPluginTest` and `quickVariantPluginTest` implementations are the same. This also allows us to update tests after config changes in an easier way because they use snapshot tests right now. * use real colors for reduced red This will make it a tiny bit easier to debug what's going on if we need it in the future since it's using the same values as the real colors. 2023-10-09 16:49:20 +02:00			`}).toMatchSnapshot()`