1 Test Driven Development

Ivan Paulovich edited this page 2019-12-03 16:07:37 +01:00

You are not allowed to write any production code unless it is to make a failing unit test pass.

You are not allowed to write any more of a unit test than is sufficient to fail; and compilation failures are failures.

You are not allowed to write any more production code than is sufficient to pass the one failing unit test.

http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd

Index of Clean Architecture Manga

Home

• Motivation
  • Learn how to design modular applications
  • Explore the .NET Core features
  • Learn from the open source community
• Contributing

Use Cases

Flow of Control

• Register Flow of Control
• Get Customer Details Flow of Control

Architecture Styles

• Hexagonal Architecture Style
  • Ports
  • Adapters
  • The Left Side
  • The Right Side
• Onion Architecture Style
• Clean Architecture Style

Design Patterns

• Controller
• ViewModel
• Presenter
  • Standard Output
  • Error Output
  • Alternative Output
• Unit of Work
• First-Class Collections
• Factory

Domain-Driven Design Patterns

• Value Object
• Entity
• Aggregate Root
• Repository
• Use Case
• Bounded Context
• Entity Factory
• Domain Service
• Application Service

Separation of Concerns

• Domain
• Application
• Infrastructure
• User Interface

Encapsulation

Test-Driven Development TDD

Fakes

SOLID

• Single Responsibility Principle
• Open-Closed Principle
• Liskov Substitution Principle
• Interface Segregation Principle
• Dependency Inversion Principle

.NET Core Web API

• Swagger and API Versioning
• Microsoft Extensions
• Feature Flags
• Logging
• Data Annotations
• Authentication
• Authorization

Entity Framework Core

• Add Migration
• Update Database

Environment Configurations

DevOps

• Running the Application Locally
• Running the Tests Locally
• Continuous Integration & Continuous Deployment

Docker

• SQL Server

Related Content and Projects