Currently when you run with --contains=pattern, the only indication of a filtered run is an initial line outputting the pattern matching information.
Nothing in the test totals reflects how many tests were skipped as a result of the filter, despite the fact that Julienne's "skipped" test feature almost exactly matches the paradigm here. The only difference is the test filter is being applied on the command line instead of statically.
IMHO it would be better if tests skipped by a --contains=pattern argument were explicitly reported as "SKIPS" in the test output and added to the running total of skipped tests, because that's effectively what is happening.
Currently when you run with
--contains=pattern, the only indication of a filtered run is an initial line outputting the pattern matching information.Nothing in the test totals reflects how many tests were skipped as a result of the filter, despite the fact that Julienne's "skipped" test feature almost exactly matches the paradigm here. The only difference is the test filter is being applied on the command line instead of statically.
IMHO it would be better if tests skipped by a
--contains=patternargument were explicitly reported as "SKIPS" in the test output and added to the running total of skipped tests, because that's effectively what is happening.