diff --git a/docs/src/content/docs/challenges/angular-performance/index.mdx b/docs/src/content/docs/challenges/angular-performance/index.mdx
index 58943ac..5d29f4a 100644
--- a/docs/src/content/docs/challenges/angular-performance/index.mdx
+++ b/docs/src/content/docs/challenges/angular-performance/index.mdx
@@ -2,7 +2,7 @@
title: Angular Performance
prev: false
next: false
-description: Challenge 34 is about learning the difference between Default and OnPush Change Detection Strategy.
+description: Learn how to use the Angular Devtool chrome extension.
sidebar:
order: 1
---
diff --git a/docs/src/content/docs/challenges/testing/index.mdx b/docs/src/content/docs/challenges/testing/index.mdx
new file mode 100644
index 0000000..51dc487
--- /dev/null
+++ b/docs/src/content/docs/challenges/testing/index.mdx
@@ -0,0 +1,66 @@
+---
+title: Testing
+prev: false
+next: false
+description: Introduction to testing challenges.
+sidebar:
+ order: 1
+---
+
+import { LinkCard } from '@astrojs/starlight/components';
+
+In this series of challenges about testing, you will learn how to write Integration tests using [Testing Library](https://testing-library.com/) and [Cypress Component Testing](https://docs.cypress.io/guides/component-testing/overview).
+
+The benefits of using Testing Library or Cypress Component Testing are to test your component as a black box. You will only interact with what the user can do on the UI. However, the difference with end-to-end tests is that the backend is mocked, which makes the tests faster and more maintainable.
+The goal is to mock as little as possible to test your component at a higher level than unit testing, which will make refactoring easier.
+Within a real application, integration tests are the tests you will write the most. Learning how to write them will make your application more robust and more maintainable.
+
+Here is a series of 8 challenges that you can take in any order.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+