# PR Summary Wrap tests in pester blocks to prepare for pesterv5 ## PR Context <!-- Provide a little reasoning as to why this Pull Request helps and why you have opened it. --> ## PR Checklist - [x] [PR has a meaningful title](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission) - Use the present tense and imperative mood when describing your changes - [x] [Summarized changes](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission) - [x] [Make sure all `.h`, `.cpp`, `.cs`, `.ps1` and `.psm1` files have the correct copyright header](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission) - [x] This PR is ready to merge and is not [Work in Progress](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---work-in-progress). - If the PR is work in progress, please add the prefix `WIP:` or `[ WIP ]` to the beginning of the title (the `WIP` bot will keep its status check at `Pending` while the prefix is present) and remove the prefix when the PR is ready. - **[Breaking changes](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#making-breaking-changes)** - [x] None - **OR** - [ ] [Experimental feature(s) needed](https://github.com/MicrosoftDocs/PowerShell-Docs/blob/staging/reference/6/Microsoft.PowerShell.Core/About/about_Experimental_Features.md) - [ ] Experimental feature name(s): <!-- Experimental feature name(s) here --> - **User-facing changes** - [x] Not Applicable - **OR** - [ ] [Documentation needed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission) - [ ] Issue filed: <!-- Number/link of that issue here --> - **Testing - New and feature** - [x] N/A or can only be tested interactively - **OR** - [ ] [Make sure you've added a new test if existing tests do not effectively test the code changed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#before-submitting) - **Tooling** - [x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted. - **OR** - [ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include: - Impact on [PowerShell Editor Services](https://github.com/PowerShell/PowerShellEditorServices) which is used in the [PowerShell extension](https://github.com/PowerShell/vscode-powershell) for VSCode (which runs in a different PS Host). - Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features. - Impact on [PSScriptAnalyzer](https://github.com/PowerShell/PSScriptAnalyzer) (which provides linting & formatting in the editor extensions). - Impact on [EditorSyntax](https://github.com/PowerShell/EditorSyntax) (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
82 lines
2.7 KiB
PowerShell
82 lines
2.7 KiB
PowerShell
# Copyright (c) Microsoft Corporation.
|
|
# Licensed under the MIT License.
|
|
|
|
Describe "ConvertFrom-Csv" -Tags "CI" {
|
|
|
|
BeforeAll {
|
|
$testObject = "a", "1"
|
|
$testcsv = Join-Path -Path (Join-Path -Path $PSScriptRoot -ChildPath assets) -ChildPath TestCsv2.csv
|
|
$testName = "Zaphod BeebleBrox"
|
|
$testColumns = @"
|
|
a,b,c
|
|
1,2,3
|
|
"@
|
|
$testTypeData = @"
|
|
#TYPE My.Custom.Object
|
|
a,b,c
|
|
1,2,3
|
|
"@
|
|
}
|
|
|
|
It "Should be able to be called" {
|
|
{ ConvertFrom-Csv -InputObject $testObject } | Should -Not -Throw
|
|
}
|
|
|
|
It "Should be able to pipe" {
|
|
{ $testObject | ConvertFrom-Csv } | Should -Not -Throw
|
|
}
|
|
|
|
It "Should have expected results when using piped inputs" {
|
|
$csvContent = Get-Content $testcsv
|
|
$actualresult = $csvContent | ConvertFrom-Csv
|
|
|
|
,$actualresult | Should -BeOfType System.Array
|
|
$actualresult[0] | Should -BeOfType PSCustomObject
|
|
|
|
#Should have a name property in the result
|
|
$actualresult[0].Name | Should -Be $testName
|
|
}
|
|
|
|
It "Should be able to set a delimiter" {
|
|
{ $testcsv | ConvertFrom-Csv -Delimiter ";" } | Should -Not -Throw
|
|
}
|
|
|
|
It "Should actually delimit the output" {
|
|
$csvContent = Get-Content $testcsv
|
|
$actualresult = $csvContent | ConvertFrom-Csv -Delimiter ";"
|
|
|
|
,$actualresult | Should -BeOfType System.Array
|
|
$actualresult[0] | Should -BeOfType PSCustomObject
|
|
|
|
# ConvertFrom-Csv takes the first line of the input as a header by default
|
|
$actualresult.Length | Should -Be $($csvContent.Length - 1)
|
|
}
|
|
|
|
It "Should be able to have multiple columns" {
|
|
$actualData = $testColumns | ConvertFrom-Csv
|
|
|
|
$actualLength = $($( $actualData | Get-Member) | Where-Object {$_.MemberType -eq "NoteProperty" }).Length
|
|
|
|
$actualLength | Should -Be 3
|
|
}
|
|
|
|
It "Should Contain the Imported Type data" {
|
|
$actualData = $testTypeData | ConvertFrom-Csv
|
|
$actualData.PSObject.TypeNames.Count | Should -Be 2
|
|
$actualData.PSObject.TypeNames[0] | Should -BeExactly "My.Custom.Object"
|
|
$actualData.PSObject.TypeNames[1] | Should -BeExactly "CSV:My.Custom.Object"
|
|
}
|
|
}
|
|
|
|
Describe "ConvertFrom-Csv DRT Unit Tests" -Tags "CI" {
|
|
It "Test ConvertFrom-Csv with pipelined InputObject and Header" {
|
|
$inputObject = [pscustomobject]@{ First = 1; Second = 2 }
|
|
$res = $inputObject | ConvertTo-Csv
|
|
$result = $res | ConvertFrom-Csv -Header "Header1","Header2"
|
|
|
|
$result[0].Header1 | Should -BeExactly "First"
|
|
$result[0].Header2 | Should -BeExactly "Second"
|
|
$result[1].Header1 | Should -BeExactly "1"
|
|
$result[1].Header2 | Should -BeExactly "2"
|
|
}
|
|
}
|