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
Describing [PCCPackage]-[Constructors]
[-] [PCCPackage]-[Constructor]([String]Name,[String]Path) should Not Throw 98ms
Expected no exception to be thrown, but an exception "Exception setting "Path": "Cannot convert value "" to type "System.IO.DirectoryInfo". Error: "The path is not of a legal form.""" was thrown from C:\Users\taavast3\OneDrive\Repo\Projects\Clients\ee\ESC\PCCComplianceChecks\Code\Classes\Class.PCCPackage.ps1:11 char:9+$this.Path=$Path+ ~~~~~~~~~~~~~~~~~~.
18: {[PCCPackage]::New($Name,$Path)} | Should Not Throw
at <ScriptBlock>, C:\Users\taavast3\OneDrive\Repo\Projects\Clients\hh\ESC\PCCComplianceChecks\Code\Classes\Class.PCCPackage.Tests.Ps1: line 18
Describing [PCCPackage]-[Methods]
[-] [PCCPackage] --> SetValues() : - should Not Throw 28ms
MethodException: Cannot find an overload for"new" and the argument count: "0".
at <ScriptBlock>, C:\Users\taavast3\OneDrive\Repo\Projects\Clients\hh\ESC\PCCComplianceChecks\Code\Classes\Class.PCCPackage.Tests.Ps1: line 33
[-] [PCCPackage] --> SetValues() : - should return type [] 30ms
MethodException: Cannot find an overload for"new" and the argument count: "0".
at <ScriptBlock>, C:\Users\taavast3\OneDrive\Repo\Projects\Clients\hh\ESC\PCCComplianceChecks\Code\Classes\Class.PCCPackage.Tests.Ps1: line 48
[-] [PCCPackage] --> _SetVersion() : - should Not Throw 32ms
Here there is no parameterless constructor (I'll add in my production code) but Write-CUPesterTEsts should assume that a parameterless constructor is present.
If no parameterless constructor is present, is should use the first one of the list available (see Get-CUConstructor)
The text was updated successfully, but these errors were encountered:
This is not always the case. See example below.
generates
Here there is no parameterless constructor (I'll add in my production code) but
Write-CUPesterTEsts
should assume that a parameterless constructor is present.If no parameterless constructor is present, is should use the first one of the list available (see
Get-CUConstructor
)The text was updated successfully, but these errors were encountered: