Test Scenario Template Generation from Multi-Organization Runs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The labor-intensive and inefficient process of testing and validating complex software systems, where each organization must develop its own testing suite due to customization and proprietary data concerns, limits the effectiveness and efficiency of software validation across different organizations.
Innovation Solution
A system and method for generating and suggesting test scenario templates based on data from multiple organizations, clustering similar test runs, and removing proprietary data, enabling organizations to leverage collective testing knowledge and streamline their testing processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If each organization develops its own testing suite, then testing effectiveness for organization-specific systems is improved, but testing effort and time increase significantly
Solution Approach 1:
Test scenario templates are prepared in advance by analyzing and generalizing test scenarios from multiple organizations. These pre-prepared templates capture common testing patterns and procedures, allowing organizations to quickly instantiate customized test scenarios without starting from scratch, thus reducing testing effort while maintaining effectiveness
Solution Approach 2:
The system allows organizations to customize test scenario templates by modifying parameters such as organization-specific module selections, customization configurations, and test data. This parameter-based customization enables efficient adaptation of generic templates to specific organizational needs, balancing reusability with effectiveness
2Productivity
If test scenarios are shared across organizations, then testing efficiency is improved, but proprietary data security risks increase
Solution Approach 1:
The system extracts and removes proprietary data elements from test scenarios before sharing them across organizations. Test scenario templates contain parameterized placeholders instead of actual organization-specific data, allowing efficient sharing while eliminating security risks associated with proprietary information exposure
Solution Approach 2:
Instead of sharing original test scenarios containing proprietary data, the system creates anonymized copies in the form of parameterized templates. These templates replicate the structure and logic of effective test scenarios while removing organization-specific identifiers and sensitive information, enabling safe knowledge transfer
3Reliability
If test scenarios are customized for each organization, then testing relevance is improved, but device complexity and maintenance burden increase
Solution Approach 1:
The testing system is segmented into modular components: generic test scenario templates, organization-specific parameter configurations, and customization modules. This segmentation allows organizations to maintain only the necessary customized parameters while relying on the shared template framework, reducing overall system complexity and maintenance burden
Solution Approach 2:
Test scenario templates are designed to be universal and multi-functional, capable of serving multiple organizations across different industries. The templates incorporate parameterized configurations that can adapt to various software systems and organizational requirements, reducing the need for organization-specific test development while maintaining relevance
Data Source
AI summary
System, method, and non-transitory computer-readable medium for generating a test scenario template from runs of test scenarios run on software systems belonging to different organizations, including: clustering the runs to clusters comprising similar runs of test scenarios; selecting from the clusters a certain cluster comprising a first run of a first test scenario and a second run of a second test scenario belonging to different organizations. At least 95% of values used in the first run of the first test scenario are provided automatically by a test script. And generating a test scenario template representing the certain cluster, wherein the test scenario template identifies a transaction used in the first and second runs, and possible values for running the transaction.


