clarifying how to evaluate complete processes or transactions

Name: Shadi Abou-Zahra
Email: shadi@w3.org
Affiliation: W3C Evaluation and Repair Tools Working Group (ERT WG)
Document: W2
Item Number: Conformance Requirements
Part of Item: 
Comment Type: editorial
Summary of Issue: clarifying how to evaluate complete processes or transactions
Comment (Including rationale for any proposed change):
A complete process or transaction may include different alternative paths depending on user profiles, user tasks or other factors (e.g. a checkout process may be different depending on if the user is already logged in the system, or registered but not logged in, or a new member. It may be different also depending of the information provided by the user or the mistakes that are made while introducing data)



>From an external perspective (external reviewer or auditor) it could be hard (or even impossible) to get an idea about all the existing paths and scenarios of a process as it requires a very good knowledge of its design, so the question that arises is if all different variants need to be considered, or testing just one of the possible complete paths may be enough.

Proposed Change:
If the testing of all possible variations is going to be required, there should be a clarification about this in the guidelines and related documents to acknowledge the issue and help guide evaluators who want to review web sites (as opposed to developers building the site)

Received on Tuesday, 3 July 2007 11:02:19 UTC