Testing Blocks

You validate code changes before a PR by running unit tests with Vitest and jsdom to verify logic-heavy utilities. This workflow ensures standardized testing across blocks and utilities to maintain project quality before submitting changes.

The best way to run browser tests for UI validations is using Playwright to perform cross-viewport checks and interaction tests. This approach allows you to verify throwaway UI validations and capture screenshots of the local dev server.

Yes, this testing workflow directly supports AEM Edge Delivery projects. It provides a standardized structure and tooling for unit tests, browser tests, linting, and performance checks specifically across blocks and utilities.

You set up test scaffolding by installing Vitest and Playwright, then creating basic test configurations. Once installed, you can run tests in watch mode during development using npm run test:watch to continuously validate changes.

You include linting and performance checks in your testing workflow to enforce quality standards before PRs. Integrating these checks into the development process ensures code changes are fully validated across functionality and performance metrics.

Yes, you can use Vitest for testing data processing utilities used across blocks. It is specifically applied to verify logic-heavy utilities, ensuring that data transformations and processing functions maintain expected behavior.