Cross-Browser Web Testing Tool with Tolerance-Based Attribute Comparison

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cross-browser web application testing is challenging due to differences in how web browsers render web pages, making it difficult to identify and validate rendering discrepancies across various browsers.

Innovation Solution

A system and method that allows users to select multiple web browsers, specify test fields and attributes, set tolerance values for rendering errors, and generate reports on comparisons between browsers, including error, warning, and pass flags, to highlight rendering differences.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If comprehensive attribute comparison is performed across multiple browsers, then measurement precision is improved, but device complexity increases

Engineering Contradiction:
Improverendering comparison accuracyVSAvoidtesting system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The testing system segments the web page into multiple test fields (elements, attributes, and values) that can be independently compared across browsers. Each test field represents a discrete unit of comparison, allowing the system to manage complexity by breaking down the overall rendering comparison into manageable segments rather than attempting to analyze the entire page as a single unit.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system allows users to specify tolerance values for different attributes, changing the comparison parameters dynamically. By adjusting tolerance thresholds, the system can adapt the measurement precision to match the specific requirements of different attributes (e.g., stricter tolerance for text content, more lenient tolerance for positioning), thereby improving overall measurement accuracy without uniformly increasing system complexity across all comparisons.

Inventive Principle:
Principle #35Parameter changes

2Loss of information

If detailed error reporting is generated for all attributes, then information completeness is improved, but loss of information increases due to report complexity

Engineering Contradiction:
Improverendering discrepancy detectionVSAvoidreport generation complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The reporting system applies local quality by providing detailed error information specifically for test fields that exhibit rendering discrepancies, while summarizing or omitting details for fields that pass comparison. Error flags, warning flags, and pass flags are selectively generated based on the actual comparison results, ensuring that comprehensive error reporting is focused only where needed rather than uniformly applied to all attributes, thus reducing overall report complexity.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system generates simplified copy representations of the rendering discrepancies through standardized flag indicators (error flags, warning flags, pass flags) that convey the essence of comparison results without requiring detailed analysis of every attribute difference. These flag copies provide a condensed summary that preserves the critical information about rendering issues while avoiding the complexity of reporting every single attribute variation in detail.

Inventive Principle:
Principle #26Copying

3Manufacturing precision

If tolerance values are set for all attributes, then manufacturing precision is improved, but ease of operation decreases

Engineering Contradiction:
Improverendering error controlVSAvoidtesting configuration simplicity
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The system implements partial action by allowing users to set tolerance values only for specific attributes that require precise control, rather than requiring tolerance configuration for all possible attributes. Users can selectively apply tolerance values to critical attributes (such as text content or key positioning) while leaving other attributes to use default comparison settings, thereby achieving manufacturing precision for important elements without the operational burden of configuring every single attribute.

Inventive Principle:
Principle #16Partial or excessive action

4Productivity

If multiple browsers are tested simultaneously, then productivity is improved, but device complexity increases

Engineering Contradiction:
Improvecross-browser testing efficiencyVSAvoidbrowser management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The testing system merges multiple browser testing operations into a single unified comparison framework. By combining the rendering outputs of multiple browsers and comparing them against each other and against expected values within the same test execution, the system achieves improved productivity through simultaneous multi-browser testing while managing complexity through a unified comparison engine that handles all browsers consistently rather than requiring separate testing processes for each browser.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9836385B2Cross-browser web application testing tool
Publication Date: 2017.12.05 ATOS FRANCE
  • US9836385B2 patent drawing
  • US9836385B2 patent drawing
  • US9836385B2 patent drawing

AI summary

A system for cross-browser testing of one or more web applications may include receiving user selection of web browsers, one or more test fields each corresponding to a specified web element, one or more attributes each corresponding to a specified property of a web element, and a tolerance value for each of the one or more selected attributes. A system for cross-browser testing may be configured to compare a selected attribute of each selected test field within a web page rendered by one selected browser with a corresponding attribute of a corresponding test field within the web page rendered by another selected browser relative to a selected tolerance value, and generate a report of the comparison. A system for cross-browser testing may be configured for comparisons independent of a human language used and may include a language translation module.