René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Tests (especially Get-FileHash) depend on machine-specific details","articleBody":"\u003c!--\r\n\r\nFor Windows PowerShell 5.1 issues, suggestions, or feature requests please use the following link instead:\r\n- Windows PowerShell [UserVoice](https://windowsserver.uservoice.com/forums/301869-powershell)\r\n\r\nIf it is a bug report:\r\n- make sure you are able to repro it on the latest released version. \r\nYou can install the latest version from https://github.com/PowerShell/PowerShell/releases\r\n- Search the existing issues.\r\n- Refer to the [FAQ](https://github.com/PowerShell/PowerShell/blob/master/docs/FAQ.md).\r\n- Refer to the [known issues](https://github.com/PowerShell/PowerShell/blob/master/docs/KNOWNISSUES.md).\r\n- Fill out the following repro template:\r\n\r\nIf it's not a bug, please remove the template and elaborate the issue in your own words.\r\n--\u003e\r\n\r\nThere are a number of tests in the PowerShell test suite that depend on a file asset in a way that depends on the specific bytes of the file. These tests fail on platforms that somehow differ from the expected encodings. For example, my Git configuration converts LF line endings to CRLF locally on Windows when checking out (and converts back on check-in), which is the default Git configuration on Windows, but because of this and Windows introducing a BOM, my file hashes come out differently.\r\n\r\nI've made a small list of the tests I see failing on my machine because of this:\r\n- [x] Get-FileHash tests depend on file encoding -- CRLF/BOM breaks it\r\n- [ ] A Get-Process test depends on having a process with the name \"notepad\"\r\n- [ ] Write-Error ErrorRecord tests seem to be affected (get 11 and not the expected 4)\r\n- [ ] Get-PSSessionConfiguration assumes there is only a single PSSessionConfiguration on the machine\r\n- [ ] NativeStreams testing using the `$longtext` like in the Write-Error tests have a similar outcome\r\n\r\nThere might be a couple more tests like this too (I will update if I find any).\r\n\r\nFor the string/encoding-dependent tests, my suggestion is to use byte streams directly instead.\r\n\r\nSteps to reproduce\r\n------------------\r\n\r\n```powershell\r\ncd $powershellBuildDir\r\nImport-Module ./build.psm1\r\ncd ./test/powershell/Modules/Microsoft.PowerShell.Utility\r\nStart-PSPester Get-FileHash.Tests.ps1\r\n```\r\n\r\nExpected behavior\r\n-----------------\r\n\r\nGet-FileHash tests pass.\r\n\r\nActual behavior\r\n---------------\r\n\r\nHashes all come out differently\r\n\r\n![Get-FileHash tests all failing on Win10](https://imgur.com/MqcloqO.jpg)\r\n\r\nEnvironment data\r\n----------------\r\n\r\n\u003c!-- provide the output of $PSVersionTable --\u003e\r\n\r\n```powershell\r\n\u003e $PSVersionTable\r\n\r\nName                           Value\r\n----                           -----\r\nPSVersion                      6.0.1\r\nPSEdition                      Core\r\nGitCommitId                    v6.0.1-261-g71cb49a99d00ae4257e63f6564fd122325b64a48\r\nOS                             Microsoft Windows 10.0.16299 \r\nPlatform                       Win32NT\r\nPSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}\r\nPSRemotingProtocolVersion      2.3\r\nSerializationVersion           1.1.0.1\r\nWSManStackVersion              3.0\r\n\r\n\r\n```\r\n","author":{"url":"https://github.com/rjmholt","@type":"Person","name":"rjmholt"},"datePublished":"2018-03-16T20:57:03.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/6413/PowerShell/issues/6413"}