[Feature]: Sensible to perform integration/unit tests using PowerShell's Pester
(with psake
)?
#27
Labels
feature
new functionality for existing module
Module Name
N/A
Description
Just a question here -- I was wondering if the testing code documentation restricts testing of terraform module's to just the
terratest
golang
framework.I have been using a combination of the following PowerShell (Core) modules lately with my Terraform projects and find it to be very fluent:
Az
: Azure Suite of PowerShell ModulesPester
: Testspsake
: Task RunnerPlaster
: Module templating and best practicesPSDepend
: Dependency Management and VersioningCrescendo
: (Optional) Could be used to create custom wrapper utilities for classicterraform-cli
commands/scenarios (for example converting terraform plan to JSON or setting up the remote-backend / service principal, etc.)CredentialManager
: Manage credentials and authenticationplatyPS
: Generate documentation similar toterraform-docs
does (although I still prefer terraform-docs here).Similar to how
PSRule
(see Validate infrastructure as code (IaC) and objects using PowerShell rules) works nicely withBicep
orARM Templates
; I feel like these PowerShell tools really integrate nicely with the Terraform infrastructure as code ecosystem, specifically for Azure infrastructural deployments.It also is a more friendly interface to use for a typical Azure developer that is more likely used to PowerShell syntax and development over Go, especially if having to write complex tests (notice the similarities between Pester/psake/DSC syntax and Terraform configuration syntax?).
Just wanted to see if anyone had any food for thoughts on this subject - any criticism or feedback would be much appreciated.
Thanks!
Example usage
No response
Other information
No response
The text was updated successfully, but these errors were encountered: