Skip to content
This repository was archived by the owner on Apr 27, 2023. It is now read-only.

Allow configurable pester verbosity (and ideally inherit from Powershell extension) #34

Open
JustinGrote opened this issue Jan 13, 2021 · 2 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@JustinGrote
Copy link

When I click the run for the tests, I prefer detailed to normal output. There should be settings to mirror these settings and ideally inherit these settings if not explicity set otherwise.

image

@TylerLeonhardt
Copy link
Owner

So luckily the Debug Output Verbosity is used already because vscode-pester-test-adapter uses the PowerShell extension for debugging.

The next change would be to hook up powershell.pester.outputVerbosity to vscode-pester-test-adapter. Pretty simple to do, I think:

const value = vscode.workspace.getConfiguration('powershell').get<string>('pester.outputVerbosity');

and then pass that in to the script:

export function GetPesterInvokeScript(scriptPath: string, outputPath: string, lineNumber?: string): string {

Interested in touching a little typescript? :)

@JustinGrote
Copy link
Author

@TylerLeonhardt if it annoys me enough, maybe :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants