Why temp.ps1?

[skataben]

Why does Pester dynamically create a "temp" command, save it to "$TestDrive\temp.ps1", dotsource it, and then invoke the "temp" command?

Why not just directly invoke the scriptblock used to create the "temp" command? Could doing so remove the need for having a TestDrive? Also, why is there a TestDrive?

My needs for Pester don't cover this, and I'm just wondering what the use cases are.

(I'm referring to the code in It.ps1)

Edit: I found the wiki for the TestDrive. My original question remains, however. What value does temp.ps1 provide?

[nohwnd]

The temp.ps1 is there because that is how someone in history made it work and it never got changed. I proposed to process all the Its in memory in #104 but we then run into (unrelated) problems, rolled back the change and forgot to commit it again.

[scottmuc]

I think temp.ps1 was to handle the line number of the error being correctly calculated.

[skataben]

Interesting, that's exactly what led me to the question. What is the intended file/line number? In other words, how is it supposed to work? My preference is the file/line # of the *.Tests file I'm running, but sometimes it displays "temp.ps1: line xxx" which isn't very helpful, at least not for me. My build is currently in disarray, so it may just be a temporary thing.

[nohwnd]

@skataben The error line number should be the line number in the Tests file. That is what is tested in the Pester self tests.