import { playwright } from '@vitest/browser-playwright'; import { defineConfig } from 'vitest/config'; import { releaseVersion } from './scripts/release-version-plugin.js'; import { scssString } from './scripts/scss-string-plugin.js'; import { svgPath } from './scripts/svg-path-plugin.js'; import { testMediaServer } from './scripts/test-media-server-plugin.js'; // Browser tests mount the real card in Chromium. They live in their own config // rather than as a fourth project in `vitest.config.ts` because `vitest run` // executes every configured project: without splitting browser tests would // become a way to satisfy the 100% per-file thresholds vs unittests. export default defineConfig({ // Tests import `src/` directly rather than a built bundle, so a test and the // card share one process and one set of objects. Vite then has to supply the // same asset shapes the Rollup build's plugins do: an SVG becomes the `{ // path, viewBox }` a custom iconset serves, SCSS becomes the string // `unsafeCSS` takes. `svgPath` is the build's own plugin, reused unchanged. plugins: [releaseVersion(), scssString(), svgPath(), testMediaServer()], resolve: { // Several dependencies declare their own Lit. Two copies in one page do not // recognise each other's directives and template results, which surfaces as // "Multiple versions of Lit loaded" followed by render-time type errors. // The build gets one copy from Rollup's resolver; Vite has to be told. dedupe: ['lit', 'lit-html', 'lit-element', '@lit/reactive-element'], }, optimizeDeps: { // `dedupe` above is not enough on its own: Vite also bundles dependencies // ahead of time, and each of those bundles carries its own copy of Lit. // Listed here, they are served as source and import the same Lit as `src/`. exclude: [ '@lit-labs/scoped-registry-mixin', '@lit-labs/task', '@lit/reactive-element', 'lit', 'lit-element', 'lit-html', ], }, server: { // Vite mirrors the page's console into the terminal, which for a mounted // card is a stream of Lit development warnings on every run. The page's // console is still intercepted in-page, where a test can assert on it. forwardConsole: false, }, css: { preprocessorOptions: { scss: { // A couple of stylesheets are pulled in by package name (e.g. `@use // '@graphiteds/core/css/core.css'`). sass resolves a bare name like // that only if node_modules is on its load path. The build passes the // same directory to `rollup-plugin-styler`. loadPaths: ['./node_modules/'], }, }, }, test: { name: 'browser', include: ['tests/**/*.browser.test.ts'], // Cosmetic: Style the pages as HA does for screenshots. setupFiles: ['./tests/browser/style.ts'], // A failing test leaves a screenshot and any attachments behind. Both // default to somewhere else -- a `__screenshots__` directory next to the // test file, and `.vitest-attachments` at the root -- so they are pointed // at one directory that `.gitignore` can name once. attachmentsDir: '.vitest/attachments', server: { deps: { // These dependencies import without extensions. // Related: https://github.com/vitest-dev/vitest/issues/2313 inline: ['ha-nunjucks', 'ts-py-datetime'], }, }, browser: { enabled: true, provider: playwright(), headless: true, // An ordinary desktop window. The default is a phone (414x896), which // would put every test on the card's narrow-screen paths and crop the // screenshot taken when one fails. viewport: { width: 1280, height: 800 }, instances: [{ browser: 'chromium' }], screenshotDirectory: '.vitest/screenshots', }, // Hide console writing to keep output clean, as the unit tests do. What // the card writes is still captured in the page, where a test can assert on // it -- a `log` action is only observable there. onConsoleLog: () => false, }, });