Eye Tracking Data Analysis for GUI Testing Coverage

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

GUI testing faces challenges in automation due to its interactive nature, leading to inefficiencies in managing and maintaining large test cases, which complicates determining coverage criteria and consumes significant system resources.

Innovation Solution

Utilizing eye-gazing technology to track user focus on GUI elements, analyzing this data to determine UI coverage, and adjusting test cases accordingly to ensure comprehensive testing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If traditional code-based coverage criteria are used for GUI testing, then testing can be automated to some extent, but the testing coverage does not accurately reflect user experience and interaction patterns

Engineering Contradiction:

Improvetesting coverage accuracyVSAvoidautomation difficulty

Core Design Contradiction:

Measurement precisionVSEase of operation

Solution Approach 1:

The patent introduces eye tracking technology as an intermediary between traditional code-based testing and user experience measurement. Eye tracking data serves as a mediator that captures actual user interaction patterns, allowing the system to bridge the gap between automated testing capabilities and human-centered usability assessment without requiring full manual testing intervention

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces traditional mechanical/manual testing methods with automated eye tracking-based testing. By substituting human observer analysis with automated eye tracking devices and software analysis, the system achieves both high measurement precision in capturing user focus patterns and full automation capability, eliminating the contradiction between accurate user experience measurement and automation difficulty

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If comprehensive test cases are created to cover all GUI elements, then testing coverage is improved, but the number of test cases becomes unmanageably large and maintenance becomes difficult

Engineering Contradiction:

Improvetesting coverageVSAvoidtest case management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts only the most relevant testing information from comprehensive test cases by using eye tracking data to identify which GUI elements actually receive user attention. This extraction process filters out unnecessary test cases for elements that users never interact with, maintaining high reliability for critical elements while dramatically reducing the overall number of test cases that need to be managed and maintained

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies different testing depths and priorities to different regions of the GUI based on eye tracking data. High-priority elements that receive frequent user attention undergo rigorous testing, while low-priority elements receive minimal testing. This local quality approach ensures comprehensive coverage of critical areas without requiring exhaustive testing of all elements, thereby reducing test case management complexity while maintaining reliability

Inventive Principle:

Principle #3Local quality

3Reliability

If a large number of test cases are executed to ensure comprehensive coverage, then testing thoroughness is improved, but the time and system resources required become excessive

Engineering Contradiction:

Improvetesting thoroughnessVSAvoidtesting efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent applies partial action by executing only the necessary subset of test cases identified through eye tracking analysis. Instead of running all possible test cases, the system performs testing on a partial set that corresponds to actually-used GUI elements, achieving sufficient thoroughness for user-critical functionality while dramatically improving testing efficiency by eliminating redundant test case executions

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The patent changes the parameter of test case selection from static code-based coverage criteria to dynamic eye-tracking-based user behavior data. This parameter change allows the testing system to adaptively adjust which test cases are executed based on actual user interaction patterns, ensuring thorough testing of relevant elements while reducing overall testing time and resource consumption by excluding irrelevant test cases

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS10372591B2Applying eye trackers monitoring for effective exploratory user interface testing

Publication Date: 2019.08.06 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

Embodiments are directed to analyzing eye tracking data collected from an end user to identify user attention and focus areas in user interface (UI) application screens. These areas can be extracted and mapped to a concrete UI component or particular UI object on the display, such as a column or row in a displayed table. Analyzed collected eye tracking data are reflected back to the UI testing, providing information for additional test cases. The test data indicates how the user interacts with the system to determine if desired conditions are achieved. By capturing the user attention areas on the application UI and identifying shifts in user attention based on the displayed data, methods disclosed herein provide a valuable input to the automated test cases, greatly increasing test covering and more accurately mimicking the user application interaction and experience.