unit-tests

Use when reviewing CI coverage, automated checks, or test strategy related to Write unit tests. Focus on whether the rule is continuously verified, not just documented.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/unit-tests/SKILL.md

Write unit tests

Unit tests catch bugs before they reach production, serve as documentation for expected behavior, and give developers confidence to refactor code without breaking functionality.

Quick Reference

Test business logic, utilities, and edge cases
Aim for 80%+ coverage on critical paths
Use descriptive test names that explain behavior
Mock external dependencies, not internal modules
Run tests in CI to catch regressions early

Check

Check if this codebase has unit tests with good coverage for critical functionality.

Fix

Write unit tests for untested functions and components to improve code reliability.

Explain

Explain how unit tests catch bugs early and serve as documentation for expected behavior.

Code Review

Review tests, CI workflows, and enforcement points related to Write unit tests. Flag exact gaps where the rule is not automatically verified or where failures do not block regressions.

For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/en/rules/testing/unit-tests

Repository: thedaviddias/Front-End-Checklist
Path: skills/unit-tests/SKILL.md
Commit: 48405aa

Last updated: about 6 hours ago
First committed: 2 months ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.