PowerShell/test/powershell/engine/Api
Dongbo Wang 9b94f18ccf
Fix BeginInvoke/EndInvoke to return results when Stop or BeginStop/EndStop was called previously (#7917)
The root cause is that `OutputBuffer` is not cleaned up (set to `null`) in `Stop` and `BeginStop/EndStop` when the powershell instance owns the `OutputBuffer` object. Since the pipeline has been intentionally stopped by the caller, the `OutputBuffer` should be set to `null` as well when it's owned by the PowerShell instance, just like how it's cleaned up in `EndInvoke`.
2018-10-12 10:46:57 -07:00
..
assets Reorganize some engine tests to make it clean (#4551) 2017-08-14 13:49:28 +04:00
BasicEngine.Tests.ps1 Fix BeginInvoke/EndInvoke to return results when Stop or BeginStop/EndStop was called previously (#7917) 2018-10-12 10:46:57 -07:00
GetNewClosure.Tests.ps1 Use new Pester syntax: -Parameter for Pester tests in engine. (#6298) 2018-03-14 12:13:32 -07:00
InitialSessionState.Tests.ps1 Use new Pester syntax: -Parameter for Pester tests in engine. (#6298) 2018-03-14 12:13:32 -07:00
LanguagePrimitive.Tests.ps1 Adding 'LanguagePrimitives.TryCompare' to provide faster comparisons (#7438) 2018-08-10 10:20:27 -07:00
ProxyCommand.Tests.ps1 Use new Pester syntax: -Parameter for Pester tests in engine. (#6298) 2018-03-14 12:13:32 -07:00
Serialization.Tests.ps1 Use new Pester syntax: -Parameter for Pester tests in engine. (#6298) 2018-03-14 12:13:32 -07:00
TypeInference.Tests.ps1 Create inferred types for Select-Object, Group-Object, PSObject and Hashtable (#7231) 2018-09-19 15:43:22 -07:00