JustinGrote
commented
5 months ago It uses the same name processing as Pester, but using hooks it occurs prior to final output for performance, so there may be an issue here especially with that referencing of a property rather than a direct object.
Thanks for the note! I'll see if I can sort this but in the meantime look in the tests directly for tested/supported name cases. https://github.com/pester/vscode-adapter/blob/main/sample/Tests/Basic.Tests.ps1
PsychoData
There is a mismatch between how placeholders are expanded in the "Pester Tests" (vscode-adapter) extension, and how they are expanded in Pester. I would expect them to be expanded the same by both.
As an example these tests ...
Template.tests.ps1
... are expanded and rendered like this by the "Pester Tests" extension:
... whereas they are expanded and rendered like this by Pester:
PowerShell version (tested with PS5 as well)
Pester Tests Extension version
Pester version