Closed TylerLeonhardt closed 4 years ago
See this line of code: https://github.com/TylerLeonhardt/vscode-powershell-test-adapter/blob/master/src/pesterTests.ts#L193
Here are the possible Test Explorer states:
(property) TestEvent.state: "running" | "passed" | "failed" | "skipped" | "errored"
I'm not sure which states Pester spits out in the NUnit report but we should map those to these.
cc @nohwnd your input here on what Pester supports in NUnit reports would be helpful.
Oh I think I found it: https://github.com/pester/Pester/blob/edb9acb73461b55df397ef974d0da2a4bea6921f/src/functions/TestResults.ps1#L783-L796
See this line of code: https://github.com/TylerLeonhardt/vscode-powershell-test-adapter/blob/master/src/pesterTests.ts#L193
Here are the possible Test Explorer states:
I'm not sure which states Pester spits out in the NUnit report but we should map those to these.
cc @nohwnd your input here on what Pester supports in NUnit reports would be helpful.