Remote Device Testing SDK for Cross-Platform Coverage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software developers face challenges in testing their applications across multiple devices and platforms without having to purchase and configure numerous hardware devices, especially for older versions and combinations of operating systems and browsers, which are difficult to acquire.
Innovation Solution
A remote development system (RDS) allows developers to connect to a network of devices in datacenters for testing, using a software development kit (SDK) to modify test scripts for remote execution without code changes, enabling cross-browser, cross-device, and cross-operating system testing.
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 physical devices through virtualization technology. Instead of acquiring multiple physical target devices, developers can access virtual instances that replicate the behavior and characteristics of various platforms, browsers, and device configurations. This allows comprehensive testing coverage while eliminating the need to physically possess and configure multiple devices.
Solution Approach 2:
The testing platform provides a universal environment that can simulate multiple different platforms, operating systems, and device types through software configuration. A single physical testing station can access and test against numerous virtual device profiles, making the system multi-functional without requiring multiple specialized hardware devices for each platform.
2Adaptability or versatility
If developers acquire multiple potential target devices for testing, then testing coverage is improved, but acquisition and configuration resources increase
Solution Approach 1:
Virtual device copies replace physical device acquisition. The system provides software-based replicas of various target devices that can be deployed and accessed without purchasing the actual hardware, thereby eliminating acquisition costs while maintaining testing coverage.
Solution Approach 2:
The patent replaces the mechanical/physical system of acquiring and configuring actual devices with a software-based virtualization system. Instead of physically obtaining and setting up multiple devices, developers interact with virtual representations through software interfaces, eliminating the need for physical acquisition and manual configuration resources.
3Reliability
If developers test on older versions and combinations of operating systems and browsers, then compatibility and reliability are improved, but device acquisition difficulty increases
Solution Approach 1:
The system pre-configures virtual device profiles representing various older versions and combinations of operating systems and browsers. These virtual environments are prepared in advance and made available through the testing platform, allowing developers to immediately access legacy configurations without the difficulty of sourcing physical devices with outdated software versions.
Solution Approach 2:
Virtual copies of devices running older operating system versions and browser combinations are created and maintained in the testing infrastructure. Developers can access these historical configurations through software without needing to physically acquire obsolete hardware, solving the acquisition difficulty while maintaining compatibility testing capability.
Data Source
AI summary
A remote software development infrastructure can include cross-continent datacenters with a variety of remote devices. The infrastructure can provide automated testing on the remote devices. A software development kit (SDK) can be used to integrate a test suite with the infrastructure. The SDK can modify the test suite to issue test commands to a remote test server of the infrastructure, as opposed to local test servers. A remote test server routes the test commands to a remote device in a datacenter. Both local testing and remote testing of a test script is possible. The SDK enables cross-browser, cross-device, cross-operating system and/or parallel testing of the test suite, without the user having to make code changes to the test suite. The test results and additional information are automatically captured and are aggregated in a dashboard in the form of aggregated reports and other graphical user interface elements.