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

Fix #1290: Ignore only class level parameters in NUnit tests is not possible #1291

Merged
merged 2 commits into from
Sep 18, 2024

Conversation

tom-englert
Copy link
Contributor

@tom-englert tom-englert commented Sep 12, 2024

This will introduce a new setting IgnoreParameters, the parameters of this setting are the names of the parameters to be ignored.

The method UseParameters is expected to always contain all parameters, even if some of them will be ignored!
Also UseParameters needs to be called along with IgnoreParameters for test frameworks that do not support automatic parameter detection like NUnit.

@tom-englert tom-englert marked this pull request as draft September 12, 2024 12:30
@tom-englert tom-englert force-pushed the issues/#1290 branch 2 times, most recently from 773a03e to d28c16d Compare September 12, 2024 13:19
@tom-englert tom-englert marked this pull request as ready for review September 12, 2024 13:21
@SimonCropp
Copy link
Member

Since the parameters passed to IgnoreParametersForVerified had no meaning/effect before (always all parameters were ignored), this should be an acceptable change.

i dont think this is true. the parameters passed in are used to prevent conflicts in received files

@tom-englert
Copy link
Contributor Author

I see, maybe this was only true for NUnit, because there UseParameters is optional...
Let me rethink this

@tom-englert tom-englert marked this pull request as draft September 13, 2024 06:15
…ts is not possible => New setting "IgnoreParameters" allows to ignore explicit parameters.
@tom-englert tom-englert marked this pull request as ready for review September 13, 2024 08:09
@tom-englert
Copy link
Contributor Author

OK, introduced a new setting, so it does not collide with the original one

@SimonCropp SimonCropp added this to the 26.5.0 milestone Sep 18, 2024
@SimonCropp
Copy link
Member

thanks. will include in the next release

@SimonCropp SimonCropp merged commit da9e9bc into VerifyTests:main Sep 18, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants