RE: One test for multiple SC?

Hi Greg,

Good point. While I think we still need the atomic tests so that we can explain how to test a particular SC, I like the idea of grouping them.

So perhaps we look at all the tests that loop on the same thing (e.g., "For each identified alternative") and we gather them together into something like: "Tests you should do together"

Cheers,
Jan

From: Greg Lowney [mailto:gcl-0039@access-research.org]
Sent: June-19-13 9:31 PM
To: WAI-UA list
Subject: One test for multiple SC?

Hi! It seems that the current format of test script can be extremely inefficient, because it would often be much quicker to make one pass through the product testing several SC on each area, rather than to make multiple passes testing one SC each time. For example, as long as you're testing the ability to search various content types (2.4.1), you might as well test searching those types in reverse (2.4.2), scrolling to bring found content into view (2.4.3), and so forth at the same time. Is it possible for us to combine the tests for multiple SC when it makes sense, or do we have to essentially repeat the procedures for each SC?

    Thanks,
    Greg