Dynamic Bridge for Proprietary Test Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software-testing frameworks, such as JUnit, face challenges in supporting proprietary tests that do not conform to Integrated Development Environments (IDEs) or tools, requiring significant effort to develop multiple connections and GUIs, making it costly and inefficient to integrate tests with various development environments.

Innovation Solution

A dynamic-bridge connects a collection of tests to a testing-framework, providing a dynamic test wrapper that presents tests as compatible with the framework, allowing them to be executed and reported within the framework, thereby enabling support from IDEs and tools without requiring extensive additional connections.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple separate connections and GUIs are developed for each IDE and tool, then proprietary tests can be supported by specific environments, but the effort and cost of integration increases significantly

Engineering Contradiction:
Improvecompatibility with IDEs and toolsVSAvoidintegration effort and cost
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal test execution framework that can execute proprietary tests across multiple IDEs and tools through a single integration point. The system provides a standardized interface that works with JUnit, TestNG, and other testing frameworks simultaneously, eliminating the need to develop separate connections for each environment while maintaining broad compatibility

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

Solution Approach 2:

The patent introduces an intermediary component that acts as a bridge between proprietary tests and various IDEs/tools. This mediator translates and adapts test execution requests into a unified format that can be processed by different testing frameworks, reducing integration complexity while maintaining versatility across multiple development environments

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If proprietary tests are integrated with testing frameworks, then test execution and reporting can be automated, but the effort to develop multiple connections increases

Engineering Contradiction:
Improvetest execution automationVSAvoidintegration development time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-configuring a universal execution framework that is ready to handle multiple testing frameworks out of the box. The system includes pre-built adapters and translation layers that are prepared in advance, allowing proprietary tests to be executed automatically across different IDEs and tools without requiring time-consuming custom integration work for each environment

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system provides a single multi-functional integration solution that enables automated test execution and reporting across multiple IDEs and tools simultaneously. This universal approach consolidates what would otherwise require multiple separate integration efforts, significantly reducing the time and effort needed to achieve automation while maintaining productivity

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

Data Source

PatentUS9075920B1Integrating software-tests with software development environments or tools that can assist software-testing
Publication Date: 2015.07.07 SUN MICROSYSTEMS INC
  • US9075920B1 patent drawing
  • US9075920B1 patent drawing
  • US9075920B1 patent drawing

AI summary

A dynamic-bridge connects a collection of tests (e.g., proprietary tests) to a testing-framework and effectively allows the collection of tests to interface with the testing-framework, thereby allowing the development environment and tools that support the testing-framework to also support the collection of tests. The dynamic-bridge provides a dynamic test wrapper which can be dynamically constructed for a test and present it as a test which conforms to or is compatible with the testing-framework and executed within the testing-framework. Test results are reported in a form that is expected or acceptable by the framework. In effect, the dynamic test wrapper simulates executing the test in the testing framework. As a result, tools which have been integrated with the testing-framework can be used to support tests which may originally not conform or be compatible with the testing-framework.