PowerShell / PowerShell/PowerShellEditorServices
Investigate why the type completion tests don't work on Windows PowerShell
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 767
- Forks
- 266
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 1
Description
The tests added in this PR don't work in Windows PowerShell:
https://github.com/PowerShell/PowerShellEditorServices/pull/1352
Not sure why... but it might be because of the xunit test harness. In any case, the code works and the tests pass in PS7 so we skipped Windows PowerShell for now.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the type completion tests introduced in PR #1352 and inspect how the xUnit test harness runs them under Windows PowerShell versus PowerShell 7. Compare the harness behavior and test results across both environments; the work is done when the tests pass in Windows PowerShell without excluding that environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100