Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[CI Environment] Introduce custom Pester results section to GitHub workflow runs #3074

Merged
merged 45 commits into from
Apr 2, 2023
Merged

[CI Environment] Introduce custom Pester results section to GitHub workflow runs #3074

merged 45 commits into from
Apr 2, 2023

Conversation

AlexanderSehr
Copy link
Contributor

@AlexanderSehr AlexanderSehr commented Apr 1, 2023 •
edited
Loading

Description

  • Introduce custom Pester results section to GitHub workflow runs, aligned with how we surface PS-Rule results
  • Several small updates to Pester tests to improve formatting

Example

Pester validation summary

Total No. of Processed Tests Passed Tests ✅ Failed Tests ❌ Skipped Tests 📎
170 161 4 5
List of failed Tests

Failed Tests

Name Error Source
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults] Output section should contain all outputs defined in the template file. Expected 0, because list of template outputs missing in the ReadMe file [location] should be empty., but got 1. module.tests.ps1:459
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults] Set-ModuleReadMe script should not apply any updates. Expected $true, because The file hashes before and after applying the Set-ModuleReadMe function should be identical and should not have diff 
diff --git a/modules/Microsoft.KeyVault/vaults/readme.md b/modules/Microsoft.KeyVault/vaults/readme.md
index 7cb36942f..c3829180a 100644
--- a/modules/Microsoft.KeyVault/vaults/readme.md
+++ b/modules/Microsoft.KeyVault/vaults/readme.md
@@ -382,6 +382,7 @@ privateEndpoints:  [
 
 | Output Name | Type | Description |
 | :-- | :-- | :-- |
+| location | string | The location the resource was deployed into. |
 | name | string | The name of the key vault. |
 | resourceGroupName | string | The name of the resource group the key vault was created in. |
 | resourceId | string | The resource ID of the key vault. |
. Please re-run the script for this module's template., but got $false.		 module.tests.ps1:552
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/secrets] Output section should contain all outputs defined in the template file. Expected 0, because list of template outputs missing in the ReadMe file [name] should be empty., but got 1. module.tests.ps1:459
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/secrets] Set-ModuleReadMe script should not apply any updates. Expected $true, because The file hashes before and after applying the Set-ModuleReadMe function should be identical and should not have diff 
diff --git a/modules/Microsoft.KeyVault/vaults/secrets/readme.md b/modules/Microsoft.KeyVault/vaults/secrets/readme.md
index 85fd672e7..dc65f229f 100644
--- a/modules/Microsoft.KeyVault/vaults/secrets/readme.md
+++ b/modules/Microsoft.KeyVault/vaults/secrets/readme.md
@@ -148,6 +148,7 @@ roleAssignments: [
 
 | Output Name | Type | Description |
 | :-- | :-- | :-- |
+| name | string | The name of the secret. |
 | resourceGroupName | string | The name of the resource group the secret was created in. |
 | resourceId | string | The resource ID of the secret. |
. Please re-run the script for this module's template., but got $false.		 module.tests.ps1:552
List of passed Tests

Passed Tests

Name Source
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] All apiVersion properties should be set to a static, hard-coded value. module.tests.ps1:816
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] All non-required parameters in template file should not have description that start with "Required.". module.tests.ps1:1153
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] All parameters in parameters files exist in template file (deploy.json). module.tests.ps1:1125
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] All required parameters in template file (deploy.json) should exist in parameters files. module.tests.ps1:1139
Test file tests. / General test file / *[Microsoft.KeyVault/vaults] Bicep test deployment files should invoke test like [module testDeployment '../.deploy.bicep' = {] module.tests.ps1:587
Test file tests. / General test file / *[Microsoft.KeyVault/vaults] Bicep test deployment files should invoke test like [module testDeployment '../.deploy.bicep' = {] module.tests.ps1:587
Test file tests. / General test file / *[Microsoft.KeyVault/vaults] Bicep test deployment files should invoke test like [module testDeployment '../.deploy.bicep' = {] module.tests.ps1:587
Test file tests. / General test file / [Microsoft.KeyVault/vaults] Bicep test deployment name should contain [-test-]. module.tests.ps1:598
Test file tests. / General test file / [Microsoft.KeyVault/vaults] Bicep test deployment name should contain [-test-]. module.tests.ps1:598
Test file tests. / General test file / [Microsoft.KeyVault/vaults] Bicep test deployment name should contain [-test-]. module.tests.ps1:598
Test file tests. / General test file / [Microsoft.KeyVault/vaults] Bicep test deployment should have parameter [serviceShort]. module.tests.ps1:609
Test file tests. / General test file / [Microsoft.KeyVault/vaults] Bicep test deployment should have parameter [serviceShort]. module.tests.ps1:609
Test file tests. / General test file / [Microsoft.KeyVault/vaults] Bicep test deployment should have parameter [serviceShort]. module.tests.ps1:609
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] Conditional parameters' description should contain 'Required if' followed by the condition making the parameter required. module.tests.ps1:1074
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] CUA ID deployment should be present in the template. module.tests.ps1:932
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults] Dependencies section should contain all cross-references defined in the template file. module.tests.ps1:465
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] Each parameters' description should start with a one word category starting with a capital letter, followed by a dot, a space and the actual description text ending with a dot. module.tests.ps1:1051
File/folder tests. / .test folder / [Microsoft.KeyVault/vaults] Folder should contain one or more test files. module.tests.ps1:135
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] If delete lock is implemented, the template should have a lock parameter with an empty default value. module.tests.ps1:852
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] Location output should be returned for resources that use it module.tests.ps1:973
File/folder tests. / General module folder tests / [Microsoft.KeyVault/vaults] Module should contain a [ .test ] folder. module.tests.ps1:102
File/folder tests. / General module folder tests / [Microsoft.KeyVault/vaults] Module should contain a [ deploy.json / deploy.bicep ] file. module.tests.ps1:83
File/folder tests. / General module folder tests / [Microsoft.KeyVault/vaults] Module should contain a [ readme.md ] file. module.tests.ps1:92
File/folder tests. / General module folder tests / [Microsoft.KeyVault/vaults] Module should contain a [ version.json ] file. module.tests.ps1:112
File/folder tests. / General module folder tests / [Microsoft.KeyVault/vaults] Module should have a GitHub workflow. module.tests.ps1:54
File/folder tests. / General module folder tests / [Microsoft.KeyVault/vaults] Module should have an Azure DevOps pipeline. module.tests.ps1:69
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] Output names should be camel-cased (no dashes or underscores and must start with lower-case letter). module.tests.ps1:913
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults] Outputs section should contain a table with these column names in order: Output Name, Type. module.tests.ps1:421
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] outputs' description should start with a capital letter and contain text ending with a dot. module.tests.ps1:1101
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] Parameter names should be camel-cased (no dashes or underscores and must start with lower-case letter). module.tests.ps1:864
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults] Parameter tables should provide columns in the following order: Parameter Name, Type, Default Value, Allowed Values, Description. Each column should be present unless empty for all the rows. module.tests.ps1:331
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults] Parameters section should contain a table for each existing parameter category in the following order: Required, Conditional, Optional, Generated. module.tests.ps1:308
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults] Parameters section should contain all parameters from the template file. module.tests.ps1:371
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults] Readme.md file should contain these sections in order: Navigation, Resource Types, Parameters, Outputs, Cross-referenced modules, Deployment examples. module.tests.ps1:233
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults] Readme.md file should not be empty. module.tests.ps1:224
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] Resource Group output should exist for resources that are deployed into a resource group scope. module.tests.ps1:995
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] Resource ID output should exist. module.tests.ps1:1031
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] Resource name output should exist. module.tests.ps1:1011
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults] Resources section should contain all resources from the template file. module.tests.ps1:258
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults] Resources section should not contain more resources than the template file. module.tests.ps1:283
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] Template schema should use HTTPS reference. module.tests.ps1:806
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] Template schema version should be the latest. module.tests.ps1:781
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] The Location should be defined as a parameter, with the default value of [resourceGroup().Location] or global for ResourceGroup deployment scope module.tests.ps1:950
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] The template file should contain required elements schema, contentVersion, resources. module.tests.ps1:841
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] The template file should not be empty. module.tests.ps1:772
Deployment template tests. / General template / [Microsoft.KeyVault/vaults] Variable names should be camel-cased (no dashes or underscores and must start with lower-case letter). module.tests.ps1:888
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] All apiVersion properties should be set to a static, hard-coded value. module.tests.ps1:816
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] All non-required parameters in template file should not have description that start with "Required.". module.tests.ps1:1153
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] All parameters in parameters files exist in template file (deploy.json). module.tests.ps1:1125
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] All required parameters in template file (deploy.json) should exist in parameters files. module.tests.ps1:1139
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] Conditional parameters' description should contain 'Required if' followed by the condition making the parameter required. module.tests.ps1:1074
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] CUA ID deployment should be present in the template. module.tests.ps1:932
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/accessPolicies] Dependencies section should contain all cross-references defined in the template file. module.tests.ps1:465
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] Each parameters' description should start with a one word category starting with a capital letter, followed by a dot, a space and the actual description text ending with a dot. module.tests.ps1:1051
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] If delete lock is implemented, the template should have a lock parameter with an empty default value. module.tests.ps1:852
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] Location output should be returned for resources that use it module.tests.ps1:973
File/folder tests. / General module folder tests / [Microsoft.KeyVault/vaults/accessPolicies] Module should contain a [ deploy.json / deploy.bicep ] file. module.tests.ps1:83
File/folder tests. / General module folder tests / [Microsoft.KeyVault/vaults/accessPolicies] Module should contain a [ readme.md ] file. module.tests.ps1:92
File/folder tests. / General module folder tests / [Microsoft.KeyVault/vaults/accessPolicies] Module should contain a [ version.json ] file. module.tests.ps1:112
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] Output names should be camel-cased (no dashes or underscores and must start with lower-case letter). module.tests.ps1:913
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/accessPolicies] Output section should contain all outputs defined in the template file. module.tests.ps1:438
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/accessPolicies] Outputs section should contain a table with these column names in order: Output Name, Type. module.tests.ps1:421
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] outputs' description should start with a capital letter and contain text ending with a dot. module.tests.ps1:1101
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] Parameter names should be camel-cased (no dashes or underscores and must start with lower-case letter). module.tests.ps1:864
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/accessPolicies] Parameter tables should provide columns in the following order: Parameter Name, Type, Default Value, Allowed Values, Description. Each column should be present unless empty for all the rows. module.tests.ps1:331
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/accessPolicies] Parameters section should contain a table for each existing parameter category in the following order: Required, Conditional, Optional, Generated. module.tests.ps1:308
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/accessPolicies] Parameters section should contain all parameters from the template file. module.tests.ps1:371
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/accessPolicies] Readme.md file should contain these sections in order: Navigation, Resource Types, Parameters, Outputs, Cross-referenced modules, Deployment examples. module.tests.ps1:233
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/accessPolicies] Readme.md file should not be empty. module.tests.ps1:224
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] Resource Group output should exist for resources that are deployed into a resource group scope. module.tests.ps1:995
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] Resource ID output should exist. module.tests.ps1:1031
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] Resource name output should exist. module.tests.ps1:1011
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/accessPolicies] Resources section should contain all resources from the template file. module.tests.ps1:258
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/accessPolicies] Resources section should not contain more resources than the template file. module.tests.ps1:283
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/accessPolicies] Set-ModuleReadMe script should not apply any updates. module.tests.ps1:520
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] Template schema should use HTTPS reference. module.tests.ps1:806
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] Template schema version should be the latest. module.tests.ps1:781
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] The Location should be defined as a parameter, with the default value of [resourceGroup().Location] or global for ResourceGroup deployment scope module.tests.ps1:950
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] The template file should contain required elements schema, contentVersion, resources. module.tests.ps1:841
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] The template file should not be empty. module.tests.ps1:772
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/accessPolicies] Variable names should be camel-cased (no dashes or underscores and must start with lower-case letter). module.tests.ps1:888
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] All apiVersion properties should be set to a static, hard-coded value. module.tests.ps1:816
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] All non-required parameters in template file should not have description that start with "Required.". module.tests.ps1:1153
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] All parameters in parameters files exist in template file (deploy.json). module.tests.ps1:1125
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] All required parameters in template file (deploy.json) should exist in parameters files. module.tests.ps1:1139
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] Conditional parameters' description should contain 'Required if' followed by the condition making the parameter required. module.tests.ps1:1074
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] CUA ID deployment should be present in the template. module.tests.ps1:932
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/keys] Dependencies section should contain all cross-references defined in the template file. module.tests.ps1:465
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] Each parameters' description should start with a one word category starting with a capital letter, followed by a dot, a space and the actual description text ending with a dot. module.tests.ps1:1051
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] If delete lock is implemented, the template should have a lock parameter with an empty default value. module.tests.ps1:852
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] Location output should be returned for resources that use it module.tests.ps1:973
File/folder tests. / General module folder tests / [Microsoft.KeyVault/vaults/keys] Module should contain a [ deploy.json / deploy.bicep ] file. module.tests.ps1:83
File/folder tests. / General module folder tests / [Microsoft.KeyVault/vaults/keys] Module should contain a [ readme.md ] file. module.tests.ps1:92
File/folder tests. / General module folder tests / [Microsoft.KeyVault/vaults/keys] Module should contain a [ version.json ] file. module.tests.ps1:112
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] Output names should be camel-cased (no dashes or underscores and must start with lower-case letter). module.tests.ps1:913
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/keys] Output section should contain all outputs defined in the template file. module.tests.ps1:438
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/keys] Outputs section should contain a table with these column names in order: Output Name, Type. module.tests.ps1:421
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] outputs' description should start with a capital letter and contain text ending with a dot. module.tests.ps1:1101
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] Parameter names should be camel-cased (no dashes or underscores and must start with lower-case letter). module.tests.ps1:864
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/keys] Parameter tables should provide columns in the following order: Parameter Name, Type, Default Value, Allowed Values, Description. Each column should be present unless empty for all the rows. module.tests.ps1:331
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/keys] Parameters section should contain a table for each existing parameter category in the following order: Required, Conditional, Optional, Generated. module.tests.ps1:308
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/keys] Parameters section should contain all parameters from the template file. module.tests.ps1:371
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/keys] Readme.md file should contain these sections in order: Navigation, Resource Types, Parameters, Outputs, Cross-referenced modules, Deployment examples. module.tests.ps1:233
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/keys] Readme.md file should not be empty. module.tests.ps1:224
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] Resource Group output should exist for resources that are deployed into a resource group scope. module.tests.ps1:995
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] Resource ID output should exist. module.tests.ps1:1031
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] Resource name output should exist. module.tests.ps1:1011
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/keys] Resources section should contain all resources from the template file. module.tests.ps1:258
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/keys] Resources section should not contain more resources than the template file. module.tests.ps1:283
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/keys] Set-ModuleReadMe script should not apply any updates. module.tests.ps1:520
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] Template schema should use HTTPS reference. module.tests.ps1:806
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] Template schema version should be the latest. module.tests.ps1:781
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] The Location should be defined as a parameter, with the default value of [resourceGroup().Location] or global for ResourceGroup deployment scope module.tests.ps1:950
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] The template file should contain required elements schema, contentVersion, resources. module.tests.ps1:841
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] The template file should not be empty. module.tests.ps1:772
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] All apiVersion properties should be set to a static, hard-coded value. module.tests.ps1:816
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] All non-required parameters in template file should not have description that start with "Required.". module.tests.ps1:1153
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] All parameters in parameters files exist in template file (deploy.json). module.tests.ps1:1125
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] All required parameters in template file (deploy.json) should exist in parameters files. module.tests.ps1:1139
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] Conditional parameters' description should contain 'Required if' followed by the condition making the parameter required. module.tests.ps1:1074
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] CUA ID deployment should be present in the template. module.tests.ps1:932
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/secrets] Dependencies section should contain all cross-references defined in the template file. module.tests.ps1:465
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] Each parameters' description should start with a one word category starting with a capital letter, followed by a dot, a space and the actual description text ending with a dot. module.tests.ps1:1051
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] If delete lock is implemented, the template should have a lock parameter with an empty default value. module.tests.ps1:852
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] Location output should be returned for resources that use it module.tests.ps1:973
File/folder tests. / General module folder tests / [Microsoft.KeyVault/vaults/secrets] Module should contain a [ deploy.json / deploy.bicep ] file. module.tests.ps1:83
File/folder tests. / General module folder tests / [Microsoft.KeyVault/vaults/secrets] Module should contain a [ readme.md ] file. module.tests.ps1:92
File/folder tests. / General module folder tests / [Microsoft.KeyVault/vaults/secrets] Module should contain a [ version.json ] file. module.tests.ps1:112
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] Output names should be camel-cased (no dashes or underscores and must start with lower-case letter). module.tests.ps1:913
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/secrets] Outputs section should contain a table with these column names in order: Output Name, Type. module.tests.ps1:421
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] outputs' description should start with a capital letter and contain text ending with a dot. module.tests.ps1:1101
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] Parameter names should be camel-cased (no dashes or underscores and must start with lower-case letter). module.tests.ps1:864
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/secrets] Parameter tables should provide columns in the following order: Parameter Name, Type, Default Value, Allowed Values, Description. Each column should be present unless empty for all the rows. module.tests.ps1:331
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/secrets] Parameters section should contain a table for each existing parameter category in the following order: Required, Conditional, Optional, Generated. module.tests.ps1:308
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/secrets] Parameters section should contain all parameters from the template file. module.tests.ps1:371
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/secrets] Readme.md file should contain these sections in order: Navigation, Resource Types, Parameters, Outputs, Cross-referenced modules, Deployment examples. module.tests.ps1:233
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/secrets] Readme.md file should not be empty. module.tests.ps1:224
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] Resource Group output should exist for resources that are deployed into a resource group scope. module.tests.ps1:995
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] Resource ID output should exist. module.tests.ps1:1031
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] Resource name output should exist. module.tests.ps1:1011
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/secrets] Resources section should contain all resources from the template file. module.tests.ps1:258
Readme tests. / Readme content tests / [Microsoft.KeyVault/vaults/secrets] Resources section should not contain more resources than the template file. module.tests.ps1:283
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] Template schema should use HTTPS reference. module.tests.ps1:806
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] Template schema version should be the latest. module.tests.ps1:781
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] The Location should be defined as a parameter, with the default value of [resourceGroup().Location] or global for ResourceGroup deployment scope module.tests.ps1:950
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] The template file should contain required elements schema, contentVersion, resources. module.tests.ps1:841
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] The template file should not be empty. module.tests.ps1:772
API version tests. / In [Microsoft.KeyVault/vaults] used resource type [diagnosticsettings] should use one of the recent API version(s). Currently using [2021-05-01-preview]. module.tests.ps1:1282
API version tests. / In [Microsoft.KeyVault/vaults] used resource type [locks] should use one of the recent API version(s). Currently using [2020-05-01]. module.tests.ps1:1282
API version tests. / In [Microsoft.KeyVault/vaults] used resource type [privateEndpoints] should use one of the recent API version(s). Currently using [2022-07-01]. module.tests.ps1:1282
API version tests. / In [Microsoft.KeyVault/vaults] used resource type [privateEndpoints/privateDnsZoneGroups] should use one of the recent API version(s). Currently using [2022-07-01]. module.tests.ps1:1282
API version tests. / In [Microsoft.KeyVault/vaults] used resource type [roleassignments] should use one of the recent API version(s). Currently using [2022-04-01]. module.tests.ps1:1282
API version tests. / In [Microsoft.KeyVault/vaults] used resource type [vaults] should use one of the recent API version(s). Currently using [2022-07-01]. module.tests.ps1:1282
API version tests. / In [Microsoft.KeyVault/vaults] used resource type [vaults/accessPolicies] should use one of the recent API version(s). Currently using [2022-07-01]. module.tests.ps1:1282
API version tests. / In [Microsoft.KeyVault/vaults] used resource type [vaults/keys] should use one of the recent API version(s). Currently using [2022-07-01]. module.tests.ps1:1282
API version tests. / In [Microsoft.KeyVault/vaults] used resource type [vaults/secrets] should use one of the recent API version(s). Currently using [2022-07-01]. module.tests.ps1:1282
API version tests. / In [Microsoft.KeyVault/vaults/accessPolicies] used resource type [vaults/accessPolicies] should use one of the recent API version(s). Currently using [2022-07-01]. module.tests.ps1:1282
API version tests. / In [Microsoft.KeyVault/vaults/keys] used resource type [roleassignments] should use one of the recent API version(s). Currently using [2022-04-01]. module.tests.ps1:1282
API version tests. / In [Microsoft.KeyVault/vaults/keys] used resource type [vaults/keys] should use one of the recent API version(s). Currently using [2022-07-01]. module.tests.ps1:1282
API version tests. / In [Microsoft.KeyVault/vaults/secrets] used resource type [roleassignments] should use one of the recent API version(s). Currently using [2022-04-01]. module.tests.ps1:1282
API version tests. / In [Microsoft.KeyVault/vaults/secrets] used resource type [vaults/secrets] should use one of the recent API version(s). Currently using [2022-07-01]. module.tests.ps1:1282
List of skipped Tests

