Integration Testing Adapter for Unstructured Databases

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing integration testing tools are incompatible with unstructured databases, making it difficult to test software applications that interact with them, leading to uncertainty about the applications' performance in production settings.

Innovation Solution

An integration testing adapter (ITA) is developed to connect integration testing tools with unstructured databases, enabling data retrieval and operations by parsing configuration files, using unstructured database drivers, and executing transactions, thus facilitating testing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If integration testing tools are used with structured databases, then testing can be performed effectively, but they are incompatible with unstructured databases

Engineering Contradiction:
Improvetesting effectivenessVSAvoiddatabase compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces an adapter as an intermediary component that connects the integration testing tool to the unstructured database. The adapter translates database-specific operations into a standardized interface that the testing tool can understand, enabling compatibility without modifying either the testing tool or the database. This resolves the contradiction by allowing the testing tool to work with unstructured databases through the mediating adapter layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The adapter dynamically changes parameters and operation modes based on the target database type. It detects whether the database is structured or unstructured and adjusts its translation logic accordingly, allowing the same testing tool to adapt to different database types by changing its operational parameters through the adapter.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If standard integration testing tools are used, then testing process is simple, but they cannot execute queries on unstructured databases

Engineering Contradiction:
Improvetesting process simplicityVSAvoiddata retrieval capability
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The adapter serves as a mediator that handles the complexity of database-specific query execution. The testing tool maintains its simple interface while the adapter translates standard testing operations into database-specific queries, enabling data retrieval from unstructured databases without complicating the testing tool's operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If integration testing is performed without adapter, then device complexity is reduced, but uncertainty exists about application performance

Engineering Contradiction:
Improvesystem architecture complexityVSAvoidapplication performance validation
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The adapter introduces minimal complexity by providing a standardized translation layer. It enables reliable performance validation by ensuring that testing operations are correctly translated and executed on unstructured databases, giving confidence that applications will operate correctly in production settings with unstructured databases.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10459833B2Software integration testing with unstructured database
Publication Date: 2019.10.29 ACCENTURE GLOBAL SOLUTIONS LTD
  • US10459833B2 patent drawing
  • US10459833B2 patent drawing
  • US10459833B2 patent drawing

AI summary

According to examples, software integration testing with an unstructured database may include retrieving a configuration file stored in memory, and parsing the configuration file to identify configuration details of an unstructured database. A connection may be established between an integration testing tool and the unstructured database based on the configuration details. Software integration testing with an unstructured database may further include identifying a transaction file specifying a database operation to be performed by the unstructured database to retrieve data stored in the unstructured database responsive to the application performing a function. A query may be generated based on the database operation. The query may be sent, via an interface, to the unstructured database for execution. Results of the query may be received via the interface. The query results may be compared to validation data to determine whether the function operates in a determined manner.