Self-contained Mobile App Testing via Cloud Packaging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current application testing is complicated for non-programmers, wasting developer resources and restricting testers and analysts due to the need for specific environments and equipment, limiting their ability to perform timely and objective testing and analysis.

Innovation Solution

A system and method for self-contained mobile application testing and integration, where a publishing agent on a developer's device compiles and sends an executable to a cloud-based code packager, generating a URL or QR code that allows testers and analysts to access and run the application on a mobile device within a self-contained processing environment, independent of the cloud, enabling testing and analysis anywhere and anytime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a developer packages applications together in designated processing environments for testers, then the testing can be performed, but it takes a substantial amount of time of the developers and taxes server resources

Engineering Contradiction:
Improvetesting capabilityVSAvoiddeveloper time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables testers to independently package and configure applications without requiring developer intervention. The automated packaging system creates self-contained test environments with all necessary dependencies, allowing testers to execute tests autonomously and reducing the time developers spend on packaging tasks.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system pre-configures and packages applications with all necessary dependencies, libraries, and settings before testing begins. This preliminary packaging action eliminates the need for testers to manually locate and reference software resources, accelerating the testing process while reducing developer time investment.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If a developer packages applications together in designated processing environments, then the code can be tested, but it taxes server resources associated with the test processing environment

Engineering Contradiction:
Improvetesting capabilityVSAvoidserver resources
Core Design Contradiction:
ReliabilityVSUse of energy by stationary object

Solution Approach 1:

The system extracts and packages only the essential components needed for testing into self-contained units. By separating test applications from the full development environment and packaging only necessary dependencies, the system reduces server resource consumption while maintaining testing capability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of packaging complete development environments with all possible resources, the system packages only the partial set of resources actually needed for testing. This selective packaging approach reduces server resource taxation while ensuring all necessary testing capabilities are included.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If testers need to access internal testing environment via desktop or laptop, then they can perform tests, but they cannot perform tests via mobile device and are restricted to specific locations

Engineering Contradiction:
Improvetesting capabilityVSAvoidtesting location flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system creates universal test packages that can execute on multiple device types including mobile devices, tablets, and desktops. The self-contained packaging includes all necessary dependencies and configurations, allowing the same test application to run consistently across different platforms and locations without requiring device-specific setup.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system transitions from a fixed, location-bound testing environment to a portable, location-independent testing model. By packaging applications as self-contained units that can execute on mobile devices, the system adds spatial flexibility and allows testing in various locations without sacrificing testing capability.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

4Productivity

If non-programming resources perform testing, then developer resources are not wasted, but they need to consult with the developer which distracts the developer away from current work

Engineering Contradiction:
Improvetesting capabilityVSAvoiddeveloper time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system enables non-programming testers to independently package, configure, and execute tests without requiring developer consultation or intervention. The automated packaging system provides all necessary technical details, dependencies, and configurations, allowing testers to work autonomously and eliminating the need for developer time investment in testing activities.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20240086307A1Self-contained mobile application processing and integration
Publication Date: 2024.03.14 CARET HOLDINGS INC
  • US20240086307A1 patent drawing
  • US20240086307A1 patent drawing
  • US20240086307A1 patent drawing

AI summary

A developer's application (app) is compiled and linked to a first processing environment associated with a cloud/server. Metadata is created to define the source code for the app, source code used with the app from the first processing environment, and settings for the app and the first processing environment. The metadata is stored on cloud/server location associated with a link. Optionally, the link is published to message threads/boards and/or a task of a workflow. A user of a mobile device provides the link/code within the context of a mobile app of the mobile device. The mobile app obtains the metadata using the link from the location and instantiates a container/shell that is provided the metadata. The container/shell configures as a self-contained instance of the developer's app within a second and self-contained processing environment and the self-contained instance is executed within a user interface window of the mobile app.