diff --git a/src/data/roadmaps/angular/content/end-to-end-testing@yhNGhduk__ow8VTLc6inZ.md b/src/data/roadmaps/angular/content/end-to-end-testing@yhNGhduk__ow8VTLc6inZ.md
index 9e2bcd9b6..14baea093 100644
--- a/src/data/roadmaps/angular/content/end-to-end-testing@yhNGhduk__ow8VTLc6inZ.md
+++ b/src/data/roadmaps/angular/content/end-to-end-testing@yhNGhduk__ow8VTLc6inZ.md
@@ -1 +1,11 @@
-# End-to-End Testing
\ No newline at end of file
+# End-to-End Testing
+
+End-to-end or (E2E) testing is a form of testing used to assert your entire application works as expected from start to finish or "end-to-end". E2E testing differs from unit testing in that it is completely decoupled from the underlying implementation details of your code. It is typically used to validate an application in a way that mimics the way a user would interact with it. The `ng e2e` command will first check your project for the "e2e" target. If it can't locate it, the CLI will then prompt you which e2e package you would like to use and walk you through the setup.
+
+Visit the following resources to learn more:
+
+- [@official@Angular Official Docs - End to End Testing](https://angular.dev/tools/cli/end-to-end)
+- [@official@Cypress Official Docs - Your First Test with Cypress](https://docs.cypress.io/guides/end-to-end-testing/writing-your-first-end-to-end-test)
+- [@official@Nightwatch Official Docs - Writing Tests: Introduction](https://nightwatchjs.org/guide/writing-tests/introduction.html)
+- [@official@Webdriver Official Docs - Getting Started](https://webdriver.io/docs/gettingstarted/)
+- [@official@Puppeteer Angular Schematic](https://pptr.dev/guides/ng-schematics/#getting-started)
\ No newline at end of file