You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a project maintainer I want other to be able to contribute and have transperancy in the testing environment. At this time, all pester tests are conducted in hand-built private Azure DevOps projects. To enable potential contributors I want to have a piece of code that can be run to deploy a test environment suiteable for running the implemented pester tests.
Acceptance Criteria
When using REST API this code should be in PowerShell, but Terraform or similar IaC tool may also be used
Must deploy 1 project where all rules fail and 1 project where all rules within current project VSE licensing pass
Adapt existing Pester tests as needed to facilitate naming conventions and the split from 1 mixed project to 2 clear defined pass and fail environments.
Implemented as both a GitHub Actions workflow and an Azure DevOps Pipelines YAML.
Should include cleanup script and/or manual cleanup instructions
The text was updated successfully, but these errors were encountered:
As a project maintainer I want other to be able to contribute and have transperancy in the testing environment. At this time, all pester tests are conducted in hand-built private Azure DevOps projects. To enable potential contributors I want to have a piece of code that can be run to deploy a test environment suiteable for running the implemented pester tests.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: