Jeremy Wilkins
Jeremy Wilkins
Commit 1851fbb413d1951b2334ff7ebdbab1b2d1a975bd is a good example how this should be done.
I will try to work on this, but my time is limited so it could take awhile.
@CharliePoole I know this conversation is getting dated, but I was wondering how you advise to separate CI tests which can be long-running and could involve resources that may not...
I am bringing this up because I noticed that use of the where clause `--where "cat!=Integration || cat==Integration"` actually includes all explicit tests, not just the ones in the `Integration`...
I know that where clause is a bit of a kludge, but technically speaking it should select all non-integration tests that are not explicit and any integration tests regardless whether...
@CharliePoole if I run each part of the where clause separately that is exactly the behaviour I get.
@CharliePoole if there was an include/exclude explicit at the top level of the expression I think that would simplify the behaviour. It seems to me there is a run exclusive...
@CharliePoole and @rprouse my proposal to maintain backward compatibility would be to allow explicit to be controlled by the where expression either: 1. When it is included in the where...
@CharliePoole well, the current misbehaviour with regards to the example above is definitely a "bug", yes. :smile: I was not proposing to keep that misbehaviour. I agree, adding switches to...
@CharliePoole no, I am not confused. I do clearly understand that the `/include` and `/exclude` switches are gone and backend converted to the new `--where` syntax. I was referring to...