Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Domain-Driven Design with Golang

You're reading from   Domain-Driven Design with Golang Use Golang to create simple, maintainable systems to solve complex business problems

Arrow left icon
Product type Paperback
Published in Dec 2022
Publisher Packt
ISBN-13 9781804613450
Length 204 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Matthew Boyle Matthew Boyle
Author Profile Icon Matthew Boyle
Matthew Boyle
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Part 1: Introduction to Domain-Driven Design
2. Chapter 1: A Brief History of Domain-Driven Design FREE CHAPTER 3. Chapter 2: Understanding Domains, Ubiquitous Language, and Bounded Contexts 4. Chapter 3: Entities, Value Objects, and Aggregates 5. Chapter 4: Exploring Factories, Repositories, and Services 6. Part 2: Real -World Domain-Driven Design with Golang
7. Chapter 5: Applying Domain-Driven Design to a Monolithic Application 8. Chapter 6: Building a Microservice Using DDD 9. Chapter 7: DDD for Distributed Systems 10. Chapter 8: TDD, BDD, and DDD 11. Index 12. Other Books You May Enjoy

TDD

TDD stands for test-driven development. It is a process in which you write tests for business requirements before your software is fully developed. As you write code, you repeatedly update your test cases until you are satisfied the code satisfies the business requirements. The goal is to write “just enough” code to pass the tests and no more. A diagram representing this process is shown here:

Figure 8.1 – TDD flow chart

Let’s look at each of the steps in isolation. If we were developing a new feature for our application, we would do the following:

  1. Add a test: Before we write any code, we write the test case. You might write this in the form of a user story such as “As an API user, I want to be able to see a user’s balance across all their accounts when I call the /balances endpoint so that I can display it on the home screen,” or by using the Given-When-Then method: “Given I am an API user...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime