Test Executive Logging via Expression Evaluation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current test executive software lacks flexibility in logging configurations for test executive sequences, particularly in automatically logging data and parameters of user-supplied code modules, requiring users to implement programming for logging functionalities.

Innovation Solution

A system and method that allows users to configure expressions and parameters for logging through a graphical user interface, enabling automatic logging of result values and parameter values during the execution of test executive sequences without requiring programming, by interacting with the sequence editor to specify expressions and parameters to be logged, which are then evaluated and logged by the test executive engine.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users manually implement logging functionalities through programming, then logging capability is achieved, but device complexity and ease of operation deteriorate

Engineering Contradiction:
Improveease of configuring loggingVSAvoidcomplexity of logging implementation
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system automatically logs test results and parameter values without requiring user programming. The test executive engine autonomously captures execution results, evaluates expressions, and writes logs to the log file, allowing the system to serve itself rather than requiring manual intervention for logging functionalities

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The logging system is designed to handle multiple types of data (test results, parameter values, expressions) through a unified logging mechanism. The same log file and logging process can record diverse information types, eliminating the need for separate logging implementations for different data kinds

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Loss of information

If the system logs all test results and parameters automatically, then information completeness improves, but loss of time increases due to processing overhead

Engineering Contradiction:
Improvecompleteness of test data loggingVSAvoidtime for evaluating and logging expressions
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system allows selective logging where users can choose which expressions and parameter values to log. Rather than logging everything unconditionally, the system evaluates and logs only the specific items configured by the user, reducing unnecessary processing while maintaining completeness of relevant test data

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

Expressions are configured in advance before test execution. The system pre-defines which expressions should be evaluated and logged, allowing the logging mechanism to be prepared beforehand rather than dynamically determining what to log during execution, thus reducing processing time during actual testing

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7451358B2Test executive system with automatic expression logging and parameter logging
Publication Date: 2008.11.11 NATIONAL INSTRUMENTS CORP
  • US7451358B2 patent drawing
  • US7451358B2 patent drawing
  • US7451358B2 patent drawing

AI summary

A test executive sequence may be created by including a plurality of test executive steps in the test executive sequence in response to user input to a sequence editor. At least a subset of the test executive steps in the test executive sequence may be configured to call user-supplied code modules. In one embodiment, one or more expressions may be configured for one or more steps in the test executive sequence, where the one or more expressions evaluate to result values to be logged when the step is executed during execution of the test executive sequence. In another embodiment, one or more parameters of one or more user-supplied code modules called by steps in the test executive sequence may be configured to be logged when the test executive sequence is executed.