docs(check-toc): Added check-toc utils documentation, not finished yet

Author: DevTKSS

doc/articles/check-toc-utilities/Overview.md

@@ -1,9 +1,10 @@
 ---
 uid: Uno.Contributing.check-toc.Overview
 ---
+
 # Toc Checker Overview
 
-The [`check_toc.ps1`](../check_toc.ps1) script helps maintain the structure and integrity of your documentation by:
+The `check_toc.ps1` script helps maintain the structure and integrity of your documentation by:
 
 - Detecting **broken links** in [toc.yml](../toc.yml)
 - Identifying **Markdown files** recursive to `articles` folder that are **not referenced** in the TOC
@@ -15,7 +16,7 @@ The [`check_toc.ps1`](../check_toc.ps1) script helps maintain the structure and
 ## 🛠️ Usage
 
 1. Open a **PowerShell terminal** at the **root** of your locally cloned Uno repository.
-2. Navigate to the [`doc/articles`](../../articles/) directory:
+2. Navigate to the `doc/articles` directory:
 
    ```ps1
    cd doc/articles

doc/articles/contributing/guidelines/creating-ps-pester-tests.md

@@ -0,0 +1,26 @@
+---
+uid: Uno.Contributing.Scripts.PowerShell-Pester-Tests
+---
+
+# Testing PowerShell Scripts with Pester
+
+## Introduction
+
+Some Parts of Uno.UI like the [Toc Checker](xref:Uno.Contributing.check-toc.Overview) with its [Utility Functions](xref:Uno.Contributing.check-toc.Utilities) are written in PowerShell. To make sure, they are working properly, the recommended and most common used Testing Framework is [Pester](https://pester.dev/docs/quick-start).
+
+<!-- ### TODO: ## Installing Pester 5+ https://pester.dev/docs/introduction/installation -->
+
+<!-- TODO: ### Pester List of the Commonly used Commands  -->
+<!-- TODO: ### Mocking File Content to test with Pester (like uid:) -->
+
+## Showing Pester Test Result in CI
+
+Pester integrates seamlessly with CI pipelines, allowing you to automate the validation of your PowerShell scripts. By including Pester tests in your CI configuration, you can ensure that changes to the `check_toc.ps1` script or its utilities do not introduce regressions. Most CI systems, such as GitHub Actions or Azure Pipelines, support running Pester tests and can display detailed test results in their interfaces.
+
+For more information, refer to the [Pester Test Results Documentation](https://pester.dev/docs/usage/test-results).
+
+## 📄 Related Pages
+
+- [The Uno docs website and DocFX](xref:Uno.Contributing.DocFx)
+- [Validating the Table of Contents](xref:Uno.Contributing.check-toc.Overview)
+- [Utility Functions for `check_toc`](xref:Uno.Contributing.check-toc.Utilities)