Integrated Software Testing System Using Reusable Test Scripts
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software testing methods are inefficient and costly due to duplicative testing across independent organizations, leading to inconsistent results and reduced confidence in software quality, primarily because of separate functional, automated regression, and performance test phases that do not communicate effectively, resulting in repetitive tasks and inadequate test coverage.
Innovation Solution
An integrated method that uses a common set of business requirements-based manual test scripts across functional, automated regression, and performance test phases, leveraging standard software testing tools to streamline testing processes, reduce duplication, and enhance coherence and efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If separate independent organizations perform functional, automated regression, and performance test phases independently, then each organization can specialize in its specific testing domain, but this results in high degree of duplicative testing, increased cost, and time consumption
Solution Approach 1:
The patent merges previously separate functional, automated regression, and performance test phases into a unified integrated testing process. A single testing organization executes all test types using a common framework and shared test artifacts, eliminating duplicative testing activities while maintaining domain expertise through standardized testing procedures across all phases.
Solution Approach 2:
The patent creates a universal testing framework that performs multiple testing functions (functional testing, automated regression testing, and performance testing) through a single integrated system. The framework uses common test scripts, shared test data, and unified test management capabilities to execute diverse testing activities, making the testing organization multi-functional rather than requiring separate specialized groups.
2Adaptability or versatility
If separate organizations independently create requirements-based test conditions, test data, and manual test scripts for each test phase, then each phase can be tested with tailored approaches, but this creates high degree of duplicative work and inconsistency in test coverage
Solution Approach 1:
The patent performs preliminary action by creating comprehensive test conditions, test data, and test scripts during the functional test phase that serve as the foundation for subsequent automated regression and performance testing. These artifacts are established once and then reused across multiple test phases, eliminating the need to recreate them independently for each phase while maintaining phase-specific testing objectives.
Solution Approach 2:
The patent implements a nested structure where test artifacts created for functional testing (outer layer) contain and support the test artifacts for automated regression testing (middle layer), which in turn contain the test artifacts for performance testing (inner layer). Each phase's test conditions, data, and scripts are nested within the broader framework of the functional testing artifacts, allowing efficient reuse while maintaining phase-specific requirements.
3Extent of automation
If different test organizations select varying requirements and functions to test from the same business requirements, then each organization can focus on its specific testing expertise, but this leads to reduced consistency and coherence between test results across phases
Solution Approach 1:
The patent applies homogeneity by ensuring that the same set of business requirements, functions, and test conditions are used consistently across all test phases (functional, automated regression, and performance testing). A single unified selection of test targets is maintained throughout the integrated process, eliminating variations in what is being tested across different phases and organizations, thereby ensuring consistent and coherent test results.
4Adaptability or versatility
If manual test scripts are created for each test phase independently, then each phase can have customized test procedures, but this results in labor and time intensive repetitive tasks
Solution Approach 1:
The patent uses copying by creating master test scripts during functional testing that are then copied and adapted for automated regression testing and performance testing. Rather than writing separate test scripts for each phase, the framework copies the core test logic and procedures from the functional phase, automates them for regression testing, and scales them for performance testing, significantly reducing repetitive manual script creation while maintaining phase-specific customization needs.
Data Source
AI summary
The system and method presented provides a multi-phase, end-to-end integrated process for testing application software using a standard software testing tool. The system and method involve integrating the functional, automated regression and performance phases of software application testing by leveraging deliverables at each phase so that the deliverables may be efficiently reused in subsequent test phases. Deliverables such as functional and technical test conditions and manual test scripts are used as inputs for each phase of the integrated tests. The use of leveraged requirements-based deliverables between test phases significantly reduces much of the repetitive testing typically associated with functionality and performance testing and minimizes repetition of testing errors discovered in earlier test phases. This integrated system and method for validating the functionality and performance of software applications by leveraging deliverables provides enhanced efficiencies, test procedure consistency throughout multiple test phases, consistent test results and high quality software applications.