Pester script breaks PrimalSense

Support for all customers who have purchased a SAPIEN PowerShell Studio product license. This forum does not offer a response time guarantee.
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
User avatar
bmclain
Posts: 39
Joined: Mon Oct 22, 2007 1:47 am

Pester script breaks PrimalSense

Post by bmclain » Tue Apr 11, 2017 12:45 pm

PowerShell Studio 2017 - Version 5.4.138 - 64bit
Running on Windows 10 Version 1607 - Build 14393.970 - 64bit
Powershell version 5.1

If the script starts with these lines (as all pester tests do):
$here = Split-Path -Parent $MyInvocation.MyCommand.Path
$sut = (Split-Path -Leaf $MyInvocation.MyCommand.Path) -replace '\.Tests\.', '.'
. "$here\$sut"

Then you save the script, when you open it up, PrimalSense is broken. If you comment out the . "$here\$sut" line, then it works again. This just started happening since the last update.

User avatar
davidc
Posts: 5913
Joined: Thu Aug 18, 2011 4:56 am

Re: Pester script breaks PrimalSense

Post by davidc » Tue Apr 11, 2017 1:17 pm

Thank you for reporting this. We are aware of the issue and it is fixed in the upcoming service build. The next service build should be released fairly soon.
David
SAPIEN Technologies, Inc.