When we looked at Input Space Partitioning, we said that there are a few good places to
look when trying to come up with characteristics. So in your explanation of why a
characteristic is appropriate, you might just appeal to one of those.
If you just give a characteristic with *no* explanation of how you got it, that won't in
general be considered a very good answer.
Apologies, but it's hard to be more specific than that without further information.
If you like, you can email me the example you're thinking of, and I can at least say
whether or not it is totally off-track as a justification.
> Hi, 1d states that we should "Explain why they (characteristics) are appropriate,> and how you would use them in writing unit tests." Is there any justification we > should be looking at in particular in this case?