Skip to content

Navigation Menu

Sign inAppearance settings

View all features
- BY COMPANY SIZE
  Enterprises
  Small and medium teams
  Startups
  Nonprofits
- BY USE CASE
  App Modernization
  DevSecOps
  DevOps
  CI/CD
  View all use cases
- BY INDUSTRY
  Healthcare
  Financial services
  Manufacturing
  Government
  View all industries
View all solutions
- EXPLORE BY TOPIC
  AI
  Software Development
  DevOps
  Security
  View all topics
- EXPLORE BY TYPE
  Customer stories
  Events & webinars
  Ebooks & reports
  Business insights
  GitHub Skills
- SUPPORT & SERVICES
  Documentation
  Customer support
  Community forum
  Trust center
  Partners
View all resources
- COMMUNITY
  GitHub SponsorsFund open source developers
- PROGRAMS
  Security Lab
  Maintainer Community
  Accelerator
  GitHub Stars
  Archive Program
- REPOSITORIES
  Topics
  Trending
  Collections
- ENTERPRISE SOLUTIONS
  Enterprise platformAI-powered developer platform
- AVAILABLE ADD-ONS
  GitHub Advanced SecurityEnterprise-grade security features
  Copilot for BusinessEnterprise-grade AI features
  Premium SupportEnterprise-grade 24/7 support
Pricing

Sign upAppearance settings

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

Uh oh!

There was an error while loading. Please reload this page.

pester / Pester Public

Notifications You must be signed in to change notification settings
Fork 478
Star 3.3k

Code
Issues 52
Pull requests 13
Discussions
Actions
Projects
Wiki
Security and quality
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Wiki
Security and quality
Insights

Code Coverage

Jump to bottom

bravo-kernel edited this page Jan 18, 2020 · 5 revisions

This page has moved to https://pester.dev/docs/usage/code-coverage.

Wiki pages Pages 40

Concepts

What is Pester?
Isolating File Operations using the TestDrive
Performing Assertions with Should
Mocking Commands with Pester
Unit Testing within Modules
Showing Test Results in CI (TeamCity, AppVeyor, Azure DevOps)
Generating Code Coverage metrics

Command Reference

Describe
Context
It
Should
BeforeEach
AfterEach
In
New‐Fixture
New‐MockObject
Invoke‐Pester
New‐PesterOption
Mock
Assert‐VerifiableMocks
Assert‐MockCalled
InModuleScope
Set‐ItResult
Set‐TestInconclusive

Clone this wiki locally

Footer

© 2026 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Community
Docs
Contact

You can’t perform that action at this time.