Before NUnit 3.0 I used the next parameter to include category of tests to execute: /include:"name"
Now in NUnit 3.0 the writing seems to be different - according to this: https://github.com/nunit/dev/wiki/Command-Line-Options
I have to use something like: -include=name
but it seems to me that correct option would be --include=name
as I write other parameters like --workers
the same way and they work.
The problems is that when I use --include
parameter I get error: "Invalid argument: --include=Selenium"
(Jenkins console shows me this error).
What am I doing wrong?
I dug dipper and somewhere found that for now there is no --include
parameter!
What we should use instead is: --where "cat==name"
cat = category. If we wanna to take priority into consideration we'll do something like this: --where "cat==name && Priority==High"
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With