Tuesday, July 29, 2014

Customer Finds Mobile Performance Flaw

We heard from an eValid user about a novel use of the internal timing capability to track down and fix a problem that only appeared when the application was viewed with evalid imitating a mobile device.

Their testing process involved setting up timing measurements within the DOM using the structural commands. The timing data let them to identify the fixes that were needed, and the same test setup was used to verify the performance improvement that was evident on the mobile device.
Here is the writeup they provided describing these results:

K2 Bug Repair Report (July 2014)
Click image for full size version

No comments: