adapt xtrem tdd links

ythirion · ythirion · commit dcc5f2915ec8 · 2024-04-26T14:22:01.000+02:00
diff --git a/docs/exercise/day08/solution/challenge-done.md b/docs/exercise/day08/solution/challenge-done.md
@@ -12,7 +12,7 @@ Here are the business rules :
 - Any other characters are not authorized.
 ```
 
-We can do it using [`Example Mapping`](https://xtrem-tdd.netlify.app/Flavours/example-mapping) workshop.
+We can do it using [`Example Mapping`](https://xtrem-tdd.netlify.app/Flavours/Practices/example-mapping) workshop.
 
 Here are some examples we can use for this business rule:
 
@@ -26,7 +26,7 @@ Here are some examples we can use for this business rule:
 
 We design the method from our test.
 
-🟢 Then we [generate the code through our IDE](https://xtrem-tdd.netlify.app/Flavours/generate-code-from-usage)
+🟢 Then we [generate the code through our IDE](https://xtrem-tdd.netlify.app/Flavours/Design/generate-code-from-usage)
 
 🔵 We can move the generated class to a named package (`password`)
 
diff --git a/docs/exercise/day08/solution/step-by-step.md b/docs/exercise/day08/solution/step-by-step.md
@@ -15,7 +15,7 @@ Here are the business rules :
 - Any other characters are not authorized.
 ```
 
-We can do it using [`Example Mapping`](https://xtrem-tdd.netlify.app/Flavours/example-mapping) workshop.
+We can do it using [`Example Mapping`](https://xtrem-tdd.netlify.app/Flavours/Practices/example-mapping) workshop.
 
 ### Contains at least 8 characters
 
@@ -33,7 +33,7 @@ We design the method from our test.
 
 ![Our first failing test](img/first-failing-test.png)
 
-🟢 Then we [generate the code through our IDE](https://xtrem-tdd.netlify.app/Flavours/generate-code-from-usage)
+🟢 Then we [generate the code through our IDE](https://xtrem-tdd.netlify.app/Flavours/Design/generate-code-from-usage)
 
 After generation, it looks like this:
 
diff --git a/docs/exercise/day09/solution/challenge-done.md b/docs/exercise/day09/solution/challenge-done.md
@@ -9,7 +9,7 @@
     - It will update the `totalAmount` meaning that the second time we call the method the result will be wrong
 
 - The responsibilities are mixed in the methods
-- We will apply the [`Command Query Separation` principle](https://xtrem-tdd.netlify.app/Flavours/command-query-separation) to fix this problem.
+- We will apply the [`Command Query Separation` principle](https://xtrem-tdd.netlify.app/Flavours/Design/command-query-separation) to fix this problem.
 
 |             | Returns  |           Side Effect           |
 |-------------|:--------:|:-------------------------------:|
diff --git a/docs/exercise/day09/solution/step-by-step.md b/docs/exercise/day09/solution/step-by-step.md
@@ -37,7 +37,7 @@ public class Client {
 
 > "Asking a question should not change the answer" - Bertrand Meyer
 
-We will apply the [`Command Query Separation` principle](https://xtrem-tdd.netlify.app/Flavours/command-query-separation) to fix this problem.
+We will apply the [`Command Query Separation` principle](https://xtrem-tdd.netlify.app/Flavours/Design/command-query-separation) to fix this problem.
 
 
 |             | Returns  |           Side Effect           |
diff --git a/docs/exercise/day11/solution/challenge-done.md b/docs/exercise/day11/solution/challenge-done.md
@@ -27,7 +27,7 @@ The concept of [`libyear`](https://libyear.com/) can help us to do so.
   - It makes dependencies management much, much easier
 
 If you want to know more on "how to keep you dependencies up-to-date", 
-you read this [article](https://xtrem-tdd.netlify.app/Flavours/keep-dependencies-up-to-date).
+you read this [article](https://xtrem-tdd.netlify.app/Flavours/Practices/keep-dependencies-up-to-date).
 
 >**Tip of the day: Code maintenance is not always about refactoring.**
 
diff --git a/docs/exercise/day11/solution/step-by-step.md b/docs/exercise/day11/solution/step-by-step.md
@@ -56,4 +56,4 @@ This kind of tool can really help teams take decisions regarding dependencies de
 
 ![Failure](img/failing-build.png)
 
-If you want to know more on "how to keep you dependencies up-to-date", you read this [article](https://xtrem-tdd.netlify.app/Flavours/keep-dependencies-up-to-date).
+If you want to know more on "how to keep you dependencies up-to-date", you read this [article](https://xtrem-tdd.netlify.app/Flavours/Practices/keep-dependencies-up-to-date).
diff --git a/docs/exercise/day13/solution/challenge-done.md b/docs/exercise/day13/solution/challenge-done.md
@@ -5,7 +5,7 @@
 In all tests, we are manipulating Articles with Comments. We want to 
 create them in a simpler and more maintainable way.
 
-We can use [`Test Data Buidler`](https://xtrem-tdd.netlify.app/Flavours/test-data-builders) pattern to achieve this
+We can use [`Test Data Buidler`](https://xtrem-tdd.netlify.app/Flavours/Testing/test-data-builders) pattern to achieve this
 purpose.
 
 It will:
diff --git a/docs/exercise/day13/solution/step-by-step.md b/docs/exercise/day13/solution/step-by-step.md
@@ -1,6 +1,6 @@
 ## Day 13: Find a way to eliminate the irrelevant, and amplify the essentials of those tests.
 
-We can use [`Test Data Buidler`](https://xtrem-tdd.netlify.app/Flavours/test-data-builders) pattern to achieve this
+We can use [`Test Data Buidler`](https://xtrem-tdd.netlify.app/Flavours/Testing/test-data-builders) pattern to achieve this
 purpose.
 
 It will:
@@ -83,7 +83,7 @@ void setup() {
 }
 ```
 
-- We then [`generate code from usage`](https://xtrem-tdd.netlify.app/Flavours/generate-code-from-usage)
+- We then [`generate code from usage`](https://xtrem-tdd.netlify.app/Flavours/Design/generate-code-from-usage)
 
 ![Generate Code From Usage](img/generate-code-from-usage.png)
 
diff --git a/docs/exercise/day17/solution/challenge-done.md b/docs/exercise/day17/solution/challenge-done.md
@@ -2,7 +2,7 @@
 
 `How could we design one test that has the impact of thousands?`
 
-We can use [`Property-Based Testing`](https://xtrem-tdd.netlify.app/flavours/pbt/). Here we choose to use the
+We can use [`Property-Based Testing`](https://xtrem-tdd.netlify.app/Flavours/Testing/pbt). Here we choose to use the
 library [`vavr-test`](https://github.com/vavr-io/vavr-test)(you may use alternatives like `junit quickcheck` for
 example).
 
diff --git a/docs/exercise/day17/solution/step-by-step.md b/docs/exercise/day17/solution/step-by-step.md
@@ -2,7 +2,7 @@
 
 `How could we design one test that has the impact of thousands?`
 
-We can use [`Property-Based Testing`](https://xtrem-tdd.netlify.app/flavours/pbt/). Here we choose to use the
+We can use [`Property-Based Testing`](https://xtrem-tdd.netlify.app/Flavours/Testing/pbt). Here we choose to use the
 library [`vavr-test`](https://github.com/vavr-io/vavr-test)(you may use alternatives like `junit quickcheck` for
 example).
 
diff --git a/docs/exercise/day18/solution/challenge-done.md b/docs/exercise/day18/solution/challenge-done.md
@@ -7,7 +7,7 @@ This kind of issues in the code are [`Linguistic Anti Patterns`](https://www.ven
 > How could we simply detect these issues?
 
 ### Architecture Unit Tests
-Take a look at [this page](https://xtrem-tdd.netlify.app/Flavours/archunit) describing this concept.
+Take a look at [this page](https://xtrem-tdd.netlify.app/Flavours/Architecture/archunit) describing this concept.
 
 - We can use the library [`archunit`](https://www.archunit.org/) in java to describe and enforce architecture / design rules.
 
diff --git a/docs/exercise/day18/solution/step-by-step.md b/docs/exercise/day18/solution/step-by-step.md
@@ -22,7 +22,7 @@ This kind of issues in the code are [`Linguistic Anti Patterns`](https://www.ven
 > How could we simply detect these issues?
 
 ### Architecture Unit Tests
-Take a look at [this page](https://xtrem-tdd.netlify.app/Flavours/archunit) describing this concept.
+Take a look at [this page](https://xtrem-tdd.netlify.app/Flavours/Architecture/archunit) describing this concept.
 
 - We can use the library [`archunit`](https://www.archunit.org/) in java to describe and enforce architecture / design rules.
 
diff --git a/docs/exercise/day19/solution/challenge-done.md b/docs/exercise/day19/solution/challenge-done.md
@@ -21,7 +21,7 @@ The problem if we use an `Error` here is that we need to be able to express that
 
 The good news is that we can do it really easily by using existing mechanism: monadic container `Either<L, R>`. It is already defined in [`vavr`](https://docs.vavr.io/#_either).
 
-More explanations on this concept [here](https://xtrem-tdd.netlify.app/Flavours/monads).
+More explanations on this concept [here](https://xtrem-tdd.netlify.app/Flavours/Design/monads).
 
 🔴 We start by describing our new expectation from a test
 - We design a new method `addCommentWithoutException`
diff --git a/docs/exercise/day19/solution/step-by-step.md b/docs/exercise/day19/solution/step-by-step.md
@@ -21,7 +21,7 @@ The problem if we use an `Error` here is that we need to be able to express that
 
 The good news is that we can do it really easily by using existing mechanism: monadic container `Either<L, R>`. It is already defined in [`vavr`](https://docs.vavr.io/#_either).
 
-More explanations on this concept [here](https://xtrem-tdd.netlify.app/Flavours/monads).
+More explanations on this concept [here](https://xtrem-tdd.netlify.app/Flavours/Design/monads).
 
 🔴 We start by describing our new expectation from a test
 - We design a new method `addCommentWithoutException`
diff --git a/docs/exercise/day23/solution/steps/1.cover-the-code.md b/docs/exercise/day23/solution/steps/1.cover-the-code.md
@@ -502,7 +502,7 @@ aUserWithTrips.addFriend(loggedUser);
 > What is the impact on our tests if the User constructor changes? 
 
 #### Use Test Data Builders
-🔵 [Test Data Builders](https://xtrem-tdd.netlify.app/Flavours/test-data-builders) can help you when writing / maintaining unit tests:
+🔵 [Test Data Builders](https://xtrem-tdd.netlify.app/Flavours/Testing/test-data-builders) can help you when writing / maintaining unit tests:
 - It helps to hide / encapsulate / centralize the creation of your objects
   - Make it more flexible if your design changes
 - Make your tests more readable and more business oriented
diff --git a/docs/exercise/day23/solution/steps/2.mutate-some-code.md b/docs/exercise/day23/solution/steps/2.mutate-some-code.md
@@ -69,7 +69,7 @@ class DemoTests {
 > Coverage metrics are a good negative indicator BUT a bad positive one...
 
 ### Mutation Testing
-Let's assess the quality of our tests by using [mutation testing](https://xtrem-tdd.netlify.app/Flavours/mutation-testing)
+Let's assess the quality of our tests by using [mutation testing](https://xtrem-tdd.netlify.app/Flavours/Testing/mutation-testing)
 
 - Test our tests by introducing MUTANTS (fault) into our production code during the test execution :
   - To check that the test is failing 
diff --git a/docs/exercise/day23/solution/steps/4.other-refactorings.md b/docs/exercise/day23/solution/steps/4.other-refactorings.md
@@ -75,7 +75,7 @@ public class UserBuilder {
 ### Be transparent in your contracts
 - For the behavior and guard in the `TripService` we may favor continuation `functions`
   - If we do so we should change the return type of our method as well to represent the computation issue that could be raised
-  - In other terms we should use a [monad](https://xtrem-tdd.netlify.app/Flavours/monads)
+  - In other terms we should use a [monad](https://xtrem-tdd.netlify.app/Flavours/Design/monads)
   - Our methods should be as explicit as possible
 - Let's decide to use a `Try` from `vavr`
 
@@ -105,7 +105,7 @@ public Try<Seq<Trip>> retrieveFriendTripsWithTry(User user, User loggedUser) {
 }
 ```
 
-- Continue this by using the [strangler pattern](https://xtrem-tdd.netlify.app/Flavours/strangler-pattern) 
+- Continue this by using the [strangler pattern](https://xtrem-tdd.netlify.app/Flavours/Refactoring/strangler-pattern) 
 
 🔵 do the opposite now -> call the new method from the former one
 

Original file line number	Diff line number	Diff line change
`@@ -56,4 +56,4 @@ This kind of tool can really help teams take decisions regarding dependencies de`
`56`	`56`
`57`	`57`	`![Failure](img/failing-build.png)`
`58`	`58`
`59`		`-If you want to know more on "how to keep you dependencies up-to-date", you read this [article](https://xtrem-tdd.netlify.app/Flavours/keep-dependencies-up-to-date).`
	`59`	`+If you want to know more on "how to keep you dependencies up-to-date", you read this [article](https://xtrem-tdd.netlify.app/Flavours/Practices/keep-dependencies-up-to-date).`