Regression tests

[andyleejordan]

This covers the desire to go back through recently merged PRs (and my own Git stashes) to see what bugs we fixed that could be covered with a regression test (for stability purposes). @SydneyhSmith we can use this for tracking!

Completed test work:

• Enable PsesInternalHostTests (previously PowerShellContextTests) #1651
• Run new PSReadLine test on Windows #1522
• Add Emacs regression tests for PSES #1820 / PSES Stdio mode broken since v3.0.0 #1695
• Add regression test for no defined profiles #1821 / Fix startup bug when zero profiles are present #1807
• Add regression test for accidentally allowing removal of $psEditor #1828 / Remove-Variable can cause cls and Clear-Host to throw You cannot call a method on a null-valued expression. vscode-powershell#3718
• Add regression test for untitled scripts in Windows PowerShell #1830 / Unsaved Script Errors Out If Last Line is Commented vscode-powershell#3965
• Improve $PROFILE variable and profile loading test #1832 / Fix profile loading and $PROFILE variable #1604
• Custom prompt function no longer sees PSDebugContext vscode-powershell#3980 / Add regression test for $PSDebugContext in prompt function #1857
• Use HostInfo.BundledModulePath to find PSScriptAnalyzer #1864 / Locally installed PSScriptAnalyzer module takes precedence over bundled one vscode-powershell#2697
• Fix bug where error in prompt function crashed REPL #1866 / Visual Studio Code Host hogs CPU and floods error log with error "Unrecognized option: --version" vscode-powershell#4073
• Add regression test for debugging script with dot-source operator #1858 / F5 on a saved script isn't dot sourcing vscode-powershell#3715
• Add DebuggerBreaksInUntitledScript unit test #1861 / Run Launch config on unsaved File is broken vscode-powershell#3655
• Handle edge case where prompt is undefined #1710 / Crash when prompt is undefined in the runspace #1699
• Add DoesNotDuplicateScriptMarkersAsync regression test #1870 / Duplicate PSSA-entries in Problem-tab after reopening file vscode-powershell#3252
• Add end-to-end integration test with Vim #1874 / Failed to load PowerShellEditorServices with lspconfig (nvim) #1663
• Add end-to-end Pester unit test #1846 / Null dereference when debugging Pester tests #1672
• Fix symbol highlight when hovering function name #1890 / Hovering function name doesn't work when function is indented #1887
• Fix whitespace in Pester symbol and add test #1893 / Pester symbols have leading whitespace in search #1891
• Failed to load PowerShellEditorServices with lspconfig (nvim) #1663 / Add end-to-end integration test with Vim #1874
• VSCode PowerShell Preview PSES no longer shows history from previous F8/F5 command in buffer vscode-powershell#3683 / Add regression tests for F5 and F8 saving to history #1914
• Fix piping to native commands for Windows PowerShell #1836 / Git STDIN not working from PowerShell Integrated Console on Windows PowerShell vscode-powershell#4021

Remaining test work

Debugging

• Synchronize PowerShell debugger and DAP server state #1685
• Avoid recording debugger commands in the history #1704
• CTRL+C stops debugging when stopped on breakpoint vscode-powershell#3832
• Fix attach to process debugging vscode-powershell#3849
• Fix prompt spam and general debugger reliability improvements #1762
• Fix extra prompting and manual debugger commands #1778
• F8 during debug session forces continuation vscode-powershell#3944
• Temporary integrated consoles stuck waiting for key press vscode-powershell#3950

Host

• Write-Host -NoNewLine and -*Color does not work #1667
• After eval with F8, PSReadLine prompt appears in command output vscode-powershell#3685
• Fix printing of command with F5 #1692
• Write-Progress not cleaned up unless -Complete is explicitly specified vscode-powershell#3807
• Cursor position is set with wrong values after finish running a git command in integrated console #1639
• Bring back WriteWithPrompt() #1781
• PSIC> spam when using Stop button with -ErrorAction Break and nested scopes vscode-powershell#4010
• Changes from #1571 are missing from preview #1603
• Display the command that is running in the PowerShell console on the same line vscode-powershell#3786

IntelliSense

• Fix a lot of IntelliSense issues #1799 (this may not belong in this list)
• SymbolService.FindFunctionDefinitionAtLocation()

PSSA

• Return a code action for each diagnostic record #1718
• Correctly map SuggestedCorrection to MarkerCorrection #1749
• Weird formatting issues vscode-powershell#3928

Startup

• Load only bundled PSReadLine #1514
• Added check to see if PSModulePath already contained BundledModulePath #1641

Non-VSCode

[andyleejordan]

@SydneyhSmith How are we tracking in here which are done or not?

[SydneyhSmith]

@SydneyhSmith How are we tracking in here which are done or not?

Was thinking moving from the remaining work section to the completed work section

[SydneyhSmith]

Next item is to create a doc of manual tests to complete for releases...assigning to myself