Support Pester running against "compiled" module or source code.

KevinMarquette / PlasterTemplates

A set of Plaster templates that I use.

MIT License

37 stars 9 forks source link

Closed christianacca closed 6 years ago

christianacca commented 6 years ago

The quickest feedback cycle is running Pester directly without having to run the build first.

Also build.ps1 adds a degree of friction to someone already familar with Pester - she now has to discover our project conventions.

Yet, when it comes to the CI build you always want to be testing against the "compiled" module output.

A project template should support both CI and developer preferences.

KevinMarquette commented 6 years ago

Thank you for your contributions. This last one had a merge conflict with your previous one. I think I sorted it out correctly.