SKILL

unit-tests

Prosjekt-uavhengig: analyser en fil og opprett manglende enhetstester. Detekter prosjektets test-oppsett (runner, kommando, stil), skriv happy/edge/error-tester som matcher eksisterende stil, kjør dem og rapporter dekning. Use when: skal generere manglende enhetstester for en fil, skal øke testdekning i et hvilket som helst prosjekt. Do NOT use for: TDD-implementering av ny funksjonalitet (egen flyt), E2E-tester (bruk `playwright-e2e`), ren kode-review.

Original · translation is not supported for this source language

Target: Software development & testing. Automatically collected · unverified.

Excerpt from the author’s documentation

Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.

Read the original text

Topics in the source

  • Lag manglende enhetstester (generisk)
  • Steg 0 — Detekter prosjektets test-oppsett FØRST
  • Arbeidsflyt
  • Steg 1 — Analyser filen
  • Steg 2 — Skriv testene
  • Steg 3 — Kjør og verifiser
  • Steg 4 — Dekning
  • Prinsipper

Analyser én fil og opprett comprehensive enhetstester for den. Skillen er prosjekt-uavhengig: den antar ikke en bestemt runner eller stil, men detekterer prosjektets oppsett og følger det. Input: $ARGUMENTS = fil-path som skal testes. Mangler den, vis: ALDRI skriv tester før du vet hvordan prosjektet tester. Kartlegg: 1. Runner + kommando: Se package.json scripts (eller pyproject.toml/go.mod/ Cargo.toml…). Finn test- og coverage-kommandoen prosjektet faktisk bruker. Vanlige: | Stack | Kjør én fil | Coverage | |-----------|----------------------------|--------------------------------------------| | Vitest | pnpm test -- --run | pnpm test -- --coverage | | Jest | npx jest | npx jest --coverage | | Mocha | npx mocha | npx nyc mocha | | node:test | node --test | node --test --experimental-test-coverage | | Pytest | pytest | pytest --cov | | Go | go test ./... | go test -cover ./... | Bruk prosjektets script (f.eks. pnpm test), ikke et antatt. Kjør alltid i ikke-watch / engangs-modus så prosessen avslutter (Vitest: --run). 2. Plassering + navngiving: Ligger tester ved siden av kilden (x.test.ts) eller i en egen mappe (tests/, tests/)? Hvilket suffiks (.test./.spec./test)? 3. Stil: Les 1

This is an excerpt. Refer to the complete source and its current requirements.

Source repository
ragnarwestad/aide
Source file
core/skills/unit-tests/SKILL.md
Fixed revision
4accd2a3379f990472d375916c4972aa2a1d0c8b
Read the complete original documentation ↗

Requirements

  • Only the author’s Skill metadata is included. Read the full instructions to check dependencies, licensing and conditions of use.

A small first task

先阅读原作者说明,再决定是否在自己的 AI 工具中使用。

Instructions for your AI tool

Author documentation is not live verification by this site. Without evidence, we do not mark a resource as compatible, safe or free.

Sources and evidence

This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.

Author: ragnarwestad/aide · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T13:00:43.330Z.

Categories are inferred from names, descriptions and paths. They do not establish compatibility.

License and attribution

MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.

Original license ↗

Synchronization, copying and user-reported success do not mark a resource as runtime-tested.

Limitations and notes

  • Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.