Test Plan

I write this article as a test plan for this project. All the test cases must be passed before a new version is published to the public.

Guarantee List:

• Android 2.3+
• iOS 8
• Windows Phone 8.1
• IE 9+
• Chrome
• Firefox

Case 1: Recognize the correct touch type

In order to get a better performance, we use different touch API provided by browser vendors for different platforms. It's important to make sure the correct API is used in a specific device.

Case 2: The swipeStart event is triggered as expected

1. Put a finger on the screen.
2. Look at the debug area.

Expected Result:

The swipeStart string was found in the div#debug.

Case 3: The swipeProgress event is triggered as expected

1. Put a finger on the screen.
2. Move the finger on the screen.
3. Look at the debug area.

Expected Result:

We can see movedPageX and movedPageY values in the div#debug.

Case 4: The swipe event is triggered as expected

1. Put a finger on the screen.
2. Move the finger on the screen.
3. Lift up your finger.
4. Look at the debug area.

Expected Result:

We can see swipe in the div#debug.

Case 5: The swipeLeft event is triggered as expected

1. Put a finger on the screen.
2. Move the finger to the left of the screen.
3. Lift up your finger.
4. Look at the debug area.

Expected Result:

The swipeLeft string was found in the div#debug.

Case 6: The swipeRight event is triggered as expected

1. Put a finger on the screen.
2. Move the finger to the right of the screen.
3. Lift up your finger.
4. Look at the debug area.

Expected Result:

The swipeRight string was found in the div#debug.

Case 7: The swipeUp event is triggered as expected

1. Put a finger on the screen.
2. Move the finger to the top of the screen.
3. Lift up your finger.
4. Look at the debug area.

Expected Result:

The swipeUp string was found in the div#debug.

Case 8: The swipeDown event is triggered as expected

1. Put a finger on the screen.
2. Move the finger to the bottom of the screen.
3. Lift up your finger.
4. Look at the debug area.

Expected Result:

The swipeDown string was found in the div#debug.

Case 9: The swipeCancel event is triggered as expected

1. Put a finger on the screen.
2. Move the finger for a short distance.
3. Lift up your finger.
4. Look at the debug area.

Expected Result:

The swipeCancel string was found in the div#debug.

Links: http://www.w3.org/2010/webevents/wiki/TEv1ImplReport