- From: Dominique Hazael-Massieux via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Apr 2019 13:41:03 +0000
- To: public-webrtc-logs@w3.org
The property which states where tests reside is `testSuiteURI` in the ReSpec configuration object. My guiding principle for where and when to use the `data-tests` attribute have been: * apply it only to content with normative language (I have had to ignore that rule in a number of cases because we have not been very consistent in our usage of normative language) * put it as high in the DOM as possible * when set on an element, you assert that the said test case provides reasonable coverage of the entirety of the element One of the expected outcome (for which I already have a proof of concept) is to get a view of what parts of the specs should be tested but aren't. Does that help? Once this guidance is clear enough, it probably should be brought into the `README.md` file -- GitHub Notification of comment by dontcallmedom Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/2156#issuecomment-479901518 using your GitHub account
Received on Thursday, 4 April 2019 13:41:04 UTC