Pester VS PSScriptAnalyzer

Pester is what's used for most Powershell testing. While it has some pretty amazing features, it does have issues with .NET class method mocking and sometimes scope can be weird. Here's a simple example:

This is the fun that is Powershell mocking, or at least the form that someone completely new to Powershell would write. One thing I must say is that Pester's mocking capabilities are quite easy to work with. It reminded me of pytest mock patching, only well, simpler. Most of the time spent fighting tests was due to the nuances of pipeline flow. For example, you can see that your mocked method was called X many times through something like this:

The folder blocked all users from reading the files so if you open up the files it looks empty, even tho you have show hidden files turned on. You can't delete it since it says that you need access from TrustedInstaller. This is cleaver by the hacker since trusted installer is actually the name of a windows feature. HOW-EVER by using the command line I found out that the folder contains framework like these two. https://github.com/d1pakda5/PowerShell-for-Pentesters https://github.com/pester/Pester

I'm really surprised that nobody in this thread has mentioned Pester. PowerShell has its own automated unit testing framework that is incredibly versatile. You do need to know PowerShell in order to really make it shine, but if there are some simple tests that your class requires such as "make sure this value conforms to this regex value", Pester is pretty easy to pick up and utilize.

Once you start building code/scripts that are used consistently, consider adding Pester testing to your work. Most sysadmin managers may not get it, but if you're talking to dev managers, they'll absolutely get the importance of unit testing and why it's a good tool to have. Again, down the road. Learn the basics first.

Finally, the Pester testing framework, which ships with Powershell, is a great way to ensure your code actually does what it's meant to do.

Pester GH page

I am looking to build a custom profile for a ws2019 with ps 7.2 + to use to check my scripts, i have tried using the compat collector https://github.com/PowerShell/PSScriptAnalyzer/tree/development/PSCompatibilityCollector and running the build.ps1 script there but I do not see an output for my commands and the script text doesn't provide much clarify to me at least.

PSScriptAnalyze is a static code analysis tool that checks PowerShell scripts for best practices and potential security issues. It is available on GitHub and can be installed as a module in PowerShell. https://github.com/PowerShell/PSScriptAnalyzer

PSScriptAnalyzer is a static code checker for PowerShell modules and scripts. Runs a set of rules that test the quality of PowerShell code against best practice, then warns about potential code defects and suggests potential solutions. xXxLinuxUserxXx likes this linter "to get unified codestyle in the scripts."

Not a windows admin and more like a programmer but i would suggest to use some linter (https://github.com/PowerShell/PSScriptAnalyzer) to get unified codestyle in the scripts :)

It’s best practice to keep $null on the left side of comparisons https://github.com/PowerShell/PSScriptAnalyzer/blob/development/RuleDocumentation/PossibleIncorrectComparisonWithNull.md

This one is a real problem. When I reference a type which is defined in another file in a class, I get an error in my vscode. the class works but the PSScriptAnalyzer doesn't know that the type is imported. I found this github issue which is about supressing the issue, I tried that and couldnt get it to work but I'd rather that it just recognized the type from the other file https://github.com/PowerShell/PSScriptAnalyzer/issues/1041

I would definer not autoformat on save with bugs such was this still outstanding: https://github.com/PowerShell/PSScriptAnalyzer/issues/1580

That's some sloppy code. Wmic is deprecated. You shouldn't put unencrypted passwords in scripts. You shouldn't use write-host anymore. $null goes in front, etc. Try using https://github.com/PowerShell/PSScriptAnalyzer to ensure decent code. Also write code in vscode. Also read https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.localaccounts/new-localuser?view=powershell-5.1

I discovered the Invoke-Build build system, PSScriptAnalyzer for linting, and Pester for testing/mocking. I wrote a GitLab CI/CD pipeline that takes advantage of all of this to push releases to our company's PSRepo. I also discovered the Plaster template system for scaffolding new projects, and created a custom company template for standardizing our repo structures.