You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using VS Code for my PowerShell development. I have version 5.1 of PowerShell and version 1.95.3 of VS Code. I have the Pester extension installed in VS Code (version v2023.7.7). Until recently, I've had no issue with this extension but in the last few days whenever I try to refresh my Pester tests in VS Code I get the popup with the error message Cannot read properties of undefined (reading 'controllerId').
I also noticed that if I try to run the tests after getting the error message above they will run but I get some strange errors that don't make any sense (e.g. functions not available for imported modules and directories not available even though they exist on the local machine).
If I run the same Pester tests from the command line, they pass without any problems, which suggests that the problem is not in the Pester tests but in the VS Code extension.
I have tried:
Restarting VS Code
Reinstalling the Pester extension
Disabling all other extensions
Reverting my code to an old version where I never saw the problem occur
The text was updated successfully, but these errors were encountered:
Thanks for your submission! The test discovery needs a little bit of a rework, but have you tried it with PS7 and the latest version of pester? That's what I test the most against, 5.1 is best effort support.
I am using VS Code for my PowerShell development. I have version 5.1 of PowerShell and version 1.95.3 of VS Code. I have the Pester extension installed in VS Code (version v2023.7.7). Until recently, I've had no issue with this extension but in the last few days whenever I try to refresh my Pester tests in VS Code I get the popup with the error message
Cannot read properties of undefined (reading 'controllerId')
.I have attached the log file Pester_extension_logs.log showing the full output from the VS Code.
I also noticed that if I try to run the tests after getting the error message above they will run but I get some strange errors that don't make any sense (e.g. functions not available for imported modules and directories not available even though they exist on the local machine).
If I run the same Pester tests from the command line, they pass without any problems, which suggests that the problem is not in the Pester tests but in the VS Code extension.
I have tried:
The text was updated successfully, but these errors were encountered: