Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Rule “what-unit-tests-to-write-and-how-many/rule” #9464

Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion rules/what-unit-tests-to-write-and-how-many/rule.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,10 @@
---
seoDescription: Do you know what unit tests to write and how many? Learn that 100% Unit Test Coverage is impractical, focus on quality over quantity, and prioritize writing tests for methods with high risk of unintended consequences.
type: rule
title: Do you know what unit tests to write and how many?
seoDescription: Do you know what unit tests to write and how many? Learn that
100% Unit Test Coverage is impractical, focus on quality over quantity, and
prioritize writing tests for methods with high risk of unintended
consequences.
uri: what-unit-tests-to-write-and-how-many
authors:
- title: Adam Cogan
Expand Down Expand Up @@ -30,6 +33,8 @@ Remember that unit tests are designed to be small in scope and help mitigate the

✅ Unit tests should be written for:

- Critical path
- Core functionality
- Fragile code
e.g. regular expressions
- When errors can be difficult to spot
Expand Down
Loading