National Instruments Corporation

Scott Richardson

James A Grey

Douglas Melamed

Patrick J Christmas

Patrick Williams

Jose Hernandez

A test executive sequence may be created by including a plurality of test executive steps in the test executive sequence and configuring at least a subset of the steps to call user-supplied code modules. One or more of the user-supplied code modules may take buffer parameters. The test executive sequence may be executed on a host computer under control of a test executive engine. When executing each step in the test executive sequence that calls a user-supplied code module that takes a buffer parameter, the test executive engine may be operable to perform several operations related to detecting a situation where the user-supplied code module writes outside the bounds of the buffer parameter and/or preventing the user-supplied code module from corrupting heap data if the user-supplied code module writes outside the bounds of the buffer parameter.

Test executive with buffer overwrite detection for parameters of user-supplied code modules

A system and method for logging results for a test executive sequence to a database. The test executive software may be operable to receive user input to a graphical user interface (GUI) to specify desired database result logging criteria. In various embodiments, any of various result logging criteria may be specifiable. For example, the user input may specify a mapping of the results for the test executive sequence to the database tables. The user input may also specify criteria for limiting the amount of data logged to the database, e.g., by filtering the results that are logged in various ways. The test executive software may then log at least a portion of the execution results for the test executive sequence to a database, according to the specified result logging criteria.

System and method for configuring database result logging for a test executive sequence

An improved method and system for detecting differences between first and second test executive sequence files in a computer system. Each of the test executive sequence files may comprise a plurality of interrelated objects. The objects may be compared and differences between the objects may be displayed. The objects may comprise one or more of: a sequence; a global variable; and/or a data type. A sequence may comprise: a step, a parameter, and/or a local variable. A step of a sequence may comprise a tree structure of step properties. Each step property may comprise one or more of: a property value, property flags, and/or a property comment. An object may comprise a hierarchy of objects (e.g., a parent object and a child sub-object). Differences between the hierarchy of objects may be detected. Differences may be navigated. Each displayed difference may be characterized as an insertion or a deletion.

System and method for graphically detecting differences between test executive sequence files

A system and method for importing and exporting test executive values from or to a database. A test executive may provide the user various places, referred to as variables and properties, in which data values can be stored. These data values may affect execution of a test executive sequence. Variables may be global to a sequence file or local to a particular sequence. Each step in a sequence can have properties. The user may include a Property Loader step in a sequence, which is operable to dynamically, i.e., at run time, load property and/or variable values from a database. The Property Loader step may be placed in a setup group of the sequence, and the step(s) whose properties are configured may be placed in a main group of the sequence, so that when the sequence is executed the steps in the main group are configured with appropriate property values before running. The test executive may also enable a user to interactively, e.g., through a user interface menu item, request variable and property values associated with a sequence to be imported from or exported to a database. For example, after exporting values to a database, the values may later be used to dynamically configure a test executive sequence.

Growing community of inventors

Austin, TX, United States of America

Scott Richardson