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.

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

Adding some Write-Progress output to It #322

Merged
merged 1 commit into from Apr 28, 2015

Conversation

dlwyatt
Copy link
Member

@dlwyatt dlwyatt commented Apr 25, 2015

Potential fix for #321

I added a few blank lines to the console output at the beginning of Invoke-Pester, to make room for the Progress display. Tests that finish quickly may not wind up displaying any progress output at all, but long-running tests will provide the user with some feedback about what's happening.

dlwyatt added a commit that referenced this pull request Apr 28, 2015
Adding some Write-Progress output to It
@dlwyatt dlwyatt merged commit 7359214 into pester:master Apr 28, 2015
@dlwyatt dlwyatt deleted the WriteProgress branch April 28, 2015 16:53
@alx9r
Copy link
Member

alx9r commented May 6, 2015

This change seems to be causing some pretty significant side-effects -- at least on my system. Here are the downsides:

  • Much of the run-time the result of the latest few test runs are out of site below the bottom of the ISE console.
  • The entire console contents jerks up and down as each test runs. The jerking is harsh enough that I have to avert my eyes to avoid discomfort.

@dlwyatt
Copy link
Member Author

dlwyatt commented May 6, 2015

I'm not sure what you're referring to. I don't notice any jerking up and down in the ISE or powershell.exe. In both cases, the progress indicator appears at the top of the console / pane, while the most recent test results are at the bottom.

In any case, if you don't want to see that stuff, you can set $ProgressPreference to 'SilentlyContinue' before running Invoke-Pester.

@alx9r
Copy link
Member

alx9r commented May 6, 2015

Hmm...I just restarted ISE and the symptoms aren't there. I think it might have something to do with multiple powershell sessions in ISE (i.e. using CTRL-T) or ISESteroids, or both. I noticed it throughout multiple restarts today, but I didn't realize it wasn't constant until now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants