Dynamic Functional Testing Tool Using Metadata Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software testing tools are unable to automate the test writing process due to a lack of business knowledge and software architecture knowledge.
Innovation Solution
A modular and user-configurable approach is provided for creating functional tests for software applications, using a metadata configuration file that specifies testing instructions and execution paths, and dynamically accessing pages of the application to test functionalities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If existing software testing tools are used, then testing functionality is available, but automation of test writing process cannot be achieved due to lack of business knowledge and software architecture knowledge
Solution Approach 1:
The system performs preliminary action by pre-defining test components, execution paths, and test data in a metadata configuration file before actual test execution. This allows the testing tool to automatically generate test scripts without requiring real-time business knowledge or software architecture understanding, thus achieving automation while compensating for the tool's lack of domain knowledge.
Solution Approach 2:
The metadata configuration file acts as an intermediary between the developer's domain knowledge and the automated testing tool. The developer defines test requirements, execution paths, and component relationships in the metadata file, which then serves as a bridge that translates business logic into automated test scripts, enabling the tool to execute tests without directly understanding the business domain.
2Productivity
If manual test writing is performed, then business knowledge and software architecture knowledge can be applied, but automation and efficiency are lost
Solution Approach 1:
The system uses copying by creating reusable test components that can be defined once in the metadata configuration and automatically instantiated multiple times across different test scenarios. This allows efficient test generation through template-based automation, where predefined test patterns are copied and adapted to specific test cases, significantly improving productivity while maintaining automation.
Solution Approach 2:
The system applies parameter changes by allowing the metadata configuration file to define variable parameters such as test data values, execution paths, and component selections. The automated testing tool dynamically adjusts these parameters to generate specific test instances, enabling high-level automation while maintaining flexibility and efficiency through parameterized test generation.
3Extent of automation
If a modular and user-configurable approach with metadata configuration file is used, then automation of test writing is enabled, but device complexity increases
Solution Approach 1:
The system applies segmentation by dividing the test configuration into distinct, manageable components within the metadata file: test components, execution paths, test data, and expected results. This modular structure allows developers to configure tests systematically without overwhelming complexity, as each segment can be independently defined and validated, thereby enabling automation while managing complexity through structured organization.
Data Source
AI summary
A computer-implemented method is provided for producing a test for a software application that is generated based on metadata. The method includes providing to the user a library of predefined test logic for testing multiple software components. Each software component is a reusable element comprising application logic, visual styling and user interface. The method also includes guiding the user to define (i) at least one execution path that specifies an order for testing one or more pages of the software application, and (ii) test instructions for one or more components on each of the one or more pages. The method further includes retrieving, from the library, predefined test logic for the one or more components if they are present in the library based on the test instructions supplied by the user, and automatically configuring a test file incorporating the predefined test logic in an order specified by the execution path.