Introduction
- About This Book
- Timeline
- Software Killers
- Billion Dollar Mistakes
- Clear Code Overview
- Clear Code Rules
Data Processing
Examples
- Separate Use Cases With Data Model
Maintenance Cost
OOP
- Separate Data And Procedures
- Do Not Use Inheritance
- When To Avoid Inheritance?
- What Is The Problem With Abstract Frameworks?
VARIOUS
Externals
Technology
- Git Tutorials
Clean Code

Powered by GitBook

On this page

Clean Code
Clean Code Outline

Unit Tests

Last updated 5 years ago

Was this helpful?

CtrlK

Rules
Benefits
Code coverage
Good practices

Was this helpful?

It is not part of this document, find only some thoughts here.

Clean Code = Testable Code

Rules

Continuously write unit tests

Maintain unit test - keep them running

TDD - Test Driven Development

Tests must be clean too - they will change with the code

Tests must obey the test patterns

F.I.R.S.T. principles

Benefits

Enforces to write testable code Makes the code flexible - changes with regression tests

Code coverage

Try to reach higher levels (>90%)
Do not write tests only for the sake of the code coverage

Good practices

Use the default (package) visibility for the sake of the unit testing

Unit Testing briefly: