Bump command reference and fix PowerShell casing #212
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fflaten
reviewed
Jun 26, 2022
We can fix those in source. Guessing it's mostly examples since they won't get formatted by VSCode to follow our |
|
Thanks, I would prefer not to touch the Pester repo to be honest so if you could.. awesome 💃 |
5 tasks
|
Pester is hands on the best test suite for my module 👍 I think all fixes have been resolved except for:
|
|
It think we should merge this, then take it from there. @fflaten you ok with that? |
fflaten
reviewed
Jun 30, 2022
Comment on lines
+67
to
+68
| SkipRun: Runs the discovery phase but skips run. | ||
| Use it with PassThru to get object populated with all tests. |
Comment on lines
+60
to
+61
| Throw: Throw an exception when test run fails. | ||
| When used together with Exit, throwing an exception is preferred. |
Comment on lines
+56
to
+57
| Exit: Exit with non-zero exit code when the test run fails. | ||
| When used together with Throw, throwing an exception is preferred. |
Comment on lines
+81
to
+82
| Line: Filter by file and scriptblock start line, useful to run parsed tests programmatically to avoid problems with expanded names. | ||
| Example: 'C:\tests\file1.Tests.ps1:37' |
Comment on lines
+88
to
+89
| FullName: Full name of test with -like wildcards, joined by dot. | ||
| Example: '*.describe Get-Item.test1' |
Comment on lines
+109
to
+110
| ExcludeTests: Exclude tests from code coverage. | ||
| This uses the TestFilter from general configuration. |
Comment on lines
+129
to
+130
| OutputFormat: Format to use for test result report. | ||
| Possible values: NUnitXml, NUnit2.5 or JUnitXml |
Comment on lines
+143
to
+144
| ErrorAction: Controls if Should throws on error. | ||
| Use 'Stop' to throw on error, or 'Continue' to fail at the end of the test. |
Comment on lines
+155
to
+156
| WriteDebugMessagesFrom: Write Debug messages from a given source, WriteDebugMessages must be set to true for this to work. | ||
| You can use like wildcards to get messages from multiple sources, as well as * to get everything. |
Comment on lines
+162
to
+163
| ReturnRawResultObject: Returns unfiltered result object, this is for development only. | ||
| Do not rely on this object for additional properties, non-public properties will be renamed without previous notice. |
|
Yeah man, see this comment earlier #212 (comment). One of the two points I think we should just accept for now. |
|
Merging as discussed. Will release a new version of the Alt3 module the coming days so we can start (and start debugging) from this point. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes:
PowerShellkeyword in mdx front matter is coming from the-MetaKeywordsparameter used by thegenerate-command-reference.ps1in this repo@fflaten:
Looks good to me💃