Re: Testing requirements page re-written

Thanks so much for doing this work, François! WAI has been looking at
this update to the requirements and like it very much. We have minor
notes here and there that are mostly editorial; we plan to complete this
review in a couple weeks. This is a good basis for us to work from now.

Michael

Francois Daoust wrote:
> Hi,
>
> I was reviewing the lists of requirements we have, and wondering how
> to merge plh's and Michael Cooper's approaches. I thought I'd give it
> a try re-writing requirements in more actionable sentences that apply
> to functional units of the testing framework to be, à la:
>
>  "The test runner must allow a test to report its result automatically"
>
> The result is visible at:
>  http://www.w3.org/wiki/Testing/Requirements
>
> It is slightly ugly to the eye, I must say, because of the use of
> headings throughout the page, but I kind of realized that too late...
>
> The list of requirements of that new page is a merge between those of
> the previous version and those who appear on Michael's page. Most
> requirements were the same from what I can tell, and I did not find
> requirements that would go in opposite directions.
>
> Apart from the comments below, I don't think I've dropped any other
> requirement from either of the two previous pages, although I've
> re-ordered and re-written some of them.
>
> Do you find it useful? If not, feel free to rollback to previous version.
>
> Michael, a few comments on your list:
>
> * the use cases section looks more like general requirements than real
> use cases. I turned them into requirements that apply at the "testing
> framework" level.
>
> * There are a few things for which I'm not sure I understand what you
> mean and how to turn that into requirements:
>  - the Accessibility support database section. I included a link in
> the "improve interoperability" requirement.
>  - "Test cases agnostic to how they're run" section: I'm not sure I
> captured that correctly
>  - Multi-file tests: I don't understand what that means
>  - Types of test files: what does it mean to support these types of
> test files?
>
> Thanks,
> Francois.
>

-- 

Michael Cooper
Web Accessibility Specialist
World Wide Web Consortium, Web Accessibility Initiative
E-mail cooper@w3.org <mailto:cooper@w3.org>
Information Page <http://www.w3.org/People/cooper/>