https://github.com/el-moudni-hicham/test-driven-development
All what you need about Test Driven Development
https://github.com/el-moudni-hicham/test-driven-development
java junit tdd testing
Last synced: 10 months ago
JSON representation
All what you need about Test Driven Development
- Host: GitHub
- URL: https://github.com/el-moudni-hicham/test-driven-development
- Owner: el-moudni-hicham
- Created: 2023-11-21T17:08:45.000Z (over 2 years ago)
- Default Branch: master
- Last Pushed: 2023-11-22T22:58:04.000Z (over 2 years ago)
- Last Synced: 2025-03-02T23:15:29.751Z (over 1 year ago)
- Topics: java, junit, tdd, testing
- Language: Java
- Homepage:
- Size: 23.4 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Test Driven Development
```All what you need about Test Driven Development```
# Table of content
- [Behavior Driven Development BDD](#behavior-driven-development-bdd)
- [Test Driven Development TDD](#test-driven-development-tdd)
- [ARRANGE ACT ASSERT Pattern](#arrange-act-assert-pattern)
# Behavior Driven Development BDD
BDD is a development methodology that emphasizes meeting the business needs of the software.
### **BDD syntax**
BDD is based on words that we often use in real life like **Given, When, Then,** and **And**, which will describe the behavior of our feature.
For example:
- **Given** a user leaves a comment
- **When** the comment exceeds 1000 characters
- **Then** the comment should not be saved
- **And** the user should see an error message
# Test Driven Development TDD
is an approach to software development where you write tests first, then use those tests to drive the design and development of your software application
Here's how the two BDD and TDD work together. You will:
1. Identify **behaviors** with BDD.
2. Write **tests** for these behaviors with TDD.
### The Three Rules of TDD
`Robert C. Martin` provides a concise set of rules for practicing TDD :
1. Write production code only to pass a failing unit test.
2. Write no more of a unit test than sufficient to fail (compilation failures are failures).
3. Write no more production code than necessary to pass the one failing unit test.
### Red, Green, Refactor Cycle
The red, green, refactor approach helps developers compartmentalize their focus into three phases:
**Red —** think about what you want to develop
**Green —** think about how to make your tests pass
**Refactor —** think about how to improve your existing implementation
# ARRANGE ACT ASSERT Pattern
There is a standard way to structure a test. This is the AAA Pattern, or Arrange - Act - Assert:
* **Arrange :** initialize all necessary inputs and the system to be tested if necessary.
* **Act :** Run the system under test with previously initialized inputs into outputs that you keep.
* **Assert :** Validate outbounds based on what is expected from your inbounds. You then conclude whether it is a success or a failure.
The figure below illustrates the entire overall architecture of the test :
