Pester code coverage for the longest time was based on break points and break points in PowerShell until 7.4, which will be released now are super slow. So I use the core of the new module profiler that I wrote to actually implement new version of code coverage inside of Pester. And so running tests on their profiler is definitely a great way to find slow code in your module because you exercise a lot of parts of your code. It gives a little bit more visibility into what the heck's going on.

Get the Snipd
podcast app

Unlock the knowledge in podcasts with the podcast player of the future.
App store bannerPlay store banner

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode

Save any
moment

Hear something you like? Tap your headphones to save it with AI-generated key takeaways

Share
& Export

Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode