Here is an example of a table used to describe when a card is selected. A card is accepted only if it matches all of the examples.
exampler.fitlibrary.AndFilterFixture | exampler.fitlibrary.exampleFixtures.CardFixture | ||
description | example | counterexample | |
the right manufacturer | Bicycle, Bingo | Zed | |
the right color | red | black | |
the number is prime | 2, 3, 5, 7 | 4, Ace, Queen | |
the card is unrumpled | yes | no |
Here, a card is accepted if it matches any of the examples.
exampler.fitlibrary.OrFilterFixture | exampler.fitlibrary.exampleFixtures.CardFixture | ||
description | example | counterexample | |
the right manufacturer | Bicycle, Bingo | Zed | |
the right color | red | black | |
the number is prime | 2, 3, 5, 7 | 4, Ace, Queen | |
the card is unrumpled | yes | no |
If all of the categories to check have yes/no true/false values, you don't need to give the examples and counterexamples.
exampler.fitlibrary.OrFilterFixture | exampler.fitlibrary.exampleFixtures.CardFixture | ||
description | |||
the card is unrumpled | |||
the card is face up |
You can mix and match explicit and default values, but that's probably more trouble than it's worth because, at least for the moment, you have to make the description column span the row. (That way, the fixture can distinguish between an omitted value and an intentional null value.)
exampler.fitlibrary.OrFilterFixture | exampler.fitlibrary.exampleFixtures.CardFixture | |
description | example | counterexample |
the card is unrumpled | ||
the number is prime | 2, 3, 5, 7 | 4, Ace, Queen |