W3C home > Mailing lists > Public > public-html-testsuite@w3.org > April 2010

RE: Test Case Approval Request

From: Kris Krueger <krisk@microsoft.com>
Date: Tue, 20 Apr 2010 01:43:26 +0000
To: Anne van Kesteren <annevk@opera.com>, James Graham <jgraham@opera.com>
CC: "public-html-testsuite@w3.org" <public-html-testsuite@w3.org>
Message-ID: <FA9085650D2F8B4A9D501ED9D9706E9A05EF4C@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
OK - I submitted an interface test for the HTMLAnchorElement
See -> http://dvcs.w3.org/hg/html/raw-file/tip/tests/submission/Microsoft/interface/anchor_href.htm


This is quite a simple framework and removes all the old harness code except for the assert functions.

One question would be would we rather have all the attributes tested on one page (href, target, rel, etc...) or have one page for each attribute.

-Kris

RSS Log for the repository is at https://dvcs.w3.org/hg/html/rss-log



-----Original Message-----
From: Anne van Kesteren [mailto:annevk@opera.com] 
Sent: Wednesday, April 07, 2010 9:06 AM
To: James Graham; Kris Krueger
Cc: public-html-testsuite@w3.org
Subject: Re: Test Case Approval Request

On Wed, 07 Apr 2010 17:43:22 +0200, Kris Krueger <krisk@microsoft.com>  
wrote:
> Thanks for the feedback, good for the group and the approval process.
> If I understand your feedback correctly, how about instead of moving the  
> valid 'a' tag dom tests into the approved folder.  Instead I also submit  
> case(s) for all of the 'a' tag attributes?  For example the 'a' tag dom  
> test would cover the interface listed below from the HTML5 spec.

That sounds great. I would again humble suggest we use a somewhat simpler  
framework than what these tests are made with though.


-- 
Anne van Kesteren
http://annevankesteren.nl/


Received on Tuesday, 20 April 2010 01:44:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 20 April 2010 01:44:18 GMT