What is the expected behavior of --exclude with the datadriver (v 1.2.0)?
I have dummy suite with 6 cases generated by a custom reader, half tagged 'flip' and half 'flop' by the reader. Additionally the suite has default tag 'default'.
So when I execute
robot --include default --include flip dummysuite
the 3 cases tagged 'flip' get executed (as I expected).
But when trying to
robot --include default --exclude flip dummysuite
this results in
[ ERROR ] Suite 'dummysuite' contains no tests after model modifiers.
(while I was expecting this would result in the execution of the 'flop' cases)
Same result also with
robot --include default --exclude NOTflop dummysuite
René 9 hours ago
Hi,
I think because you have included default, but default is not added to these test cases in your datareader.
Just --exclude flip should work.
Because --include default explicitly limit the tests to those who have default attached.
The tests in the end however do have the default tag. but not at the time the list is filtered.
Not sure how this would affect existing implementations in the field, if i change that…
What is the expected behavior of --exclude with the datadriver (v 1.2.0)?
I have dummy suite with 6 cases generated by a custom reader, half tagged 'flip' and half 'flop' by the reader. Additionally the suite has default tag 'default'. So when I execute
robot --include default --include flip dummysuitethe 3 cases tagged 'flip' get executed (as I expected). But when trying torobot --include default --exclude flip dummysuitethis results in[ ERROR ] Suite 'dummysuite' contains no tests after model modifiers.(while I was expecting this would result in the execution of the 'flop' cases) Same result also withrobot --include default --exclude NOTflop dummysuiteHi, I think because you have included
default, butdefaultis not added to these test cases in your datareader. Just--exclude flipshould work. Because--include defaultexplicitly limit the tests to those who havedefaultattached. The tests in the end however do have the default tag. but not at the time the list is filtered. Not sure how this would affect existing implementations in the field, if i change that…