- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Feb 2020 11:53:15 +0000
- To: public-webrtc-logs@w3.org
henbos has just submitted a new pull request for https://github.com/w3c/webrtc-pc: == Chapter 8 testing: Mark what needs or doesn't need testing == First pass for issue #2466. If a section doesn't need a test, this PR explicitly marks is as "test-not-needed" (even if its an informative section). This makes it clear that we have looked at the section and made a conscious decision. If a section talks about something that needs a test, but the actual thing (e.g. algorithm) is described in more detail elsewhere, I marked it as "test-not-needed" and added an HTML comment explaining that test coverage is elsewhere. For steps that needs tests I've added the "needs-test" label. In many places I've added HTML TODO-comments for a second pass to verify that tests exists for specific behaviors. I'm trying to have the testing labels refer to specific testable behaviors wherever possible (rather than catch-all "this method needs a test" type of labels). In the second pass, I will remove the TODOs and add references to the tests or change the TODO into a comment referencing the wpt issue for adding the test. See https://github.com/w3c/webrtc-pc/pull/2475
Received on Thursday, 13 February 2020 11:53:30 UTC