Skipped Tests

Name Reason Source
File/folder tests. / .test folder / [Microsoft.KeyVault/vaults] JSON test files in the .test folder should be valid json. Test is skipped, because the module has no JSON test files. module.tests.ps1:1282
File/folder tests. / .test folder / [Microsoft.KeyVault/vaults] JSON test files in the .test folder should be valid json. Test is skipped, because the module has no JSON test files. module.tests.ps1:1282
File/folder tests. / .test folder / [Microsoft.KeyVault/vaults] JSON test files in the .test folder should be valid json. Test is skipped, because the module has no JSON test files. module.tests.ps1:1282
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/keys] Variable names should be camel-cased (no dashes or underscores and must start with lower-case letter). Test is skipped, because the module template has no variables. module.tests.ps1:1282
Deployment template tests. / General template / [Microsoft.KeyVault/vaults/secrets] Variable names should be camel-cased (no dashes or underscores and must start with lower-case letter). Test is skipped, because the module template has no variables. module.tests.ps1:1282

Pipeline references

For module/pipeline changes, please create and attach the status badge of your successful run.

Pipeline Notes
KeyVault - Vaults <- Illustrates error message

Type of Change

Please delete options that are not relevant.

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Update to documentation

@AlexanderSehr AlexanderSehr linked an issue Apr 1, 2023 that may be closed by this pull request
[Feature Request]: Reworking Pester-Test Results publishing to PSRule approach #2575
Closed
@AlexanderSehr AlexanderSehr self-assigned this Apr 1, 2023
@AlexanderSehr AlexanderSehr added [cat] pipelines category: pipelines [cat] testing category: testing [cat] github category: GitHub labels Apr 1, 2023
@AlexanderSehr AlexanderSehr marked this pull request as ready for review April 1, 2023 13:23
@AlexanderSehr AlexanderSehr requested a review from a team as a code owner April 1, 2023 13:23
@AlexanderSehr AlexanderSehr enabled auto-merge (squash) April 1, 2023 13:23
@AlexanderSehr AlexanderSehr merged commit 50a50d1 into main Apr 2, 2023
@AlexanderSehr AlexanderSehr deleted the users/alsehr/pesterTestResultsFormat branch April 2, 2023 06:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ahmadabdalla ahmadabdalla ahmadabdalla approved these changes

Assignees

@AlexanderSehr AlexanderSehr

Labels
[cat] github category: GitHub [cat] pipelines category: pipelines [cat] testing category: testing
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[Feature Request]: Reworking Pester-Test Results publishing to PSRule approach
2 participants
@AlexanderSehr @ahmadabdalla