Invalid Test Assertions

We have two test assertions (1.11, 1.12) which deal with pointerId being
restricted to 1 for mouse. Since we have tests that reference the test
assertions by number, how do we handle removing these from the list? Do we
keep them numbered 1.11 and 1.12 and strike them out? Or do we delete them
and renumber 1.13?

Once we have a resolution on this, I will update the Test Assertion page
[1] and update the tests.


Received on Wednesday, 26 June 2013 18:24:38 UTC