8000 Multiple test fixes and improved logging for fragile tests by adityapatwardhan · Pull Request #9569 · PowerShell/PowerShell · GitHub
[go: up one dir, main page]

Skip to content

Multiple test fixes and improved logging for fragile tests#9569

Merged
adityapatwardhan merged 17 commits intoPowerShell:masterfrom
adityapatwardhan:RAFixes
May 10, 2019
Merged

Multiple test fixes and improved logging for fragile tests#9569
adityapatwardhan merged 17 commits intoPowerShell:masterfrom
adityapatwardhan:RAFixes

Conversation

@adityapatwardhan
Copy link
Member
@adityapatwardhan adityapatwardhan commented May 8, 2019

PR Summary

  • Read-Host - set the expect file to be executable
  • DotNetAPI - lookup a type instead of calling an API that does not work on all platforms
  • ExecutionPolicy - Fix test and improve logging for the test
  • GetCommand - Fix test
  • Markdown cmdlet - Fix tests on platforms that do not support VT100.
  • BasicEngine - Add more logging for fragile test. This fails intermittently.
  • TaskBasedAsyncPowerShellAPI - Add a sleep for waiting for the pipeline to start. Also added more logging.
  • HelpSystem.Online - Fix the expected environment variable as AzDevOps makes are variable all caps.

PR Context

Fix multiple test failures found while running release automation tests on multiple platforms.

PR Checklist

@adityapatwardhan adityapatwardhan changed the title Multiple test fixes and improved logging for fragile tests [WIP] Multiple test fixes and improved logging for fragile tests May 8, 2019
Copy link
Collaborator
@JamesWTruher JamesWTruher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just nits and a typo. Should probably fix the typo

@PoshChan
Copy link
Collaborator
PoshChan commented May 9, 2019

@adityapatwardhan, your last commit had 1 failures in PowerShell-CI-windows
Validate ExecutionPolicy cmdlets in PowerShell.Validate that 'Unrestricted' execution policy works on OneCore powershell.Test 'Unrestricted' execution policy. Importing D:\a\1\s\src\powershell-win-core\bin\Release\netcoreapp2.1\win7-x64\publish\Modules\Loc

Expected an exception, with FullyQualifiedErrorId 'UnauthorizedAccess,Microsoft.PowerShell.Commands.ImportModuleCommand' to be thrown, but no exception was thrown.
at <ScriptBlock>, D:\a\1\s\test\powershell\Modules\Microsoft.PowerShell.Security\ExecutionPolicy.Tests.ps1: line 688
688:                     $testScript | Should -Throw -ErrorId $expectedError

@adityapatwardhan adityapatwardhan changed the title [WIP] Multiple test fixes and improved logging for fragile tests Multiple test fixes and improved logging for fragile tests May 9, 2019
@adityapatwardhan
Copy link
Member Author

@JamesWTruher I have addressed your comments. Please have another look.

@adityapatwardhan adityapatwardhan merged commit ade85b4 into PowerShell:master May 10, 2019
@adityapatwardhan adityapatwardhan deleted the RAFixes branch May 10, 2019 17:56
@TravisEz13
Copy link
Member

Does this need to be back ported?

@adityapatwardhan adityapatwardhan added this to the 6.2.1 milestone May 15, 2019
@TravisEz13 TravisEz13 added the CL-Test Indicates that a PR should be marked as a test change in the Change Log label May 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CL-Test Indicates that a PR should be marked as a test change in the Change Log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

0