Add touch and basic longpress typing tests for the IME keyboard.

Add touch and basic longpress typing tests for the IME keyboard.

To be landed after: https://codereview.chromium.org/247883002/

BUG=353857

[rsadam, 2014-04-24 17:45:04]

This is a followup patch to the test framework.

PTAL Biao!

https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
File chrome/test/data/chromeos/virtual_keyboard/inputview/test_base.js (right):

https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
chrome/test/data/chromeos/virtual_keyboard/inputview/test_base.js:210: //
TODO(rsadam:) Add support for touch move here once latest CRX uploaded to
The current CRX uses the delta in screen position between events, whereas the
new one uses pagex in touches. Waiting for the new one to be uploaded before
mocking touchmove.

[bshe, 2014-04-24 18:36:25]

https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
File chrome/test/data/chromeos/virtual_keyboard/inputview/test_base.js (right):

https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
chrome/test/data/chromeos/virtual_keyboard/inputview/test_base.js:77: */
Assume this will be used when add upper case tests? If so, could you add this
function in that CL?

https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
chrome/test/data/chromeos/virtual_keyboard/inputview/test_base.js:154: * @param
{Object} The object to check.
nit: document return value

https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
chrome/test/data/chromeos/virtual_keyboard/inputview/test_base.js:212:
generateTouchEvent(key, 'touchend', true, true)
should the touchend dispatched by candidate?

https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
File chrome/test/data/chromeos/virtual_keyboard/inputview/typing_test.js
(right):

https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
chrome/test/data/chromeos/virtual_keyboard/inputview/typing_test.js:11: // Mouse
events.
We probably dont need to test the same case 5 times? Perhaps just test l and p
(e and a for long press) is enough?

[rsadam, 2014-04-24 21:23:25]

https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
File chrome/test/data/chromeos/virtual_keyboard/inputview/test_base.js (right):

https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
chrome/test/data/chromeos/virtual_keyboard/inputview/test_base.js:77: */
On 2014/04/24 18:36:25, bshe wrote:
> Assume this will be used when add upper case tests? If so, could you add this
> function in that CL?

Done.

https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
chrome/test/data/chromeos/virtual_keyboard/inputview/test_base.js:154: * @param
{Object} The object to check.
On 2014/04/24 18:36:25, bshe wrote:
> nit: document return value

Done.

https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
chrome/test/data/chromeos/virtual_keyboard/inputview/test_base.js:212:
generateTouchEvent(key, 'touchend', true, true)
On 2014/04/24 18:36:25, bshe wrote:
> should the touchend dispatched by candidate?

I believe the W3 spec is for the target to be same the same, otherwise it
interprets it as a second finger.

https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
File chrome/test/data/chromeos/virtual_keyboard/inputview/typing_test.js
(right):

https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
chrome/test/data/chromeos/virtual_keyboard/inputview/typing_test.js:11: // Mouse
events.
On 2014/04/24 18:36:25, bshe wrote:
> We probably dont need to test the same case 5 times? Perhaps just test l and p
> (e and a for long press) is enough?

Done.

[bshe, 2014-04-29 16:02:05]

On 2014/04/24 21:23:25, rsadam wrote:
>
https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
> File chrome/test/data/chromeos/virtual_keyboard/inputview/test_base.js
(right):
> 
>
https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
> chrome/test/data/chromeos/virtual_keyboard/inputview/test_base.js:77: */
> On 2014/04/24 18:36:25, bshe wrote:
> > Assume this will be used when add upper case tests? If so, could you add
this
> > function in that CL?
> 
> Done.
> 
>
https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
> chrome/test/data/chromeos/virtual_keyboard/inputview/test_base.js:154: *
@param
> {Object} The object to check.
> On 2014/04/24 18:36:25, bshe wrote:
> > nit: document return value
> 
> Done.
> 
>
https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
> chrome/test/data/chromeos/virtual_keyboard/inputview/test_base.js:212:
> generateTouchEvent(key, 'touchend', true, true)
> On 2014/04/24 18:36:25, bshe wrote:
> > should the touchend dispatched by candidate?
> 
> I believe the W3 spec is for the target to be same the same, otherwise it
> interprets it as a second finger.
> 
>
https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
> File chrome/test/data/chromeos/virtual_keyboard/inputview/typing_test.js
> (right):
> 
>
https://codereview.chromium.org/259603002/diff/1/chrome/test/data/chromeos/vi...
> chrome/test/data/chromeos/virtual_keyboard/inputview/typing_test.js:11: //
Mouse
> events.
> On 2014/04/24 18:36:25, bshe wrote:
> > We probably dont need to test the same case 5 times? Perhaps just test l and
p
> > (e and a for long press) is enough?
> 
> Done.

lgtm