Import InvokePesterStub.ps1 from vscode-powershell (with history)
#1513
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
* Run single test * Add options for code lens and verbosity * Rename Pester options to enableLegacyCodeLens and outputVerbosity * change to use Co-authored-by: Tyler Leonhardt <[email protected]>
* Fix renamed setting * Fall through when legacy option is disablebd but Pester 5 is not found
…2730) * Support adding OutputPath and run file * refactor all logic
* Fixed crash when running pester older than 3.4.5 Calling Invoke-Pester with the -show param was breaking tests if running a version of pester older than 3.4.5 Moved logic for building spalt to call invoke-pester into a function and only added the show parameter if running pester 3.4.5 or newer * Update InvokePesterStub.ps1 Co-authored-by: Tyler James Leonhardt <[email protected]> * Update InvokePesterStub.ps1 Co-authored-by: Tyler James Leonhardt <[email protected]> Co-authored-by: Tyler James Leonhardt <[email protected]>
I used `git filter-repo` to export the history and adjust the path of this script, so that I could then use `git merge --allow-unrelated-history` to merge said script in with its development history intact.
|
Ok, verified that this build signs it properly: Now checking that the downstream build picks up the packaged artifact and works. |
|
Ok! All confirmed. The file is properly signed by this build, then incorporated into the module, which then uses it from the correct path and the "Run Pester Tests" command works as expected. @rjmholt |
rjmholt
approved these changes
Jun 28, 2021
dependabot bot
added a commit
to rjmholt/PowerShellEditorServices
that referenced
this pull request
Oct 11, 2021
…ster-stub Import `InvokePesterStub.ps1` from `vscode-powershell` (with history)
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.
I used
git filter-repoto export the history and adjust the path of this script, so that I could then usegit merge --allow-unrelated-historyto merge said script in with its development history intact.