Skip to content
This repository was archived by the owner on Jul 23, 2022. It is now read-only.

Commit 02ffb06

Browse files
acidonperAsier Cidon
andauthored
Added DDD and BDD in TDD presentation (#623)
Co-authored-by: Asier Cidon <[email protected]>
1 parent 7e48036 commit 02ffb06

File tree

5 files changed

+65
-1
lines changed

5 files changed

+65
-1
lines changed

slides/images/tdd/bdd.jpg

40.4 KB
Loading

slides/images/tdd/ddd-bdd-tdd.jpg

44.2 KB
Loading

slides/images/tdd/ddd.png

12.7 KB
Loading

slides/images/tdd/tdd.jpg

40.8 KB
Loading

slides/markdown/automated_testing_part_1.md

Lines changed: 65 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,65 @@
11
<!-- .slide: data-background-image="images/RH_NewBrand_Background.png" -->
22
## DevOps Culture and Practice <!-- {_class="course-title"} -->
3-
### Automated Testing Part 1 <!-- {_class="title-color"} -->
3+
### DDD, BDD & TDD <!-- {_class="title-color"} -->
44
DO500 <!-- {_class="title-color"} -->
55

66

77

8+
<!-- .slide: id="ddd" -->
9+
## Domain Driven Design
10+
11+
12+
13+
### Domain Driven Design
14+
#### _What Is It?_
15+
Domain-driven design (DDD) is an approach to developing software for complex
16+
needs by deeply connecting the implementation to an evolving model of the core
17+
business concepts.
18+
19+
20+
21+
![DDD](images/tdd/ddd.png)
22+
23+
24+
25+
### Domain Driven Design
26+
#### _How Does It Help?_
27+
* Placing the project's primary focus on the core domain and domain logic
28+
* Basing complex designs on a model of the domain
29+
* Initiating a creative collaboration between technical and domain experts to iteratively
30+
refine a conceptual model that addresses particular domain problems
31+
* Bridge the gap between domain experts and developers by using the same language to
32+
create the same understanding
33+
34+
35+
36+
<!-- .slide: id="bdd" -->
37+
## Behavior Driven Development
38+
39+
40+
41+
### Behavior Driven Development
42+
#### _What Is It?_
43+
Behavior-Driven Development (BDD) is a Test-First, Agile Testing practice
44+
that provides Built-In Quality by defining (and potentially automating) tests
45+
before, or as part of, specifying system behavior.
46+
47+
48+
49+
![BDD](images/tdd/bdd.jpg)
50+
51+
52+
53+
### Behavior Driven Development
54+
#### _How Does It Help?_
55+
* Creates a shared understanding of requirements between
56+
the business and the Agile Teams
57+
* Helps guide development, decrease rework, and increase flow
58+
* Creates business-facing scenarios that attempt to describe the behavior of a
59+
Story, Feature, or Capability from a user's perspective.
60+
61+
62+
863
<!-- .slide: id="tdd" -->
964
## Test Driven Development
1065

@@ -22,6 +77,10 @@ This practice is particularly powerful when combined with
2277

2378

2479

80+
![TDD](images/tdd/tdd.jpg)
81+
82+
83+
2584
### Test Driven Development
2685
#### _How Does It Help?_
2786
* Creates a detailed specification for the code
@@ -35,6 +94,11 @@ This practice is particularly powerful when combined with
3594

3695

3796

97+
### DDD & BDD & TDD
98+
![TDD](images/tdd/ddd-bdd-tdd.jpg)
99+
100+
101+
38102
<!-- .slide: id="revenge-automated-testing" -->
39103
## Revenge of the Automated Testing
40104
### Part 1

0 commit comments

Comments
 (0)