Abort Handler Completes Test Record Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Raw test data format is often not accepted by analysis programs and is difficult to comprehend, leading to data formatting operations being abruptly terminated and resulting in corrupted or lost test records, causing significant delays and repetitive work.
Innovation Solution
A system comprising data formatters and an abort handler that retrieves test data from a store, generates test records, and completes record generation upon receiving abort events, ensuring partial records can be completed based on available data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data formatting operations are performed on raw test data, then the test records become more usable and comprehensible, but the operations may be abruptly terminated by abort events causing corruption or loss of test records
Solution Approach 1:
The patent applies preliminary action by creating and maintaining checkpoint records during the data formatting process. Before an abort event can corrupt in-progress test records, the system has already saved intermediate formatting states as checkpoint records. This allows recovery without losing the work done up to each checkpoint, effectively preventing the corruption problem before it occurs.
Solution Approach 2:
The patent implements beforehand cushioning by establishing a recovery mechanism that cushions against the harmful effects of abort events. The checkpoint record system acts as a protective buffer, ensuring that even if formatting operations are abruptly terminated, the partial records generated before the abort can be recovered and completed, preventing total loss of formatting work.
2Ease of operation
If data formatting operations are performed on raw test data, then the test records become more usable and comprehensible, but significant delays and repetitive work occur when abort events terminate operations
Solution Approach 1:
The system performs preliminary action by continuously saving checkpoint records during formatting operations. When an abort event occurs, these pre-saved checkpoints enable rapid recovery without requiring restart of the entire formatting process, thus preventing time loss while maintaining ease of operation through usable test records.
Solution Approach 2:
The patent ensures continuity of useful action by implementing a recovery mechanism that allows formatting operations to be resumed from checkpoint records after abort events. This maintains the continuous generation of usable test records without interruption, eliminating delays and repetitive work while preserving the usability benefits of formatted data.
3Loss of information
If partial test records are generated during in-progress formatting operations, then valuable test information is captured, but these partial records are corrupted or lost when abort events occur
Solution Approach 1:
The patent applies preliminary action by saving checkpoint records that capture the state of partial test records at intermediate stages. Before an abort event can corrupt these partial records, their current state has already been preserved in checkpoint records, ensuring test information is not lost even though the formatting operation was interrupted.
Solution Approach 2:
The patent uses copying by creating checkpoint records as copies of the formatting state at various stages. These checkpoint copies serve as backup versions that can be restored if the original in-progress records are corrupted by abort events, thereby preserving test information while maintaining record integrity through the copy mechanism.
Data Source
AI summary
A system for formatting test data includes at least one data formatter to retrieve test data from a data store, upon receiving notifications of test events, and to generate a number of test records based on the test data. The system further includes an abort handler to cause at least one of the data formatters to complete the generation of its number of test records based on currently available test data in the data store, in response to an abort event.