Test Scenario Template Generation via Anonymized Data Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The process of testing software systems is time-consuming and expensive, especially when new modules are installed or updated, as organizations often develop their own testing suites due to proprietary data concerns and the lack of shared testing knowledge, leading to inefficiencies in leveraging testing data across different organizations.
Innovation Solution
A method and system for generating and suggesting test scenario templates based on crowd-sourced data from multiple organizations, allowing for the identification and selection of frequently performed test steps and the creation of customized templates that can be exported and imported, leveraging 'testing crowd wisdom' to streamline software validation processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If organizations share their testing data and knowledge, then testing efficiency and knowledge utilization are improved, but proprietary data security and risk of data leakage worsen
Solution Approach 1:
The patent extracts and removes proprietary data elements from test scenarios before sharing them across organizations. The system identifies and redacts sensitive information such as organization-specific identifiers, proprietary values, and confidential data, leaving only the structural test logic and methodology that can be safely shared while protecting organizational secrets.
Solution Approach 2:
The patent introduces an intermediary processing layer that acts as a mediator between organizations. This layer anonymizes and generalizes test data, transforming organization-specific test scenarios into universal templates that preserve testing logic while removing proprietary elements. The intermediary ensures secure knowledge sharing without direct exposure of sensitive data.
2Reliability
If each organization develops its own testing suite, then proprietary data security is maintained, but testing time and cost increase
Solution Approach 1:
The patent performs preliminary actions by pre-processing and anonymizing test scenarios before they are made available for sharing. Organizations can access and utilize pre-anonymized test templates without needing to develop everything from scratch, significantly reducing testing time while maintaining security through prior data protection.
Solution Approach 2:
The patent enables organizations to copy and adapt standardized, anonymized test templates rather than developing unique test suites. These templates can be replicated across multiple organizations with minimal customization, reducing redundant development effort while the anonymization process ensures proprietary data remains protected.
3Measurement precision
If test scenarios are customized for each organization, then testing accuracy and relevance are improved, but device complexity and processing requirements worsen
Solution Approach 1:
The patent applies local quality by allowing organizations to customize only the specific portions of test scenarios that are relevant to their needs, while retaining the standardized anonymized framework. This enables targeted customization of local elements (organization-specific parameters, particular test cases) without requiring complete reconfiguration of the entire testing system.
Solution Approach 2:
The patent segments test scenarios into modular components that can be independently selected and customized. Organizations can assemble test suites by combining standardized anonymized templates with organization-specific modifications, reducing overall system complexity through modular design while maintaining testing accuracy for critical organization-specific requirements.
Data Source
AI summary
System, method, and non-transitory medium for generating a test scenario template from runs of test scenarios that include a subset of test steps. Executing the method involves the steps of identifying runs of test scenarios run by users on software systems that belong to different organizations; identifying subsets of test steps that are frequently described in the runs; receiving a profile of a user and selecting, based on the profile, a certain subset, from among the subsets, which is appropriate for the user; selecting, from among the identified runs, a first run and a second run; the first and second runs include test steps that are essentially identical to the test steps in the certain subset; and generating a test scenario template based on the first and second subsets of test steps.