Flash Testing Framework Using External Proxy Objects
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional testing frameworks for multimedia applications, such as Macromedia Flash, are inadequate as they rely on manual testing, are error-prone, time-consuming, and lack the capability to generate native user interface events, access graphical output, and perform true end-to-end testing, limiting their effectiveness in ensuring the correctness, reliability, and performance of complex Flash applications.
Innovation Solution
An automated testing framework that uses an external application programming interface (API) to communicate with the Flash application, allowing test scripts to be executed externally and leveraging proxy objects to represent symbolic values in the Flash memory space, enabling the generation of native user input events, capturing graphical output, and executing arbitrary code within the Flash player, thereby overcoming the limitations of existing ActionScript-based tests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual testing is used for Flash applications, then testing can be performed with simple tools, but the testing process becomes time-consuming and error-prone
Solution Approach 1:
The testing framework enables automated self-testing of Flash applications through externally executed test scripts that automatically generate UI events, capture output, and verify functionality without requiring manual human intervention for each test case
Solution Approach 2:
The patent replaces manual mechanical testing processes with an automated electronic testing system that uses external APIs and command interpreters to execute test scripts, generate events, and capture output programmatically
2Adaptability or versatility
If ActionScript-based test frameworks are used, then testing can be performed within the Flash environment, but the frameworks cannot generate native UI events or access graphical output
Solution Approach 1:
The patent introduces an intermediary command interpreter that bridges the external test script environment and the Flash player internal environment, enabling translation of external commands into native Flash events and providing access to graphical output and UI events that were previously inaccessible
Solution Approach 2:
The testing framework moves from a single-dimension internal ActionScript testing environment to a multi-dimensional architecture that combines external test script execution with internal Flash player operations, enabling simultaneous access to both native OS UI events and Flash graphical output
3Adaptability or versatility
If externally executed test scripts are used, then comprehensive testing capabilities are achieved, but the system complexity increases
Solution Approach 1:
The command interpreter serves multiple functions: it translates external commands to internal Flash events, executes test scripts, captures graphical output, and manages communication between the external testing framework and the Flash player, consolidating diverse testing capabilities into a single universal component
Data Source
AI summary
A computer-based automated testing framework tests a multimedia application (such as a Flash application running in a player module) that includes one or more Flash objects by executing test scripts in an external Java-based test module that uses proxy objects in the test module to represent the Flash objects in the player module. Correspondence between the proxy object and Flash objects is maintained by translating the first test script into a command, sending the command from the external test module to the player module, interpreting the command by accessing a lookup table at the player module, and then returning a value to the external test module in response to the command.