Domain model

Q: How deeply does Unit Testing Principles, Practices, and Patterns cover domain model?

Defines the domain model and explains its testing priority, but defers detailed isolation techniques.

As explained in Unit Testing Principles, Practices, and Patterns

A software model representing the concepts, rules, and behavior of an application domain.

A domain model represents the concepts, rules, and behavior of an application domain. Because it contains the system’s business logic, it usually deserves the greatest unit-testing attention and offers the strongest return on testing effort. section 1.4

Keep the domain model central to a maintainable testing strategy:

Isolate it from infrastructure code, external services, databases, and other application concerns so unit tests can target business logic directly. section 1.4
Test less-critical code briefly or indirectly, while using integration tests when broader system behavior matters. section 1.4
Treat testing attention as an investment: complex infrastructure algorithms may still merit thorough tests, but the domain model remains the default focus. section 1.4

How Unit Testing Principles, Practices, and Patterns covers it

Cover of Unit Testing Principles, Practices, and Patterns

liveBook manning.com

Read Unit Testing Principles, Practices, and Patterns on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

AI-Powered Developer: Build software with ChatGPT and CopilotA domain model is the representation of an application’s core business logic, including domain entities, value objects, and domain services.
liveBook manning.com

Architecture Modernization: Socio-technical alignment of software, strategy, and structureA domain model is a representation of the concepts, relationships, and rules that constitute a business domain.
liveBook manning.com

Java Persistence with Spring Data and Hibernate epubA domain model is an object-oriented representation of application-domain concepts, their state, and their relationships.
liveBook manning.com

Functional Design and Architecture: Examples in HaskellA domain model is a structured representation of the concepts, properties, relationships, and behavior of a problem domain.
liveBook manning.com

Automating API DeliveryA domain model is a structured representation of business concepts, relationships, and workflows as interconnected software objects with behavior and data.
liveBook manning.com

F# in Action: A Revised Edition of Get Programming with F#A domain model is a software representation of the entities, relationships, rules, and behavior of a problem domain.
liveBook manning.com

Go in Action, Second EditionA domain model is a representation of the concepts and relationships in a problem domain that software components conform to.

Compare how 8 books explain domain model →

Related concepts

domain-driven designused by · Domain-driven design is a software design approach that centers models, structure, and terminology on the concepts, behavior, and boundaries of a problem domain.
MVC modelequivalent to · An MVC model is the application component that represents application data and associated domain logic, making relevant state and behavior available to other components such as views.
shared kernelhas part · The shared kernel is a Domain-Driven Design pattern in which bounded contexts share a deliberately coordinated subset of their domain model, code, or data design.
api modelproduced by · An API-accessible model is a machine-learning model whose capabilities are made available to software through an application programming interface.
collaborative discovery and modelingequivalent to · Collaborative discovery and modeling is a group technique in which stakeholders jointly create and refine representations to establish shared understanding of a domain or system.

This explainer was generated by Manning's knowledge graph from the text of Unit Testing Principles, Practices, and Patterns. The section links point to the parts of the book it draws on.