Internationalization Automation Framework Using Lookup Database
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Prior art automation frameworks for internationalization compliant applications face reduced maintainability and scalability due to hard-coded business logic that statically links message identifiers to message strings, requiring frequent modifications and resulting in high operational overhead when message identifiers and strings change.
Innovation Solution
An automation framework that uses a synchronization engine to manage reference identifiers stored in a lookup database, allowing message identifiers and strings to be updated independently of the test script, enabling efficient testing of changing message data without modifying business logic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If message identifiers and strings are hard-coded in test scripts, then the automation framework can execute tests, but maintainability and scalability deteriorate when message data changes
Solution Approach 1:
The patent segments the automation framework into distinct components: test scripts that reference only message identifiers, a message catalog that stores message strings, and a synchronization engine that manages the mapping between identifiers and strings. This segmentation allows message data to be modified independently of test execution logic, resolving the contradiction between maintaining test reliability and adapting to message changes.
Solution Approach 2:
The patent extracts message strings from test scripts and places them in a separate message catalog. Test scripts now only contain message identifiers as references, while the actual message strings are stored externally in the catalog. This extraction enables message data to be updated without modifying test scripts, improving adaptability while preserving test execution reliability.
2Device complexity
If message identifiers are statically linked to message strings in test scripts, then the framework structure is simple, but operational overhead increases when updates are needed
Solution Approach 1:
The patent implements a synchronization engine that performs preliminary actions by automatically updating test scripts with new message identifiers from the message catalog before test execution. This preliminary synchronization eliminates the need for manual script modifications when message data changes, reducing operational overhead and update time while maintaining a simple framework structure.
3Ease of manufacture
If the automation framework uses hard-coded business logic, then implementation is straightforward, but scalability is reduced when new message data is added
Solution Approach 1:
The patent creates a universal message catalog that can store any message string and serves all test scripts through reference to message identifiers. The synchronization engine provides multi-functional capabilities by automatically managing the mapping between identifiers and strings across the entire framework. This universal approach allows new message data to be added to the catalog without modifying existing test scripts, enhancing scalability while keeping implementation straightforward.
Data Source
AI summary
An automation framework for internationalization compliant applications is described. The automation framework includes a computer that executes a parser, an execution engine, and a logger. The parser parses a test case from a test case suite to identify script instructions to test an internationalization compliant application. The script instructions include a reference identifier. The execution engine executes the script instructions to test the internationalization compliant application, to identify at least one message identifier and at least one message string based on referencing a lookup database for an automation framework using the reference identifier, and to validate at least one message identifier and at least one message string with the internationalization compliant application. The logger logs a result of executing the script instructions, and outputs the result via an output device.