make sure tests are run according to pester.groups #8160
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of Change
.\tests\manual.pester.ps1
)Purpose
Make sure we run only tests that are safe to run on appveyor. @andreasjordan noticed when running #8159 that a test was invoked even if it is explicitely disabled via pester.groups.ps1.
This was because the dependency tracking that kicks in when tests are filtered out by the magic keyword
(do whatever)
considered the disabled when picking up the main tests, but not all of the dependencies. This fix refilters the list AFTER picking up the dependent tests.Screenshots
Before
After