Remote Device Browser Testing with Local Host Traffic Injection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software developers face challenges in testing their products across multiple platforms and devices without having to invest in hardware and configuration, especially with varying generations and iterations of devices like iOS and Android, complicating the development process.
Innovation Solution
A remote software development infrastructure that allows developers to test their software on a variety of devices and platforms using remote devices located in datacenters, with a local machine interface that mirrors and interacts with the remote device's display and browser, enabling seamless interaction and testing without parallel processes or mirrored data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If developers acquire and configure multiple potential target devices for testing, then testing coverage across multiple platforms is improved, but resource strain and device complexity increase
Solution Approach 1:
The patent creates virtual copies of target devices through containerized environments that replicate the hardware and software characteristics of physical devices. Developers can test on these virtual device copies without acquiring actual hardware, thereby maintaining testing coverage while eliminating resource strain from managing multiple physical devices.
Solution Approach 2:
The patent implements a universal testing platform that can simulate multiple different device types, operating systems, and configurations within a single infrastructure. This multi-functional system allows one platform to serve the role of many different target devices, improving adaptability while reducing the need for multiple specialized devices.
2Reliability
If developers configure multiple target devices for comprehensive testing, then product compatibility is improved, but time and configuration effort increase
Solution Approach 1:
The patent pre-configures containerized testing environments with various device specifications, operating systems, and software versions before testing begins. These ready-made virtual device images are stored and can be instantly deployed, eliminating the time-consuming configuration process that would otherwise be required for each target device.
Solution Approach 2:
The testing platform automatically manages the provisioning, configuration, and teardown of virtual device environments based on test requirements. The system self-services by selecting appropriate container images, allocating resources, and cleaning up after tests without requiring manual developer intervention for each device setup.
3Ease of manufacture
If developers use remote infrastructure for testing, then resource investment is reduced, but network latency and interaction delay increase
Solution Approach 1:
The patent implements a nested architecture where containerized virtual devices are embedded within a remote infrastructure platform, which itself is accessible from the developer's local environment. This nested structure allows the system to leverage remote resources while maintaining local interaction points, reducing the perceived latency by nesting the remote testing environments within an accessible interface layer.
Data Source
AI summary
A remote software development infrastructure can include multiple cross-continent datacenters with a variety of remote devices to choose from in the datacenters. A user can select a remote device and access the remote device via a local machine. The infrastructure can stream a video feed of the display of the remote device to the local machine. The user can run a browser on the remote device to test a website, including for example, testing accessing the website and its features via the browser running on the remote device. URL requests to the user's website are received from the local machine and injected into the browser running on the remote device. The browser running on the remote device issues the URL requests. Restricted URL requests can be modified via a browser extension and replaced with a non-restricted URL pointing to the same communication endpoint as the restricted URL.