Android Cross-Application Testing via Nested Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing Android Instrumentation framework does not support cross-application testing, limiting the ability to monitor and control secondary applications invoked by primary applications during testing.

Innovation Solution

An Android automated cross-application testing device and method that includes a primary application testing unit, trigger monitoring unit, secondary application testing control unit, secondary application testing unit, and test result processing unit, utilizing the Test Runner Enhancement Framework Open Innovative Layout to enable cross-application testing by monitoring and controlling secondary applications within the same process as the primary application.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If the Instrumentation framework is used to test applications, then the primary application can be monitored and controlled accurately, but the framework cannot manipulate or monitor secondary applications invoked by the primary application

Engineering Contradiction:
Improvemonitoring capabilityVSAvoidcross-application testing capability
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The patent introduces an intermediary component (the testing framework enhancement layer) that sits between the primary application and secondary applications. This intermediary intercepts method calls from the primary application, identifies when secondary applications are invoked, and automatically initiates testing of those secondary applications. The intermediary translates cross-application interactions into monitorable events without requiring direct instrumentation of each secondary application, thus resolving the contradiction between maintaining precise monitoring of the primary application and enabling versatile cross-application testing.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a nested testing structure where the testing framework is embedded within the primary application's execution context. When the primary application invokes secondary applications, the testing framework nests its monitoring capabilities within the same process hierarchy, allowing it to observe and control secondary applications as if they were part of the primary application's internal state. This nesting approach enables the framework to maintain its monitoring precision while extending its versatility to cover cross-application scenarios.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Reliability

If the Instrumentation framework monitors applications in the same process, then it can manipulate and monitor the tested application, but it cannot do so for applications in different processes

Engineering Contradiction:
Improvemonitoring reliabilityVSAvoidcross-process testing capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent enhances the Instrumentation framework with multi-functional capabilities that allow it to operate effectively both within the same process and across different processes. The framework detects whether a secondary application resides in the same process or a different process, and automatically adapts its monitoring strategy accordingly. This universality enables the framework to maintain reliable monitoring for same-process applications while extending its capability to monitor cross-process applications through process-aware instrumentation and inter-process communication mechanisms.

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

Solution Approach 2:

The patent implements dynamic process detection and adaptation within the testing framework. The framework continuously monitors the process context of invoked applications and dynamically adjusts its monitoring approach based on whether the target application is in the same process or a different process. This dynamic behavior allows the framework to maintain reliable monitoring for same-process applications while seamlessly transitioning to cross-process monitoring strategies when needed, thus resolving the contradiction between monitoring reliability and cross-process versatility.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9396096B2Android automated cross-application testing device and method
Publication Date: 2016.07.19 NEW BORQS TECHNOLOGIES(BEIJING) CO LTD
  • US9396096B2 patent drawing
  • US9396096B2 patent drawing
  • US9396096B2 patent drawing

AI summary

The present disclosure provides an Android automated cross-application testing device and method. The device comprises a primary application testing unit, a trigger monitoring unit, a secondary application testing control unit, a secondary application testing unit, a secondary application test result recording unit, a library file storage unit, a primary application test checking unit, a test result processing unit, and a test result output unit. The method comprises monitoring the starting of a secondary application in the primary application testing process; testing the secondary application and collecting and processing the test result of the secondary application; and continuing the test of the primary application. If the test of the secondary application is successful, the above steps are repeated until the test of the primary application is completed. The method further comprises terminating the test of the primary application if the test of the secondary application times out or fails.