authoring-tests

Write and run automated tests for Elements components including unit, accessibility, visual, SSR, and lighthouse tests. Use this skill whenever the user wants to write, create, update, or debug test files (.test.ts, .test.axe.ts, .test.visual.ts, .test.ssr.ts, .test.lighthouse.ts). Also trigger when the user asks about createFixture, removeFixture, elementIsStable, emulateClick, untilEvent, runAxe, visual baselines, theme testing, or test structure patterns like describe block naming.

Aller à l'installation Vérifier les fichiers

Dépôt: NVIDIA/elements
Dernière activité de la source: 12 août 2026 à 00:30
Langue détectée de SKILL.md: anglais
Étoiles: 93
Forks: 18

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec un assistant IA

Copiez ce prompt dans l’assistant IA que vous utilisez.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/NVIDIA/elements/tree/main/.agents/skills/authoring-tests.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/NVIDIA/elements --skill authoring-tests

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

SKILL.md

Instructions source · Aperçu en lecture seule

name: authoring-tests
description: Write and run automated tests for Elements components including unit, accessibility, visual, SSR, and lighthouse tests. Use this skill whenever the user wants to write, create, update, or debug test files (.test.ts, .test.axe.ts, .test.visual.ts, .test.ssr.ts, .test.lighthouse.ts). Also trigger when the user asks about createFixture, removeFixture, elementIsStable, emulateClick, untilEvent, runAxe, visual baselines, theme testing, or test structure patterns like describe block naming.

# Authoring Tests You MUST review @projects/site/src/docs/internal/guidelines/testing.md before making any testing changes. ## When to Use This Skill - Creating new test files for components (`.test.ts`, `.test.axe.ts`, `.test.visual.ts`, `.test.ssr.ts`, `.test.lighthouse.ts`) - Debugging test failures or updating existing tests - Understanding testing utilities from `@internals/testing` - Setting up test configurations or HTML templates - Writing tests that follow project patterns ## Test Type Guidelines Read the specific guideline based on the test type you're working with: - **Unit Tests (`.test.ts`)**: Read [testing-unit.md](/projects/site/src/docs/internal/guidelines/testing-unit.md) - covers `createFixture`, `elementIsStable`, event testing - **Accessibility Tests (`.test.axe.ts`)**: Read [testing-accessibility.md](/projects/site/src/docs/internal/guidelines/testing-accessibility.md) - covers axe-core usage, WCAG compliance - **Visual Tests (`.test.visual.ts`)**: Read [testing-visual.md](/projects/site/src/docs/internal/guidelines/testing-visual.md) - covers Playwright screenshots, theme testing - **SSR Tests (`.test.ssr.ts`)**: Read [testing-ssr.md](/projects/site/src/docs/internal/guidelines/testing-ssr.md) - covers server-side rendering compatibility - **Lighthouse Tests (`.test.lighthouse.ts`)**: Read [testing-lighthouse.md](/projects/site/src/docs/internal/guidelines/testing-lighthouse.md) - covers performance, accessibility scores ## Key Principles 1. **Test Isolation**: Each test should be independent with proper setup/teardown using `createFixture` and `removeFixture` 2. **Wait for Stability**: Always use `elementIsStable()` before making assertions on Lit components 3. **Comprehensive Coverage**: All new components require unit, accessibility, and visual tests at minimum 4. **Real User Events**: Use `emulateClick` and `untilEvent` for realistic event testing 5. **Theme Testing**: Visual tests should cover both light and dark themes ## References - [Testing Overview](/projects/site/src/docs/internal/guidelines/testing.md) - [Unit Testing](/projects/site/src/docs/internal/guidelines/testing-unit.md) - [Accessibility Testing](/projects/site/src/docs/internal/guidelines/testing-accessibility.md) - [Lighthouse Testing](/projects/site/src/docs/internal/guidelines/testing-lighthouse.md) - [SSR Testing](/projects/site/src/docs/internal/guidelines/testing-ssr.md) - [Visual Testing](/projects/site/src/docs/internal/guidelines/testing-visual.md) - [Vite Internals](/projects/internals/vite/README.md)

Voir sur GitHub

Retour à la recherche Retour à l’installation

summarize-releases

Create a monthly NVIDIA Elements “What’s New” docs page, matching video, and concise, copy-ready summary from local release tags, tagged changelogs, package versions, and commit history. Use for a scheduled release PR, monthly update, release roundup, changelog digest, Slack blurb, announcement, or plain-language explanation of recent Elements releases.

2026-10-01

summarize-video-releases

Create the 24–36 second marketing video for a monthly NVIDIA Elements “What’s New” post, rendered to projects/site/public/static/video/releases/MM-YYYY.webm from real Elements components, with feature snapshots inserted into the post. Use after the summarize-releases skill creates or updates a post, and whenever someone asks for a release video, what’s new video, monthly recap clip, changelog teaser, social video, or animated summary of Elements releases, even if they do not say “video skill”.

2026-10-01

agent-starters

Verify every starter supported by the stable production NVIDIA Elements CLI from a fresh consumer environment, investigate failures, and prepare at most one focused repair pull request. Use for nightly or scheduled production starter verification and starter availability failures.

2026-09-30

Tout voir dans ce dépôt

authoring-tests

Informations de source

Options d'installation

Installer avec un assistant IA

Vérifiez les fichiers source

Plus depuis ce dépôt

Installer avec un assistant IA

Plus depuis ce dépôt