Wireless Component Test Harness Using Modular Event Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developing software applications for wireless devices is challenging due to disparities in hardware and software across different platforms, leading to inefficient and costly manual testing, with current automated testing methods being inadequate for ensuring comprehensive functionality across various devices.

Innovation Solution

A test harness system that uses testlets and event handlers to validate target application log events, allowing for rigorous automated functionality testing of wireless component applications, reducing developer effort and resource usage while being modular and adaptable.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual testing is used to test wireless component applications across multiple platforms, then testing comprehensiveness can be improved, but testing efficiency and cost increase significantly

Engineering Contradiction:
Improvetesting comprehensivenessVSAvoidtesting efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The testing system performs self-validation through automated testlets that execute test cases and automatically compare results against expected outcomes, eliminating the need for manual intervention in each test iteration while maintaining comprehensive coverage across multiple wireless platforms

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system changes testing parameters dynamically by configuring testlets with different test cases, expected results, and validation criteria to adapt to various wireless device platforms and application types, enabling comprehensive automated testing without manual reconfiguration

Inventive Principle:
Principle #35Parameter changes

2Productivity

If automated testing is implemented for wireless component applications, then testing efficiency improves, but testing comprehensiveness and adaptability to platform differences decrease

Engineering Contradiction:
Improvetesting efficiencyVSAvoidtesting comprehensiveness
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The testing system achieves universality by designing testlets that can operate across multiple wireless device platforms and application types through a common architecture, allowing automated testing to maintain comprehensiveness while improving efficiency

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

Solution Approach 2:

The system segments testing into modular testlets that can be independently configured and executed, each handling specific test cases and validation rules, enabling comprehensive automated testing across platform differences through composed test suites

Inventive Principle:
Principle #1Segmentation

3Reliability

If platform-specific native applications are developed for each wireless device, then application performance and optimization improve, but development complexity and resource requirements increase

Engineering Contradiction:
Improveapplication performanceVSAvoiddevelopment complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the application into portable components that can be independently developed and tested, allowing platform-specific optimization without requiring complete platform-specific development, thereby reducing development complexity while maintaining performance

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8001529B2System and method of testing wireless component applications
Publication Date: 2011.08.16 MALIKIE INNOVATIONS LTD
  • US8001529B2 patent drawing
  • US8001529B2 patent drawing
  • US8001529B2 patent drawing

AI summary

A test harness system and method of functionality testing of wireless component applications is provided. The test harness system comprises at least one testlet for testing at least one target application log event and at least one event handler for validating at least one comparator against the at least one target application log event. The method comprises the steps of listening for target application log events, receiving a target application log event, receiving a testlet and validating the target application log event based upon the testlet.