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

Add usage page about filters #242

Open
fflaten opened this issue Dec 26, 2022 · 1 comment
Open

Add usage page about filters #242

fflaten opened this issue Dec 26, 2022 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@fflaten
Copy link
Collaborator

fflaten commented Dec 26, 2022

Consider rewriting Tags-page to be about filters in general. Should explain behavior when multiple filters are used like exclude/include/explicit priority. The latter is only indirectly mentioned on other pages, including deprecated v4-parameters in Invoke-Pester command ref.

I have a PesterConfiguration with two filter options set - $configuration.Filter.Tag and $configuration.Filter.FullName.

I expected, that the both filters will apply to the subset of tests and it'll narrow down the search so only specified tests that has the selected tag will be run. Pester works in a different manner. It creates a union of two filters so all the tests specified in $configuration.Filter.FullName will be launched as well as all the tests having $configuration.Filter.Tag tags.

If that's the strategy we expect from Pester, maybe we could mention this behavior it in the New-PesterConfiguration Filter documentation.

Originally posted by @tempora-mutantur in pester/Pester#2278 (comment)

@fflaten
Copy link
Collaborator Author

fflaten commented Dec 26, 2022

Resource: pester/Pester#1442

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant