Fix rule tests for CoreCLR on Linux

Author: Kapil Borle

Tests/Rules/AvoidUnloadableModuleOrMissingRequiredFieldInManifest.tests.ps1

@@ -1,7 +1,10 @@
-Import-Module PSScriptAnalyzer
+$directory = Split-Path -Parent $MyInvocation.MyCommand.Path
+$testRootDirectory = Split-Path -Parent $directory
+Import-Module PSScriptAnalyzer
+Import-Module (Join-Path $testRootDirectory 'PSScriptAnalyzerTestHelper.psm1')
+
 $missingMessage = "The member 'ModuleVersion' is not present in the module manifest."
 $missingMemberRuleName = "PSMissingModuleManifestField"
-$directory = Split-Path -Parent $MyInvocation.MyCommand.Path
 $violationFilepath = Join-Path $directory "TestBadModule\TestBadModule.psd1"
 $violations = Invoke-ScriptAnalyzer $violationFilepath | Where-Object {$_.RuleName -eq $missingMemberRuleName}
 $noViolations = Invoke-ScriptAnalyzer $directory\TestGoodModule\TestGoodModule.psd1 | Where-Object {$_.RuleName -eq $missingMemberRuleName}
@@ -30,9 +33,9 @@ Describe "MissingRequiredFieldModuleManifest" {
             $violations.SuggestedCorrections.Count | Should Be $numExpectedCorrections
         }
 
-
-	    It "has the right suggested correction" {
-	        $expectedText = @'
+    # On Linux, mismatch in line endings cause this to fail
+	It "has the right suggested correction" -Skip:(Test-PSEditionCoreCLRLinux) {
+	   $expectedText = @'
 # Version number of this module.
 ModuleVersion = '1.0.0.0'
 '@