- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Fri, 16 Dec 2011 08:53:31 -0500
- To: "public-webevents@w3.org" <public-webevents@w3.org>
Hi All, During our December 13 call, I took Action-89 to make a short proposal on our test directory structure. I included the bulk of the proposal in the draft agenda for that meeting: [[ http://lists.w3.org/Archives/Public/public-webevents/2011OctDec/0149.html a. Directory organization: for consistency with WebApps and HTML WGs, should the directory structure be changed: http://www.w3.org/2008/webapps/wiki/Submission#Test_Repository_Structure .../webapps/[SPECIFICATION]/ .../webapps/[SPECIFICATION]/tests/approved/ .../webapps/[SPECIFICATION]/tests/submissions/[CONTRIBUTOR]/ Giving: .../webevents/touch-events-v1/ .../webevents/touch-events-v1/tests/approved/ .../webevents/touch-events-v1/tests/submissions/Mozilla/ .../webevents/touch-events-v1/tests/submissions/Intel/ .../webevents/touch-events-v1/tests/submissions/Opera/ ]] The above organization implies a certain bit of related process and copies WebApps' process [WebApps-Testing]. WebApps process was designed to be relatively light-weight and to accommodate async participation. In addition to the above directory structure, I propose we adopt WebApps' testing processes with the understanding that we can modify any part of the process that results in WebEvents WG working "better". For instance, ATM, I don't think it is necessary to create a separate list just for testing. So, if you have any comments on: a) the directory structure; and/or b) adoptiong WebApp's testing process (with the proviso above), please send them by December 21. In the absence of any unresolvable issues, I will go ahead and start making the directory changes on December 22. -AB [WebApps-Testing] http://www.w3.org/2008/webapps/wiki/Testing Tracker: ACTION-89: Start a CfC re directory structure for WebEvents tests (Web Events Working Group)
Received on Friday, 16 December 2011 13:53:15 UTC