This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
"5 Good Practice C: Write sample code or tests" -- another technique is to go back and create new tests for old sections once the sections are better understood and more mature. It also helps to write tests that check the interactions of different sections. Also, especially when using test assertions, the temptation is to have one (or more) tests per assertion. However, one must absolutely check the _interactions_ of assertions, as that is where most bugs are likely to be found. For example, the two assertions "when X happens, A must happen" and "when Y happens, B must happen" can be tested individually, but they must also be checked together, to ensure that if X and Y both happen, first A happens then B happens, etc.
http://lists.w3.org/Archives/Public/www-qa-wg/2005Feb/0021.html (dh) Mostly editorial, suggesting that an additional requirement is to go back an create tests for "old" sections, once they have matured. You also need to check interactions between tests, separate tests not enough (tb) Do we want to recommend against having interactive assertions? (dh) The idea of atomic assertions? (tb) Right (dm) That depends on the technology, for some technologies you have a necessary impact between things (kd) The comment is good but a bit out of scope, it's about how to write good tests, not about Spec GL. We could add a line, not sure if we should change a lot of things. I take that action item
http://lists.w3.org/Archives/Public/www-qa-wg/2005Feb/0028.html KD wrote something to clarify http://lists.w3.org/Archives/Public/www-qa-wg/2005Feb/0008 There being no objections to his revisions, this item is now resolved.
setting version to LC in case of future use