Blog

DetentShell's built-in test generation is built on Pester. Its author, Keith Ramsey, wrote the 25-part Pester for Beginners series linked below: unit vs. integration in plain English, through mocking, code coverage, and a full TDD workflow, capstone included.

1. What Is Pester, and Why Test PowerShell at All?
2. Installing Pester (and Untangling v3/4 vs v5)
3. Your First Test: Describe, It, and Should
4. Running Tests with Invoke-Pester and Reading the Output
5. The Should Command and Core Operators
6. Comparing Numbers, Strings, and Collections
7. Testing That Things Fail: Should -Throw
8. Saying "Not": Negating Assertions Cleanly
9. Describe vs Context vs It: Organizing Intent
10. Setup & Teardown: BeforeAll, AfterAll, BeforeEach, AfterEach
11. Arrange, Act, Assert: Naming Tests People Can Read
12. File Layout: .Tests.ps1, Folders, and Naming Conventions
13. Getting Your Function Under Test (Dot-Sourcing vs Modules)
14. Safe File and Registry Tests with TestDrive and TestRegistry
15. Data-Driven Tests with -ForEach and -TestCases
16. Tagging and Filtering Which Tests Run
17. What Mocking Is and When You Actually Need It
18. Mock Basics: Replacing a Command's Behavior
19. Proving Interactions with Should -Invoke
20. Targeted Mocks with -ParameterFilter
21. Mocking Pitfalls: Scope, InModuleScope, and Over-Mocking
22. Measuring Code Coverage with Pester
23. Configuring Pester with New-PesterConfiguration
24. Running Pester in CI/CD (GitHub Actions & Azure Pipelines)
25. Putting It Together: A TDD Workflow + Common Pitfalls (Capstone)

Start from the series announcement →