Log test starting

[davidmatson]

Checklist

• Feature request has a meaningful title
• I have searched the existing issues. See all issues
• I have tested using the latest version of Pester. See Installation and update guide.

Summary of the feature request

I'd like to be able to see when a test starts, so that if it hangs or crashes, I can know what test is the problem.

How should it work?

Perhaps only shown in higher-verbosity output modes, such as Diagnostic. something like a "[>] name" output line could work, such as:

Running tests from 'C:\My.Tests.ps1'
Describing some describe string
  [>] sleeps before passing
  [+] sleeps before passing 1.03s (1.02s|6ms)

for this test:

Describe "some describe string" {
It "sleeps before passing" {
Sleep 1
"a" | Should -Be "a"
}
}

[nohwnd]

we could use ansi to rewrite the line. so we show when the test started and then when it finished. It would be harder in CI where the test start would most often be kept on screen and probably pollute the execution.

Interesting feature but I would like to see this thought out for the CI and see if there are some other better ways to do this, we had feature like this before where we used the progress reporter to show the test that is running right now.

My ideal situation would be if we could show progress bar only for tests that take 1s or more, to avoid overwhelming the user with ton of changes on tests that are short.

[fflaten]

Also related to #2021 so you could add or replace with custom output.

[davidmatson]

@nohwnd, @fflaten - any mechanism that allows knowing when a test starts reliably would be great. I tend to think always providing this indication, rather than just sometimes, makes this mechanism more valuable, covering cases such as CI or when a process immediately exits/crashes when a test starts running.

I'd tend to start simple, with just giving the option (when in the most verbose mode) always to display a "starting" line, which would help all cases, whether interactive dev or CI. Thoughts?