Backend Webpage Copies for Non-Intrusive Automated Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing browser-based tools for webpage testing are limited in functionality and cannot perform automated background testing without interfering with the developer's workflow, particularly in areas like accessibility testing.
Innovation Solution
A software development and testing platform (SDTP) with a browser extension that performs automated background testing on backend copies of webpages, parallel to the developer's frontend testing, using a proxy map to redirect asset requests to a background testing database, and compiles results for the developer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If automated background testing is performed on webpages, then testing completeness and reliability are improved, but system complexity and resource consumption increase
Solution Approach 1:
The system divides testing into two independent segments: foreground testing performed by the developer in the browser, and background testing performed automatically on backend copies of webpages. Each segment operates independently with its own test scripts and results, allowing comprehensive testing without requiring the developer to manage complex automated testing infrastructure.
Solution Approach 2:
The system creates backend copies of webpages that replicate the structure and content of the original pages. These copies are used exclusively for automated background testing, allowing thorough testing of accessibility and other features without interfering with the developer's workflow or requiring modifications to the original webpage code.
2Extent of automation
If automated testing scripts are executed on webpages, then testing automation is improved, but interference with developer workflow occurs
Solution Approach 1:
The system extracts automated testing operations from the developer's browser environment and relocates them to a separate background testing server. Test scripts are executed remotely on backend copies of webpages, completely isolating automated testing activities from the developer's foreground workflow while maintaining full automation capabilities.
Solution Approach 2:
The system introduces backend copies of webpages as an intermediary layer between the developer's browser and the automated testing scripts. The testing scripts interact with these copies rather than the original pages, allowing full automation without any interference with the developer's workflow or the actual webpage being developed.
3Ease of operation
If browser extension tools are used for webpage inspection, then ease of use is improved, but functionality limitations occur
Solution Approach 1:
The system merges the simplicity of browser extension tools with the powerful functionality of server-based testing. The browser extension provides easy initialization and configuration for developers, while the background testing server executes comprehensive automated test scripts that would be too complex to run from the browser alone, combining both ease of use and extensive functionality.
Solution Approach 2:
The background testing server provides universal testing capabilities that can be applied to any webpage type and any testing requirement. The system supports multiple test scripts for different testing scenarios (accessibility, functionality, performance), making the solution versatile while maintaining the simple browser extension interface for developers.
Data Source
AI summary
A software development and testing platform (SDTP) includes a browser extension, allowing a developer to run manual or automatic tests on a website. At the same time, a feature of the extension allows for performing automatic background tests, as the developer test workflow generates various webpages of the website. The SDTP captures the webpages, generates copies of the webpages in a backend server and runs background tests on the copies. The background tests, running on webpage copies do not interfere with the developer test workflow in the frontend.