Creates a workaround the failing tests.

We have set the CustomRulePath parameter in the cmdlet implementation in LibraryUsage.tests.ps1 to "string[]" type whereas in the c# implementation it is of "string" type. If we set the CustomRulePath parameter here to "string", then the library usage test fails when run as an administrator. We want to note that the library usage test doesn't fail when run as a non-admin user. Even if we create a "[string[]]" type object and pass it to Initialize method,  the tests fail to run as an admin with the following error message.

Assert failed on "Initialize" with "7" argument(s): "Test failed due to terminating error: The module was expected to contain an assembly manifest. (Exception from HRESULT: 0x80131018)

Author: Kapil Borle

Tests/Engine/InvokeScriptAnalyzer.tests.ps1

@@ -41,7 +41,14 @@ Describe "Test available parameters" {
         }
 
         It "accepts a string" {
-            $params["CustomRulePath"].ParameterType.FullName | Should Be "System.String"
+			if ($testingLibraryUsage)
+			{
+				$params["CustomRulePath"].ParameterType.FullName | Should Be "System.String[]"
+			}
+			else
+			{
+				$params["CustomRulePath"].ParameterType.FullName | Should Be "System.String"
+			}
         }
 
 		It "has a CustomizedRulePath alias"{

Tests/Engine/LibraryUsage.tests.ps1

@@ -17,7 +17,7 @@ function Invoke-ScriptAnalyzer {
 
         [Parameter(Mandatory = $false)]
 		[Alias("CustomizedRulePath")]
-		[string] $CustomRulePath = $null,
+		[string[]] $CustomRulePath = $null,
 
 		[Parameter(Mandatory = $false)]
 		[switch] $RecurseCustomRulePath,
@@ -41,17 +41,18 @@ function Invoke-ScriptAnalyzer {
 		[Parameter(Mandatory = $false)]       
         [string] $Profile = $null
 	)
-	[string[]]$customRulePathArr = @($CustomRulePath);
-	if ($CustomRulePath -eq $null)
-	{
-		$customRulePathArr = $null;
-	}
+	# There is an inconsistency between this implementation and c# implementation of the cmdlet. 
+	# The CustomRulePath parameter here is of "string[]" type whereas in the c# implementation it is of "string" type.
+	# If we set the CustomRulePath parameter here to  "string[]", then the library usage test fails when run as an administrator. 
+	# We want to note that the library usage test doesn't fail when run as a non-admin user.
+	# The following is the error statement when the test runs as an administrator. 
+	# Assert failed on "Initialize" with "7" argument(s): "Test failed due to terminating error: The module was expected to contain an assembly manifest. (Exception from HRESULT: 0x80131018)"
 
 	$scriptAnalyzer = New-Object "Microsoft.Windows.PowerShell.ScriptAnalyzer.ScriptAnalyzer";
 	$scriptAnalyzer.Initialize(
 		$runspace, 
 		$testOutputWriter, 
-		$customRulePathArr, 
+		$CustomRulePath, 
 		$IncludeRule,
 		$ExcludeRule,
 		$Severity,