Dynamic Test Catalog Generation for Software Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software testing methods for component-based applications distributed across multiple systems are inefficient, as they fail to automatically adapt to the dynamic capabilities of the system landscape, leading to incomplete or irrelevant testing.

Innovation Solution

A system and method for aspect and landscape capability-driven automatic testing, which involves creating a master test catalog by comparing sub-test catalogs to the aspects and capabilities of the software application and system landscape, ensuring only relevant tests are executed based on available system capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional software testing methods are used for component-based applications distributed across multiple systems, then testing can be performed with standard procedures, but the testing becomes inefficient and fails to adapt to dynamic system landscape capabilities

Engineering Contradiction:
Improvetesting efficiencyVSAvoidadaptability to system landscape capabilities
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The test catalog is made dynamic by automatically adapting its structure and content based on the detected system landscape capabilities. The testing system dynamically generates test catalogs that include only relevant test cases matching the actual capabilities present in the target system landscape, rather than using static pre-defined test suites.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The testing system performs self-service by automatically detecting system landscape capabilities and generating appropriate test catalogs without manual intervention. The system autonomously compares available capabilities against required capabilities and selects relevant sub-test catalogs, eliminating the need for manual test suite configuration.

Inventive Principle:
Principle #25Self-service

2Reliability

If all sub-test catalogs are executed regardless of system capabilities, then comprehensive testing coverage is achieved, but irrelevant tests are performed wasting time and resources

Engineering Contradiction:
Improvetesting completenessVSAvoidtesting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system extracts and selects only the relevant sub-test catalogs from the complete test suite by comparing required capabilities against available system capabilities. This extraction process removes irrelevant tests from execution, keeping only those tests that correspond to actually present system capabilities.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The testing approach changes parameters by dynamically adjusting the test catalog composition based on capability matching. The system modifies which tests are included in the final execution set by evaluating capability parameters, transforming a fixed test suite into a variable, capability-dependent test selection.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If manual test catalog creation is performed to ensure relevance to system capabilities, then testing relevance is improved, but the complexity and effort of test preparation increases significantly

Engineering Contradiction:
Improvetest catalog creation easeVSAvoidcapability matching accuracy
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The system performs self-service by automatically detecting system landscape capabilities and generating appropriate test catalogs without manual intervention. The system autonomously compares available capabilities against required capabilities and selects relevant sub-test catalogs, eliminating the need for manual test suite configuration.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses feedback from capability detection and matching results to automatically adjust the test catalog composition. The capability comparison process provides feedback that drives the selection of relevant sub-test catalogs, ensuring accurate capability matching without manual effort.

Inventive Principle:
Principle #23Feedback

4Productivity

If the test catalog is dynamically adapted to system landscape capabilities, then testing efficiency is improved, but the complexity of the testing system increases

Engineering Contradiction:
Improvetesting efficiencyVSAvoidtesting system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The testing system is segmented into distinct functional modules: capability detection module, capability comparison module, and test catalog generation module. This segmentation allows the complex dynamic adaptation process to be broken down into manageable, independent components that can be developed and maintained separately.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The testing system achieves universality by designing a multi-functional platform that can handle capability detection, comparison, and test catalog generation in a unified manner. The system is built to work with different system landscapes and capability types through standardized interfaces, reducing overall system complexity despite the dynamic adaptation capabilities.

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

Data Source

PatentUS8930908B2Aspect and system landscape capability-driven automatic testing of software applications
Publication Date: 2015.01.06 SAP SE
  • US8930908B2 patent drawing
  • US8930908B2 patent drawing
  • US8930908B2 patent drawing

AI summary

In a system and a method, a sub-test catalog is retrieved from a test catalog repository. A test aspect of the sub-test catalog is compared to an aspect of a software application to be tested. A required system capability of the sub-test catalog is compared to the capabilities of a system landscape based on a determination that the sub-test catalog test aspect matches the aspect of the software application to be tested. The system landscape includes at least one system. The sub-test catalog is added to a master test catalog based on a determination that the required system capability of the sub-test catalog matches the system landscape capabilities.