AI TOOLS RADAR
Tutti gli Skills / LANGGENIUS
langgenius/dify

frontend-testing

Use when writing or changing Vitest or React Testing Library tests under web/ or packages/dify-ui/, or when the user explicitly requests frontend test strategy, including evaluation of an existing strategy.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/langgenius/dify --skill frontend-testing

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

Frontend Testing

Read the testing policy for the package that owns the changed tests:

  • web/: web/docs/test.md owns Web test boundaries, environments, and commands.
  • packages/dify-ui/: packages/dify-ui/docs/testing.md owns primitive test boundaries, environments, Storybook, and commands.

This skill adds no parallel policy or check sequence. Follow the selected owner's requirements, including its validation commands. Recommend deleting low-value tests as readily as adding missing behavior coverage, and report the contract verified and any material verification gap.

Correlati per attività

affaan-m
Community

springboot-verification

Run the full Spring Boot verification loop — Maven or Gradle build, SpotBugs, PMD, and Checkstyle static analysis, unit and Testcontainers integration tests with JaCoCo coverage, OWASP dependency and secret scans, and diff review — producing a pass/fail readiness report. Use when preparing a Spring Boot pull request, validating coverage thresholds, or running pre-deploy verification.

installazioni
3
GitHub Stars
288,1K
Aggiornato
20 ott
MIT1 File
Vedi dettagli →

Motivo della selezione: Test e sicurezza

affaan-m
Community

tdd-workflow

Test-driven development workflow: write a failing test first, watch it fail, implement the smallest change to green, then refactor with 80%+ coverage across unit, integration, and E2E tests. Use when writing a new feature, fixing a bug, refactoring, or when told to write failing tests first.

installazioni
3
GitHub Stars
287,3K
Aggiornato
20 ott
MIT1 File
Vedi dettagli →

Motivo della selezione: Test e sicurezza

morluto
Community

rea-ci-tests-audit

Audit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.

installazioni
5
GitHub Stars
345,8K
Aggiornato
20 ott
MIT3 File
Vedi dettagli →

Motivo della selezione: Test e sicurezza

mattpocock
Community

code-review

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".

installazioni
792,4K
GitHub Stars
302,5K
Aggiornato
22 ott
MIT2 File
Vedi dettagli →

Motivo della selezione: Test e sicurezza

dallo stesso repository

Altri Skills

Tutti gli Skills
langgenius
Community

frontend-code-review

Use only when the user explicitly requests a review or audit of frontend code under web/ or packages/dify-ui/. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests, diagnosis without review intent, or backend-only code.

installazioni
1
GitHub Stars
159,1K
Aggiornato
21 ott
NOASSERTION9 File
Vedi dettagli →