Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

win_pester path behavior changed to match Pester behavior #56677

wants to merge 5 commits into
base: devel


None yet
3 participants
Copy link

commented May 20, 2019


Fix supplying directory path to only execute *.tests.ps1 files, using Pester's built-in test searching functionality.

Fixes #55736

  • Bug Fix Pull Request



Previously, win_pester would search for '.ps1' files in the directory supplied to 'Path:', and then execute 'Invoke-Pester' against each file. This is different from Pester's behavior, which only executes against '.tests.ps1' files. Due to this divergent behavior, the win_pester module could inadvertently execute code that changes your system state when you are attempting to execute tests.

Pester also will search supplied paths itself, so searching for the files to execute within the win_pester module was unnecessary.

Also, I converted the module from using 'Ansible.ModuleUtils.Legacy' to using 'Ansible.Basic'

The behavior when a single test file is passed has not changed.


This comment has been minimized.

clcaldwell added some commits May 20, 2019

@ansibot ansibot added needs_revision and removed core_review labels May 20, 2019

@samdoran samdoran removed the needs_triage label May 23, 2019


This comment has been minimized.

Copy link

commented May 31, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.