Add dot source tests for strange paths

Author: Robert Holt

test/PowerShellEditorServices.Test.Shared/scriptassets/Bad&name4script.ps1

@@ -0,0 +1,4 @@
+function Hello
+{
+    "Bye"
+}

test/PowerShellEditorServices.Test.Shared/scriptassets/NormalScript.ps1

@@ -0,0 +1 @@
+Write-Output "Windows won't let me put * or ? in the name of this file..."

test/PowerShellEditorServices.Test.Shared/scriptassets/[Truly] b&d Name_4_script.ps1

@@ -1,11 +1,14 @@
 using System;
 using Xunit;
 using Microsoft.PowerShell.EditorServices;
+using System.IO;
 
 namespace Microsoft.PowerShell.EditorServices.Test.Session
 {
     public class PathEscapingTests
     {
+        private const string ScriptAssetPath = @"..\..\..\..\PowerShellEditorServices.Test.Shared\scriptassets";
+
         [Theory]
         [InlineData("DebugTest.ps1", "DebugTest.ps1")]
         [InlineData("../../DebugTest.ps1", "../../DebugTest.ps1")]
@@ -107,5 +110,23 @@ public void CorrectlyUnescapesPaths(string escapedPath, string expectedUnescaped
             string extensionUnescapedPath = PowerShellContext.UnescapeGlobEscapedPath(escapedPath);
             Assert.Equal(expectedUnescapedPath, extensionUnescapedPath);
         }
+
+        [Theory]
+        [InlineData("NormalScript.ps1")]
+        [InlineData("Bad&name4script.ps1")]
+        [InlineData("[Truly] b&d Name_4_script.ps1")]
+        public void CanDotSourcePath(string rawFileName)
+        {
+            string fullPath = Path.Combine(ScriptAssetPath, rawFileName);
+            string quotedPath = PowerShellContext.QuoteEscapeString(fullPath);
+
+            var psCommand = new System.Management.Automation.PSCommand().AddScript($". {quotedPath}");
+
+            using (var pwsh = System.Management.Automation.PowerShell.Create())
+            {
+                pwsh.Commands = psCommand;
+                pwsh.Invoke();
+            }
+        }
     }
 }