-
Notifications
You must be signed in to change notification settings - Fork 1
Release Plan
Andrew Davidson edited this page Jan 14, 2021
·
57 revisions
For previous releases see Release History
- add the ability to export the pester test results (or pass back the generated result objects)
- add ability to pass in Pester configuration object to allow for some configuration of running Pester tests
- look into Format-Pester for formatting results output
- add integration tests
- module test
- script test
- code fixes from faults discovered by testing
- improve error message/failed test messages so that they are more meaningful
- further testing on different platforms
- Server 2016
- Server 2019
- Linux (distros to be confirmed)
- Ubuntu 20.04
- Other distros
- PowerShell 4.x ?
- PowerShell 6.x ?
- PowerShell 7.2
- Extra PSScriptAnalyzer rules (used by VSCode)
- code fixes from faults discovered by testing
- change
-SonarQubeRulesPath
to have a more generic name (-ExtraRulesPath
or-ScriptAnalyzerRulesPath
)- allow parameter to take multiple sets of rules
- modify checks to call PSScriptAnayzer with each rule set
- add the ability to specify which checks to run (
-Include
)- if not specified then this will be equivalent to
-Include All
- if not specified then this will be equivalent to
- add the ability to specify which checks to not run (
-Exlude
)- if not specified then this will be equivalent to
-Exclude None
- if not specified then this will be equivalent to
- add new check(s):
- whether or not unit tests exist for module functions
- add parameter to allow HelpElementsRules.psd1 file/location to be specified (
-HelpRulesPath
)- make the default to the same folder as the checks (therefore making the parameter optional)
- rename file to be HelpRules.psd1? to match parameter
- document HelpRules file format
- add commandlets to manage the HelpElementRules.psd1 datafile for help comment quality checks
- view rules
- add rule
- remove rule
- update rule
- validate rules
- convert HelpElementRules file to be json to allow support for PowerShell 4 ? (only if rest of system appears to work under PowerShell 4)
- work out a way to handle public/private functions
- create build system to auto-compile the module and publish to the PSGallery
- further improve help and wiki content
If there is something that you think would be useful please use the Discussions area and we can talk it through