Test.Aliasing
The test verifies that the device can track and report unique continually arriving and departing contacts without aliasing at fixed separation distances.
Test details
Associated requirements |
Device.Input.PrecisionTouchpad.Performance.MinSeparation System.Client.PrecisionTouchpad.PrecisionTouchpad |
Platforms |
Windows RT 8.1 Windows 8.1 x64 Windows 8.1 x86 |
Expected run time |
~2 minutes |
Categories |
Certification |
Type |
Manual |
Running the test
Before you run the test, complete the test setup as described in the test requirements: Mouse or other Pointing Device Testing Prerequisites.
Alternate between 2 fingers ~15mm apart, and tap the touchpad at 240 taps/minute.
When you tap, hold down a contact until it is time to make another tap with that contact, rather than making light taps (to interleave the down times of the two contacts).
Verify that after tapping for ten seconds, no line is drawn between these contacts (see Common Errors in this topic for an example of a failure).
Repeat steps 1 and 2 by having fingers aligned on the vertical axis.
Repeat steps 1 and 2 by having fingers aligned on the diagonal axis.
Manually pass the iteration if validations in all axes were successful.
Repeat steps 1 through 5 by having fingers ~40mm apart.
Troubleshooting
For troubleshooting information, see Troubleshooting Device.Input Testing.
| Error | Description/Workaround |
|---|---|
[20] Positional delta too large ### |
Aliasing caused device contact swap, thereby causing the device to report a quick swipe. The value represents the displacement distance. Any displacement > 270 (2.7mm) causes this error. |
More information
Command syntax
| Command | Description |
|---|---|
ptlogo.exe Test.Aliasing.json |
Runs the test. |
File list
| File | Location |
|---|---|
ptlogo.exe |
<testbinroot>\input\PrecisionTouchpad\ |
config.json |
<testbinroot>\input\PrecisionTouchpad\ |
Test.Aliasing.json |
<testbinroot>\input\PrecisionTouchpad\ |