unit-tests

스타2

포크1

업데이트2026년 6월 5일 16:08

Write unit tests for a function or module. Use when the user shares code and wants tests for it.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

TeamDzX

TeamDzX/myllm-skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Unit tests

Write focused unit tests for the code the user provides.

Identify the language and test framework. If it's not obvious, pick the idiomatic default (e.g. pytest for Python, Jest for JS/TS, XCTest for Swift, JUnit for Java) and say which you used.
Cover, at minimum:
- the happy path,
- edge cases (empty/zero/boundary/large inputs),
- error/invalid-input behaviour.
Output the tests in one runnable code block.

Rules:

Use Arrange–Act–Assert and descriptive test names that state the expectation.
Test observable behaviour and the public interface — not private implementation details.
One logical assertion focus per test; avoid coupling tests to each other.
Don't hit the network, clock, or filesystem — stub/mock those and note it.
If a likely bug surfaces while writing tests, add a failing test for it and flag it briefly.

이 저장소의 다른 Skills

같은 저장소

changelog

TeamDzX/myllm-skills

Turn a list of commits or changes into a release changelog (Keep a Changelog format). Use when preparing release notes.

2026-06-052

decision-matrix

TeamDzX/myllm-skills

Weigh options against weighted criteria to support a decision. Use when the user is choosing between alternatives.

2026-06-052

proofread

TeamDzX/myllm-skills

Proofread and tighten text — fix grammar, clarity, and tone — and show what changed. Use when the user wants writing improved.

2026-06-052

regex-builder

TeamDzX/myllm-skills

Build and explain a regular expression from a description, with examples. Use when the user needs a regex or wants one explained.

2026-06-052

research-brief

TeamDzX/myllm-skills

Answer a question with a short, sourced research brief. Use for "research X", "what's the latest on Y", or fact-finding that needs citations.

2026-06-052

sql-query

TeamDzX/myllm-skills

Write a SQL query from a plain-English request and a table schema. Use when the user wants a query written, explained, or fixed.

2026-06-052

name	unit-tests
description	Write unit tests for a function or module. Use when the user shares code and wants tests for it.
license	MIT

Unit tests

Write focused unit tests for the code the user provides.

Identify the language and test framework. If it's not obvious, pick the idiomatic default (e.g. pytest for Python, Jest for JS/TS, XCTest for Swift, JUnit for Java) and say which you used.
Cover, at minimum:
- the happy path,
- edge cases (empty/zero/boundary/large inputs),
- error/invalid-input behaviour.
Output the tests in one runnable code block.

Rules:

Use Arrange–Act–Assert and descriptive test names that state the expectation.
Test observable behaviour and the public interface — not private implementation details.
One logical assertion focus per test; avoid coupling tests to each other.
Don't hit the network, clock, or filesystem — stub/mock those and note it.
If a likely bug surfaces while writing tests, add a failing test for it and flag it briefly.