vurbroker.blogg.se

Pester tests with visual studio code vs visual studio 2017
Pester tests with visual studio code vs visual studio 2017












Requirements and how to install Powershell 5.0 There are also other stats that I collect like average, min and max times. I was able to flesh out a working prototype fairly quickly and then spent the next several days polishing it into something usable.īecause I have the line by line execution times, I also tracked how many times each line was ran.

pester tests with visual studio code vs visual studio 2017

I decided to do the same thing and measure the time deltas between executions. Then after they run all the tests, they walk the breakpoints to see how many were hit.

pester tests with visual studio code vs visual studio 2017

They set a breakpoint for every line in the specified script. I took a close look at it and they did something clever.

pester tests with visual studio code vs visual studio 2017

This idea was inspired by Pester’s ability to give you the code coverage of your tests. It also has the fun side effect of showing your code coverage visually if you run it with pester. Calling this one Chronometer because it has the ability to track line by line script execution times. I just published a new module to the Powershell Gallery.














Pester tests with visual studio code vs visual studio 2017