Browser Extension for Automated Web Testing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional automated testing frameworks for websites require coding experience, making it difficult for non-technical personnel to create and execute test scenarios, and they lack the capability to effectively test browser extensions.

Innovation Solution

A browser extension-based testing system that allows users to record test scenarios by interacting with web pages, generating test scenarios that specify testable outcomes based on user actions and element characteristics, and executing these scenarios to determine if the expected outcomes occur.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional automated testing frameworks are used, then testing functionality can be achieved, but coding experience is required making it difficult for non-technical personnel

Engineering Contradiction:

Improveease of creating test scenariosVSAvoidcomplexity of testing framework

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

A recording intermediary component is introduced that captures user interactions with the web application and automatically translates them into test scenario code. This intermediary layer shields non-technical users from the complexity of traditional testing frameworks while still enabling comprehensive automated testing functionality.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables self-service automated testing by allowing users to record their own test scenarios through simple user interactions. The framework automatically generates the necessary test code, eliminating the need for users to manually write or understand complex testing framework syntax.

Inventive Principle:

Principle #25Self-service

2Adaptability or versatility

If traditional automated testing frameworks are used, then web pages can be tested, but they lack capability to effectively test browser extensions

Engineering Contradiction:

Improvecapability to test different targetsVSAvoideffectiveness of testing

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The testing framework is designed with universal functionality that can test multiple target types including web pages, browser extensions, and hybrid applications. The same core testing engine and recording mechanism adapts to different testing targets, providing reliable and effective testing across diverse platforms without requiring separate specialized tools.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Productivity

If manual test scenario creation is required, then testing can be performed, but it requires significant time and effort

Engineering Contradiction:

Improvespeed of test scenario creationVSAvoidtime to create and execute tests

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary action by automatically generating test scenario code during the recording phase. Instead of requiring users to write tests beforehand, the framework captures user interactions and pre-generates the corresponding test code, significantly reducing the time required for test scenario creation and enabling rapid deployment of automated tests.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS12222846B2Methods and systems for automated testing using browser extension

Publication Date: 2025.02.11 CAPITAL ONE SERVICES LLC

AI summary

According to certain aspects of the disclosure, non-transitory computer readable media, systems and methods are disclosed for creating and executing test scenarios for automated testing of web pages. A computer system, for example, may perform operations including: recording one or more actions performed by a user on a web page, the one or more actions resulting in a web page element being displayed in the web browser application, recording an identifier of the web page element, in response to detecting a user input indicating a selection of the web page element, and recording a characteristic of the web page element; and generating, by the testing extension, a test scenario specifying a testable outcome resulting from the one or more actions, the testable outcome being an occurrence of an element having the identifier and the characteristic.