libtest `--ignored` vs `--include-ignored`

[epage]

        --include-ignored
                        Run ignored and not ignored tests
        --ignored       Run only ignored tests

The problem is --ignored requires knowing whether a test is ignored a priori which is unknown when dealing with runtime ignoring.

Currently libtest2 treats --ignored as --include-ignored. What is the right behavior to specify though?

[epage]

One option might be to deprecated --ignored.

[epage]

This gets into several workflow questions.

Someone may not want a test to run because

• prerequisites are not available (e.g. cargo has tests that require hg to be installed)
• the test may be buggy and the user just doesn't want to deal with it right now

We may want another state for tests that are unrunnable. Would that remove most of the use case for runtime ignoring?