web-renderer-test
Facilitates adding visual regression tests for the web renderer component.
Install
mkdir -p .claude/skills/web-renderer-test-alexgutscher26 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15507" && unzip -o skill.zip -d .claude/skills/web-renderer-test-alexgutscher26 && rm skill.zipInstalls to .claude/skills/web-renderer-test-alexgutscher26
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Add a test case to the web rendererKey capabilities
- →Add a new fixture in `packages/web-renderer/src/test/fixtures`
- →Add the fixture to `packages/web-renderer/src/test/Root.tsx` for preview
- →Add a new test in `packages/web-renderer/src/test`
- →Execute the test using `bunx vitest src/test/video.test.tsx`
- →Update `packages/docs/docs/client-side-rendering/limitations.mdx`
How it works
The skill guides the user through creating a fixture for a new component, integrating it into the test suite for visual preview, writing a corresponding test, and updating documentation.
Inputs & outputs
When to use web-renderer-test
- →Adding new test cases
- →Visual regression testing
- →Previewing web renderer components
About this skill
The web renderer is in packages/web-renderer and the test suite is in packages/web-renderer/src/test.
It uses visual snapshot testing using vitest. A test file can for example be executed using:
bunx vitest src/test/video.test.tsx
Example
Each test is powered by a fixture in packages/web-renderer/src/test/fixtures.
A fixture looks like this for example:
import { AbsoluteFill } from "remotion";
const Component: React.FC = () => {
return (
<AbsoluteFill
style={{
justifyContent: "center",
alignItems: "center",
}}
>
<div
style={{
backgroundColor: "red",
width: 100,
height: 100,
borderRadius: 20,
}}
/>
</AbsoluteFill>
);
};
export const backgroundColor = {
component: Component,
id: "background-color",
width: 200,
height: 200,
fps: 25,
durationInFrames: 1,
} as const;
The corresponding test looks like this:
import { test } from "vitest";
import { renderStillOnWeb } from "../render-still-on-web";
import { backgroundColor } from "./fixtures/background-color";
import { testImage } from "./utils";
test("should render background-color", async () => {
const blob = await renderStillOnWeb({
licenseKey: "free-license",
composition: backgroundColor,
frame: 0,
inputProps: {},
imageFormat: "png",
});
await testImage({ blob, testId: "background-color" });
});
Adding a new test
- Add a new fixture in
packages/web-renderer/src/test/fixtures. - Important: Add the fixture to
packages/web-renderer/src/test/Root.tsxto add a way to preview it. - Add a new test in
packages/web-renderer/src/test. - Run
bunx vitest src/test/video.test.tsxto execute the test. - Important: Update
packages/docs/docs/client-side-rendering/limitations.mdxto reflect the newly supported property.
When not to use it
- →When adding tests for components outside the web renderer
- →When the test does not involve visual snapshot testing
- →When the test is not for a new component or property
Prerequisites
Limitations
- →The skill is specific to the `packages/web-renderer` directory structure
- →The skill requires updating `packages/docs/docs/client-side-rendering/limitations.mdx`
- →The skill uses visual snapshot testing with vitest
How it compares
This workflow provides a structured approach for adding visual snapshot tests to the web renderer, unlike manually creating test files without specific integration steps.
Compared to similar skills
web-renderer-test side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| web-renderer-test (this skill) | 0 | 5mo | No flags | Beginner |
| ui-ux-expert-skill | 91 | 9mo | Review | Advanced |
| react-best-practices | 22 | 3mo | No flags | Intermediate |
| frontend-testing | 11 | 3mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by alexgutscher26
View all by alexgutscher26 →You might also like
ui-ux-expert-skill
fercracix33
Technical workflow for implementing accessible React user interfaces with shadcn/ui, Tailwind CSS, and TanStack Query. Includes 6-phase process with mandatory Style Guide compliance, Context7 best practices consultation, Chrome DevTools validation, and WCAG 2.1 AA accessibility standards. Use after Test Agent, Implementer, and Supabase agents complete their work.
react-best-practices
redpanda-data
Client-side React performance optimization patterns.
frontend-testing
langgenius
Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.
feature-flags
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
verify
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
flow
Use when you need to run Flow type checking, or when seeing Flow type errors in React code.