Test Scenario Templates Based on Setup Similarity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current testing approaches for complex software systems, such as ERP systems, are labor-intensive and costly due to the need for each organization to develop its own testing suite, and the inability to share proprietary data, hindering the utilization of the 'wisdom of the crowd' for effective and efficient testing.
Innovation Solution
A method and system for generating and suggesting test scenario templates based on data from similar organizations, using a computer system that identifies similar setups and removes proprietary data, allowing organizations to leverage testing knowledge from other organizations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If each organization develops its own testing suite, then testing can be customized for specific organizational needs, but testing becomes labor-intensive and costly
Solution Approach 1:
Test scenario templates are pre-developed and validated by multiple organizations before being made available for reuse. This preliminary action allows organizations to benefit from pre-done testing work, reducing their own testing effort while maintaining customization through selective template choice and parameter adjustment.
Solution Approach 2:
Organizations can copy and reuse test scenario templates from other organizations with similar setup files. The copying mechanism allows transfer of validated testing knowledge without redeveloping tests from scratch, significantly improving productivity while maintaining adaptability through template selection based on organizational similarity.
2Productivity
If organizations share testing data, then the wisdom of the crowd can be leveraged for better testing, but proprietary data may be leaked to unauthorized parties
Solution Approach 1:
The system extracts and removes proprietary data elements from test scenarios before making them available for sharing. By separating the valuable testing logic from sensitive organizational data, the system enables knowledge sharing while protecting proprietary information, allowing organizations to benefit from crowd wisdom without data leakage risks.
Solution Approach 2:
A centralized platform acts as an intermediary that mediates the sharing of test scenarios between organizations. This intermediary automatically processes test scenarios to remove proprietary data, manages access controls, and enables secure sharing, thus facilitating productivity improvement while eliminating data security concerns through automated protection mechanisms.
3Measurement precision
If test scenarios are customized for different organizations, then testing accuracy is improved, but the ability to reuse tests across organizations is reduced
Solution Approach 1:
Test scenario templates are designed with local quality by allowing organizations to customize only the specific portions relevant to their setup files while keeping the core testing logic standardized. This approach maintains high reusability for the standardized parts while allowing localized customization where organizational specificity is needed, balancing accuracy and reusability.
Solution Approach 2:
The system enables parameter changes in test scenarios based on organizational setup files. By allowing dynamic parameter adjustment while maintaining the overall test structure, the system achieves both customization for accuracy and reusability through parameterized templates that can adapt to different organizations without requiring complete test redevelopment.
4Reliability
If extensive testing is performed to validate software systems, then system reliability is improved, but testing cost and time increase
Solution Approach 1:
Test scenarios are pre-validated by multiple organizations before reuse, so that when an organization applies a template, the validation work has already been performed. This preliminary action by the crowd eliminates the need for each organization to perform extensive validation from scratch, maintaining reliability while significantly reducing testing time and cost.
Solution Approach 2:
Validated test scenarios are copied and reused across organizations, eliminating redundant validation efforts. By copying proven test scenarios rather than creating new ones, organizations achieve the same reliability validation without repeating the time-consuming validation process, thus reducing testing duration while maintaining software reliability.
Data Source
AI summary
Systems, methods, and non-transitory medium for generating a test scenario template based on similarity between descriptions associated with different organizations. A monitoring module is used to monitor users and to identify runs of test scenarios run on software systems belonging to the different organizations. A processor receives a description of a certain organization (e.g., setup files) and descriptions of the different organizations and identifies, based on similarity between the certain description and the descriptions, organizations that are similar to the certain organization. The processor also identifies a run of a specific test scenario that is utilized by one or more of the organizations. A template generator is used to generate the test scenario template based on the run of the specific test scenario. Additionally, a data cleaner is used to remove from the test scenario template proprietary data associated with at least one of the different organizations.