Proxy Server Module Testing with Dynamic Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current module testing methods rely on static data, which is inadequate for modules dependent on time-sensitive factors, leading to unrealistic results and poor quality online platforms due to untested or improperly tested modules.

Innovation Solution

A system and method utilizing a proxy server to receive user requests, determine if a test is required, and call a mobile application programming interface (MAPI) to perform tests using dynamic or mock data, verify responses against predetermined responses, and implement modules based on verification results.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If static test data is used for module testing, then testing simplicity is improved, but testing realism deteriorates for time-sensitive modules

Engineering Contradiction:
Improvetesting simplicityVSAvoidtesting realism
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system dynamically selects between static and dynamic test data based on module characteristics. For time-sensitive modules, dynamic test data (real-time or mock) is automatically generated and applied, while for other modules static test data suffices. This dynamic adaptation resolves the contradiction by making the testing approach flexible rather than fixed.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the parameter of test data temporality from static to dynamic based on module requirements. By detecting whether a module is time-sensitive, the system automatically adjusts the test data characteristic, transforming the testing approach to match the module's needs and achieving both simplicity and realism.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If all modules are tested before implementation, then module quality is improved, but implementation speed deteriorates

Engineering Contradiction:
Improvemodule qualityVSAvoidimplementation speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system applies partial testing by selectively testing only those modules that require it based on their characteristics. Not all modules undergo the same testing process - the system identifies which modules need testing and which can be implemented directly, applying testing action only where necessary to maintain quality while improving implementation speed.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system performs preliminary analysis of module characteristics before implementation to determine testing requirements. By pre-identifying which modules are time-sensitive and require dynamic testing, the system prepares the testing strategy in advance, avoiding unnecessary testing delays for modules that don't require it.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If dynamic test data is used for time-sensitive modules, then testing realism is improved, but system complexity increases

Engineering Contradiction:
Improvetesting realismVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system introduces a proxy server as an intermediary that handles the complexity of dynamic test data generation and management. The proxy server acts as a mediator between the testing system and the modules, automatically generating mock or real-time data as needed, thereby isolating the complexity from the core module testing process and making the overall system more manageable.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If module testing is automated, then productivity is improved, but measurement precision deteriorates

Engineering Contradiction:
Improveautomation efficiencyVSAvoidverification accuracy
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The system incorporates feedback mechanisms where verification results from automated testing are used to refine and improve future testing processes. The system compares actual module responses against expected outcomes, learns from discrepancies, and adjusts testing parameters accordingly, thereby maintaining measurement precision while preserving automation efficiency.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11397666B2Computerized systems and methods for generating and modifying data for module implementation
Publication Date: 2022.07.26 COUPANG CORP
  • US11397666B2 patent drawing
  • US11397666B2 patent drawing
  • US11397666B2 patent drawing

AI summary

The present disclosure may be directed to a system for generating and modifying data for modules. The system may include receiving, from a user via a proxy server, a request and user information associated with the user; based on the determination that the request comprises a test, calling a mobile application programming interface. The mobile application programming interface may be configured to perform steps including retrieving data; performing the test on the module using the retrieved data; performing a verification on responses from the test to predetermined responses; and sending results of the performed verification to the user. The system may include implementing the module based on the performed verification.