- From: Dominique Hazael-Massieux via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jan 2020 15:45:09 +0000
- To: public-webrtc-logs@w3.org
The test coverage system tries to automatically identify the normative pieces of the spec that needs test coverage, using the following algorithm: * anything that uses an RFC keyword is expected to need test * anything in an algorithm step (marked up with `<ol>`) is expected to need test To complete these automatic annotations, there are 3 annotations that can be set with a `class` attribute on elements: * `class="untestable"`: something that is normative, but can't be meaningfully tested (e.g. "if something unexpected happens, throw an error") * `class="no-test-needed"`: something that is part of a normative piece of the spec and flagged as such by the automatic detection of things that needs test, but that in practice doesn't need to be tested (e.g. naming the variables representing the values of a method parameters) * `class="needs-test"`: something not automatically flagged as needing test, but in fact needing test. The resulting view shows in red things that should be tested but aren't, in green the things that are tested (determined by the `data-tests` attribute), and in white the things that aren't expecting tests. -- GitHub Notification of comment by dontcallmedom Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2442#issuecomment-580314653 using your GitHub account
Received on Thursday, 30 January 2020 15:45:11 UTC