PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

Benefits of Writing Unit Tests

hackerone.com | blog | #software-quality | #unit-testing | #tdd | #static-typing | #dynamic-typing | #development-practices
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

Unit testing improves code quality and maintainability by catching errors early. The article covers how tests catch type/import errors in dynamic languages and support test-driven development.
Published
Collected

Related coverage

blog · hackerone.com
Code Reviews, Small Moments, Big Impacts
HackerOne engineer Rafael de Carvalho on code reviews: explain why an issue matters, share examples and trade-offs, and mind tone; small review moments compound into software quality and team trust.
blog · hackerone.com
Unraveling Cyclomatic Complexity: A Guide to Simplifying Your Code
Explains cyclomatic complexity, McCabe's 1976 metric counting linearly independent paths through code, how high scores hurt testability and maintainability, and how to simplify tangled functions.
blog · hackerone.com
5 Ways I Provide Value as a PullRequest Reviewer When I Start Reviewing a New Project
A PullRequest reviewer describes five ways to add immediate value on a new project, starting with catching security vulnerabilities that most updates introduce, often fixable with minor changes.
blog · hackerone.com
Navigating Time Pressure in the Code Review Process
Will Barrett offers tactics for code review under urgency: define urgency levels with expected responses, create space for review, and resist efficiency pressure that lets bugs slip through.
blog · hackerone.com
What We Can Learn from the Ruby on Rails Project about Code Review
Will Barrett examines the Ruby on Rails project as a model for code review at scale, from maintainer structure to contribution flow and conventions that keep a huge open-source codebase healthy.
blog · hackerone.com
11 Ways to Create Pull Requests that are Easy to Review
Eleven habits for review-friendly pull requests: keep them under 500 lines, enforce consistent style with linters, write self-documenting code, unit tests, and intent comments.
Back