Re: Invalid Test Assertions

On 6/26/13 2:24 PM, ext Scott González wrote:
> 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?

My recommendation is to just strike those two IDs (so any references to 
ID 1.13 do not have to be updated).

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

By June 27, if you don't hear any objections to `striking`, please go 
ahead and update [1] accordingly and update the tests.

-Thanks! Art

> [1]

Received on Wednesday, 26 June 2013 21:27:41 UTC