Distributed Measurement and Analysis System with Dynamic Application Builder

Abstract

The separated and distributed measurement analysis system provides a test measurement automation platform that generates automated test suites using solution workflow metadata as solutions that are deployed to the automation engine of the test measurement automation platform. The automation platform provides tools and methods for developing measurements and deploying the solutions to the automation engine without requiring a system restart. The system uses the test measurement automation platform to enable a user to develop measurements for the solutions and deploy and run each solution in the automation engine of the test measurement automation platform without having to compile the solution.

Description

[Technical field]

[0001] The technical field relates to collaborative computing technology, and in particular to a distributed measurement and analysis system. [Background technology]

[0002] Currently, the traditional technical solution available on the market for creating automated test suites for devices such as integrated circuits is a custom programmatic interface. [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] Fortino G. et al.: "Multicast control of mobile measurement systems", INSTRUMENTATION AND MEASUREMENT TECHNOLOGY CONFERENCE, 1998. IMTC / 98. CONFERENCE PROCEEDINGS. IEEE ST. PAUL, MN, USA 18-21, MAY 1998, NEW YORK, NY, USA, IEEE, US, vol. 1, 18 May 1998 (1998-05-18), pages 108-114, XP010281663, DOI: 10.1109 / IMTC.1998.679723 ISBN: 978-0-7803-4797-7, abstract page 108, left-hand column, page 109 left-hand column - page 110, right-hand column, page 111, right-hand column [Non-Patent Document 2] Domenico Grimaldi et al.: "Java-Based Distributed Measurement Systems", IEEE TRANSACTIONS ON INSTRUMENTATION AND MEASUREMENT, IEEE SERVICE CENTER, PISCATAWAY, NJ, US, vol. 47, no. 1 , 1 February 1998 (1998-02-01), XP011024430, ISSN: 0018-9456, page 100, left-hand column - page 102, right-hand column Summary of the Invention [Problem to be solved by the invention]

[0004] Such programmatic interfaces have two characteristic problems. First, the user of the system needs to understand a programming language that affects the concepts of write, build, and deploy. Second, known programmatic interfaces require the user to combine, integrate, and install the programs in the target software ecosystem, as well as restart the application when it is installed. Some of these solutions are specific to only one piece of hardware and may only address a limited part of this specific hardware that they handle.

[0005] Moreover, other conventional solutions require additional hardware on top of the hardware they are managing. In addition, automated test suites for test and measurement systems have solutions that are specific to certain interfaces, such as HDMI, USB, PCI, etc., that are ineffective for other interfaces.

[0006] Therefore, there is a need to address the above-mentioned technical problems and limitations of currently known systems. [Means for solving the problem]

[0007] To this end, the systems and methods described herein provide an automation platform that uses metadata to create automated test suites in separate software, enables the automation platform to provide a method for describing and deploying measurement methods to an automation engine without restarting the system, and provides a method for creating automated test suites in the form of separate software using metadata.

[0008] According to at least one embodiment, a computer-controlled method for creating and executing an automatic test suite in a test and measurement system includes at least one computer processor receiving input indicating measurements to be performed on a device under test (DUT) and a solution workflow of a first solution that constitutes the automatic test suite, and at least one computer processor dynamically executing instructions of the first solution to perform measurements on the DUT without having to compile the first solution.

[0009] The method may further include, in response to receiving the input, at least one computer processor generating solution workflow metadata associated with the first solution.

[0010] Executing the instructions includes using the solution workflow metadata to facilitate dynamic execution of instructions of the first solution without having to compile the first solution.

[0011] The method may further include at least one computer processor building the first solution using the solution workflow metadata to prepare the first solution for execution without compiling after the first solution is deployed to the test and measurement system. Executing the instructions of the first solution may be based on solution workflow metadata associated with the first solution.

[0012] Executing the instructions may include using the solution workflow metadata to facilitate dynamically executing the first solution without restarting the test and measurement system.

[0013] The method may further include providing a user interface configured to interact with an API (Application Programming Interface) in response to user input and to execute the solution workflow based on the solution workflow metadata as part of executing the instructions.

[0014] The method further includes at least one computer processor receiving input indicating additional measurements to be performed and a different solution workflow of a second solution including another automated test suite; in response to receiving the input, the at least one computer processor generating solution workflow metadata associated with the second solution; and, based on the solution workflow metadata associated with the second solution, the at least one computer processor dynamically executing instructions of the second solution to perform measurements on the DUT without having to compile and without having to restart the test and measurement system between execution of the instructions of the first solution and execution of the instructions of the second solution.

[0015] Execution of the instructions may include calling one or more services that are self-registered as part of the test and measurement system.

[0016] The test and measurement automation platform's automation engine is built on a distributed architecture and supports failover and recovery.

[0017] According to at least one embodiment, a computer-controlled method for enabling creation of automated test suites in a test and measurement system includes at least one computer processor providing a test and measurement automation platform that uses solution workflow metadata to create automated test suites using separated software as solutions that are deployed into an automation engine of the test and measurement automation platform, and enabling a user, via the test and measurement automation platform, to develop measurements for the solutions and deploy each of the solutions to the automation engine of the test and measurement automation platform without restarting the test and measurement system.

[0018] Providing a test and measurement automation platform includes providing a test and measurement automation platform configured to receive input for a first solution among a plurality of solutions and dynamically execute instructions of the first solution of the plurality of solutions to perform a test on an integrated circuit.

[0019] According to various embodiments, a system for creating and executing automatic test suites in a test and measurement system includes at least one memory and at least one processor coupled to the at least one memory, the at least one memory having computer-executable instructions stored therein that, when executed, cause the at least one processor to perform one or more of the methods described above.

[0020] According to various embodiments, a non-transitory computer-readable storage medium has computer-executable instructions stored thereon that, when executed by at least one processor, cause the at least one processor to perform one or more of the methods described above.

[0021] The components within the drawings are not necessarily to scale relative to each other. Like reference numbers designate corresponding parts throughout the several views. [Brief description of the drawings]

[0022] [Figure 1] FIG. 1 is a block diagram illustrating elements of an exemplary test and measurement system, which is a separate distributed measurement analysis system that includes an automation platform, in accordance with various exemplary embodiments. [Diagram 2] FIG. 2 is a schematic block diagram illustrating an example computing device upon which an embodiment of a test and measurement system automation platform may be implemented, in accordance with various exemplary embodiments. [Diagram 3] FIG. 3 is a diagram illustrating the workflow of an automation engine according to various exemplary embodiments that may be deployed on an automation platform. [Figure 4] FIG. 4 is a flow diagram of a computer-controlled method for creating and executing an automatic test suite in a test and measurement system according to various exemplary embodiments. [Diagram 5]FIG. 5 is a flow diagram of a computer-controlled method according to various exemplary embodiments for creating and running multiple automatic test suites in a test and measurement system without having to reboot the system between running the test suites. [Figure 6] FIG. 6 is a flow diagram of a computer-controlled method for enabling the creation of an automated test suite in a test and measurement system, according to various exemplary embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0023] Various embodiments of the present disclosure provide an operation platform that uses metadata to create automated test suites in a disaggregated software format. The disclosed automation platform provides tools and techniques to develop or write measurements and deploy the associated solution workflows that compose the automated test suites into an automation engine without requiring a system restart. Furthermore, these measurements are automatically registered in the system and are immediately available to users.

[0024] 1 is a block diagram illustrating elements of an exemplary test and measurement system 100 that is a disaggregated, distributed measurement analysis system that includes an automation platform in accordance with various exemplary embodiments. Shown in FIG. 1 are an automation platform 102, an integrated development environment (IDE) 104, and hardware devices 106.

[0025] The automation platform 102 includes a user interface 108, an analysis (measurement) services engine 110, a core services engine 112, and a template catalog service engine 114. The analysis services engine 110 includes multiple signal measurement services, such as, in this example, a jitter measurement service 116, a base measurement service 118, an eye measurement service 120, a time measurement service 122, and an amplitude measurement service 124.

[0026] The core services engine 112 includes an open application programming interface (API) 126, which may be a RESTful or Representational State Transfer (REST) ​​API designed to leverage existing protocols. Because REST can be used with almost any protocol, developers do not need to install libraries or additional software to leverage the REST API mechanisms. Unlike Simple Object Access Protocol (SOAP), REST is not limited to Extensible Markup Language (XML), but instead can return XML, JavaScript Object Notation (JSON), and other formats in response to client requests. Also, unlike Remote Procedure Call (RPC), users do not need to know the procedure name or specific parameters for a particular procedure. The core services engine 112 also includes an automation engine 128 and a hardware controller 130, which are described in more detail below.

[0027] The template catalog service engine 114, in this example, includes a pattern generator 132, a measurement catalog service 134, a solution catalog service 136, and a device configuration / calibration catalog service 138. The automation platform provides a user interface 108 to facilitate building of solutions by providing, at least as part of the user interface, a menu of test automation workflow or solution templates from which a user can select as a basis for creating one or more solutions.

[0028] Examples of test equipment in the hardware device 106 include an oscilloscope 140, a bit error rate tester (BERT) 142, an arbitrary waveform generator (AWG) 144, and a spectrum analyzer 146, among others.

[0029] By utilizing embodiments of the present disclosure, the system 100 provides an extensibility feature for adding new measurement methodologies to the test and measurement system without the need to restart the application. Additionally, the automation platform 102 also provides the ability to create useful solutions using a solution builder in the user interface 108 and directly and immediately publish the solutions within its ecosystem without the need to restart the system 100.

[0030] In another embodiment, new solutions can also be created using the API 126. Additionally, the automation platform 102 makes it easy for customers to define workflows within their test suites, which may have different types of hardware, such as oscilloscopes 140, BERTs 142, AWGs 144, etc.

[0031] The automation platform 102 is a disaggregated software solution that controls the hardware devices 106, performs analysis of measurements (e.g., waveforms) taken by the hardware devices 106, and executes the solution using an API, such as API 126, via a user interface that provides a visualized experience to a user. For example, the automation platform 102 allows a user to visualize how the test and measurement automation platform 102 controls the hardware devices 106, performs analysis of measurements (e.g., waveforms), and executes the solution.

[0032] Furthermore, the test and measurement system 100 according to the embodiment of the present disclosure is metadata-based, which allows the solution to be deployed without compiling or rebooting. The IDE 104 is used to deploy the measurement service 110 in the software environment of the automation platform 102. The measurement service 110 to be deployed is automatically registered with the measurement catalog service 134 at startup. Once automatically registered, the measurement service 110 can access the automation engine 128 to perform measurements during application execution. Once the solution is deployed to the system 100, it is built and immediately available for use throughout the system. The solution / application builder of the user interface 108 uses a template-based approach by utilizing the template catalog service 114, thereby reducing the overall time for development and deployment.

[0033] Further, in one or more embodiments, the automation platform 102 may be written in JSON. The automation platform 102 may be written as well as other approaches using a domain specific language (DSL). The automation engine 128 reads user input provided for a solution and dynamically executes the instructions. For example, the automation platform 102 may receive input indicating measurements to be performed on a device under test (DUT) and a solution workflow of a first solution that constitutes an automated test suite. The automation platform 102 then dynamically executes the instructions of the first solution to perform tests on the DUT without compiling the first solution. In response to receiving the input, the automation platform 102 creates solution workflow metadata associated with the first solution. Executing the instructions may include using the solution workflow metadata to facilitate dynamically executing the solution without requiring compilation. Executing the instructions may also include using the solution workflow metadata to facilitate dynamically executing the first solution without restarting the test and measurement system. The depicted flow shows the creation and deployment of solution metadata (e.g., JSON metadata 148) that is created and deployed via API 126 to solution catalog service 136, which validates and stores the metadata content. In one embodiment, the creation and deployment of the metadata is done using API 126 (e.g., using OpenAPI using JSON over HyperText Transfer Protocol (HTTP)).

[0034] The user interface 108 is configured to interact with the API 126 in response to user input and execute a solution workflow based on the solution workflow metadata as part of executing the instructions. Illustrated is an exemplary execution request 150 (e.g., a JSON execution request) where the automation engine 128 executes the instructions in the metadata (e.g., JSON metadata 148) by retrieving the metadata from the solution catalog service 136. The automation engine 128 validates the solution execution request 150 against the solution metadata and executes the solution and measurements defined in the solution. For example, a user can send an execution instruction using the API 126 (e.g., using OpenAPI using JSON over HTTP protocol).

[0035] In at least one embodiment, the automation engine 128 uses a microservices approach to call multiple services that are self-registered as part of the ecosystem. Deployed measurement services 110 self-register with the measurement catalog service 134 upon startup. Once self-registered, the measurement service 110 can access the automation engine 128 to perform measurements during application runtime. The automation engine 128 is built on a distributed architecture and supports failover and recovery.

[0036] The automation platform 102 enables the creation of multiple automated test suites within the test and measurement system 100 and the execution of the multiple automated test suites without having to restart the system between execution of the test suites. For example, the automation platform 102 may receive input for a second solution and then create solution workflow metadata associated with the second solution in response to receiving the input for the second solution. The automation platform 102 then dynamically executes instructions of the second solution based on the metadata associated with the second solution to test the DUT without having to compile or restart the test and measurement system 100 between execution of the instructions of the first solution and execution of the instructions of the second solution.

[0037] Additionally, embodiments of the present disclosure provide extensibility features that allow end users to modify the workflow or solution and add additional requirements for testing the DUT at any time, thus reducing the overall time to market.

[0038] 2 is a block diagram illustrating an example of an automation platform computer 210 according to various exemplary embodiments on which an embodiment of the automation platform of the test and measurement system 100 may be implemented. In the illustrated embodiment, the automation platform computer 210 includes computer memory ("memory") 201, a display 202 (such as, but not limited to, a light emitting diode (LED) panel, a liquid crystal display (LCD), a touch screen display, etc.), one or more central processing units ("CPUs") 203, input / output devices 204 (e.g., a button panel, a keyboard, a mouse, RF or infrared receivers, a USB port, other communications ports, etc.), other computer readable media 205, and communications connections 206. The automation platform 102 is shown residing within the memory 201. In another embodiment, some of the contents of the automation platform 102 and some or all of the components are stored on or transmitted through a separate computer readable medium 205. These components of the automation platform 102, preferably executing on one or more CPUs 203, may also perform or otherwise facilitate operations to receive inputs indicating measurements to be performed on the DUT and a solution workflow of a first solution that constitutes an automated test suite, and to execute instructions of the first solution to perform tests on the DUT without compiling the solution. The components of the automation platform 102, preferably executing on one or more CPUs 203, may also perform or otherwise facilitate operations to provide the test measurement automation platform 102 with solutions that use the solution workflow metadata to be deployed to an automation engine of the test measurement automation platform, to create automated test suites that use disaggregated software, and to enable a user to develop measurements for these solutions and deploy each of these solutions to the automation engine 128 of the test measurement automation platform 102 without the need to restart the test measurement system 100.

[0039] Other processing devices and configurations may be used in other embodiments, including but not limited to graphics processing units (GPUs), ASICs, and embedded CPU / GPU blocks. The automation platform 102 may operate as, be a part of, or be coupled or operated in conjunction with various software applications stored in the memory 201. The automation platform 102 also facilitates communication with the IDE 104 and the hardware devices 106 via a communication system 208. The communication system 208 may include many different types of communication media, including those utilized by a variety of different physical and logical communication channels. Examples of media and communications channels include, but are not limited to, one or more of the following: HDMI (registered trademark), Universal Serial Bus (USB), Peripheral Component Interconnect (PCI), Wi-Fi systems, WLAN systems, short range wireless (e.g., Bluetooth (registered trademark)) systems, peer-to-peer network systems, hardwired systems, communications buses, computer network cabling, wide area network (WAN) systems, the Internet, cable systems, telephone systems, fiber optic systems, microwave systems, asynchronous transfer mode ("ATM") systems, frame relay systems, digital subscriber line ("DSL") systems, radio frequency ("RF") systems, cellular systems, and satellite systems, or any operable combination thereof.

[0040] The automation platform 102 includes an API 126 (shown in FIG. 1 ) that provides programmatic access to one or more functions or services of the test and measurement system 100, such as the analytical services engine 110, the core services engine 112, and the template catalog services engine 114, both of which are shown in FIG. 1 . For example, such an API 126 may provide a programmatic interface to one or more functions of the automation platform 102 that may be invoked by any of the analytical services engine 110, the core services engine 112, and the template catalog services engine 114, or other programs 230.

[0041] In an exemplary embodiment, the components / modules of the automation platform 102 are implemented using standard programming techniques. For example, the automation platform 102 may be implemented as a “native” executable running on the CPU 203 along with one or more static or dynamic libraries. In another embodiment, the automation platform 102 may be implemented as instructions processed by a virtual machine running among other programs 230. In general, various programming languages ​​known in the art may be employed to implement such exemplary embodiments, including representative implementations of various programming language paradigms, including but not limited to object-oriented (e.g., JSON, Java, C++, C#, Visual Basic.NET, Smalltalk, etc.), functional (e.g., ML, Lisp, Scheme, etc.), procedural (e.g., C, Pascal, Ada, Modula, etc.), scripting (e.g., Perl, Ruby, Scratch, Python, JavaScript, VBScript, etc.), declarative (e.g., SQL, Prolog, etc.), and the like.

[0042] In a software or firmware implementation, instructions stored in memory, when executed, configure one or more processors (e.g., CPUs) of the automation platform computer 210 to perform the functions of the automation platform 102. These instructions cause the CPU 203 or other processors (such as an I / O controller / processor) to perform the processes described herein.

[0043] The above-described embodiments may also use known or other synchronous or asynchronous client-server computing techniques. However, the various components may be implemented using more monolithic programming approaches, for example, in addition to executables running on a single CPU system, or alternatively may be decomposed using various structuring approaches known in the art, including, but not limited to, multiprogramming, multithreading, client-server, peer-to-peer (e.g., Bluetooth® wireless technology, etc.), running on one or more computer systems each having one or more CPUs or other multiple processors, etc. Some embodiments execute simultaneously and asynchronously, communicating using message passing techniques. Equivalent synchronous embodiments are also supported by embodiments of the automation platform 102. Other functions may also be implemented or performed by each component / module in a different order and by different components / modules and still achieve the functionality of the automation platform 102.

[0044] Additionally, programming interfaces to the data stored as part of the automation platform 102 may be obtained through standard mechanisms, such as, for example, C, C++, C# and Java APIs, libraries for accessing files, databases and other data repositories, scripting languages, or through a web server, FTP server, or other type of server that provides access to the stored data and machine learning models.

[0045] Different configurations and locations of programs and data are contemplated for use with the techniques described herein. A variety of distributed computing technologies are suitable for implementing the components of the illustrated embodiment, including but not limited to TCP / IP, REST, sockets, RPC, RMI, HTTP, and Web Services (XML-RPC, JAX-RPC, SOAP, etc.). A variety of other formats are possible. Other functionality may be provided by each component / module, and existing functionality may be distributed in various ways among the components / modules while still providing the functionality of the automation platform 102.

[0046] Additionally, in some embodiments, some or all of the components of the automation platform 102 may be implemented or provided at least partially in firmware or other hardware form, including, but not limited to, one or more application specific integrated circuits ("ASICs"), standard integrated circuits, controllers (e.g., by executing appropriate instructions, including microcontrollers and embedded controllers), field programmable gate arrays ("FPGAs"), complex programmable logic devices (CPLDs), etc.). Some or all of the system components and data structures may be stored as content (e.g., executable or other machine-readable software instructions or structured data) on a computer-readable medium (e.g., a "hard disk," "memory," "a computer network, a cellular or wireless network, or other data transmission medium, or a "portable media article read by a suitable drive or suitable connection, such as a flash memory device"), thereby enabling the computer-readable medium and one or more associated computing systems or devices to execute or otherwise use or provide the content, or to be configured to execute or otherwise use or provide the content, to perform at least some of the techniques described above.

[0047] Figure 3 illustrates an example automation engine workflow 300 that may be deployed on an automation platform 102 in accordance with various exemplary embodiments. Figure 3 illustrates an example workflow illustrating how a user 302 utilizes the automation platform 102 to perform a first action 304 using the IDE 104 to cause the automation platform 102 to develop a measurement and solution workflow (310), to perform a second action 306 using the API 126 and user interface 108 to cause the automation platform 102 to create a solution using workflow metadata (312) and to have the automation engine 128 deploy the solution using the workflow metadata with the help of the API (314), and then perform a third action 308 using the API 126 and user interface 108 to cause the automation platform 102 to request the solution based on the metadata with the help of the API (316).

[0048] FIG. 4 is a flow diagram of a computer-controlled method 400 for creating and executing an automatic test suite in a test and measurement system 100, according to various exemplary embodiments.

[0049] At 402, the system 100 receives input indicating measurements to be performed on the DUT and a solution workflow for a first solution that constitutes an automated test suite.

[0050] At 404, the system dynamically executes the instructions of this solution to perform the measurement method on the DUT without having to compile the first solution.

[0051] FIG. 5 is a flow diagram of a computer-controlled method 500 for creating and running multiple automated test suites in a test and measurement system 100 without having to reboot the system between execution of the test suites, according to various exemplary embodiments.

[0052] At 502, the system 100 receives input indicating additional measurements to be performed and different solution workflows for a second solution that constitutes a new automated test suite.

[0053] At 504, in response to receiving the input, the system 100 creates solution workflow metadata associated with the second solution.

[0054] At 506, the system 100 dynamically executes the instructions of the second solution based on the metadata associated with the second solution to perform the measurement method for the DUT without having to compile and without having to restart the test and measurement system between execution of the instructions of the first solution and execution of the instructions of the second solution.

[0055] FIG. 6 is a flow diagram of a computer-controlled method 600 for enabling creation of an automated test suite in a test and measurement system 100 according to various exemplary embodiments.

[0056] At 602, the system 100 provides a test and measurement automation platform that uses the solution workflow metadata to create automated test suites using separate software as solutions that are deployed to an automation engine of the test and measurement automation platform.

[0057] In 604, the system 100, through the test and measurement automation platform, enables the user to develop measurements for solutions and deploy each of these solutions to the automation engine of the test and measurement automation platform without the need to restart the test and measurement system.

[0058] Although various embodiments have been described above in this application, it will be understood that various changes in form and detail may be made therein without departing from the spirit and scope of the invention as presented or as set forth in the following claims.

Claims

1. 1. A computer-controlled method for creating and executing an automated test suite in a test and measurement system, comprising: a processor of at least one computer receiving a first input indicative of measurements to be performed on a device under test (DUT) and a first solution workflow for a first solution that constitutes an automated test suite; generating, by a processor of the at least one computer in response to receiving the first input, first solution workflow metadata associated with the first solution; a processor of the at least one computer dynamically executing instructions of the first solution using the first solution workflow metadata to perform measurements on the DUT without having to compile the first solution; receiving, by a processor of the at least one computer, second inputs indicative of additional measurements to be performed and a different second solution workflow for a second solution that constitutes another automated test suite; a processor of the at least one computer responsive to receiving the second input generating second solution workflow metadata associated with the second solution; a processor of the at least one computer dynamically executes instructions of the second solution based on the second solution workflow metadata associated with the second solution to perform measurements on the DUT without having to compile and without having to restart the test and measurement system between execution of instructions of the first solution and execution of instructions of the second solution; A computer-controlled method comprising:

2. The method of claim 1, further comprising a process of building, by a processor of the at least one computer, the first solution using the first solution workflow metadata in preparation for execution without compilation after the first solution is deployed to the test and measurement system.

3. 1. A computer-controlled method for enabling automatic test suite creation in a test and measurement system, comprising: providing, by at least one computer processor, a test and measurement automation platform that uses the solution workflow metadata to create an automated test suite in separate software as a solution that is deployed to an automation engine of the test and measurement automation platform; said test and measurement automation platform enabling a user to develop measurements for said solutions and deploy each of said solutions to said automation engine of said test and measurement automation platform without having to restart said test and measurement system; A computer-controlled method comprising:

4. The process of providing the test and measurement automation platform includes: receiving an input for a first solution of the plurality of solutions; Dynamically executing instructions of said first solution among said plurality of solutions to perform a test on the integrated circuit.

4. The method of claim 3, further comprising providing a test and measurement automation platform configured to:

5. 5. The method of claim 4, wherein providing the test and measurement automation platform comprises providing a test and measurement automation platform configured to create solution workflow metadata associated with the first solution in the plurality of solutions in response to receiving the input for the first solution in the plurality of solutions.

6. 6. The method of claim 5, wherein the process of providing the test measurement automation platform includes a process of providing a test measurement automation platform configured to facilitate deploying the first solution among a plurality of solutions to the test measurement system without having to compile the first solution among the plurality of solutions using the solution workflow metadata.

7. 6. The method of claim 5, wherein providing the test and measurement automation platform comprises providing a test and measurement automation platform configured to build the first solution in the plurality of solutions using the solution workflow metadata to prepare the first solution in the plurality of solutions for execution after being deployed to the test and measurement system.

8. 6. The method of claim 5, wherein the process of enabling the user to develop measurements for the solutions and deploy each of the solutions to the automation engine of the test measurement automation platform includes enabling use of the solution workflow metadata to facilitate dynamically executing the first solution among the plurality of solutions to perform measurements on the integrated circuit without having to restart the test measurement system.

9. 6. The method of claim 5, wherein providing the test and measurement automation platform includes providing a test and measurement automation platform including a user interface configured to execute the solution workflow based on the solution workflow metadata as part of executing the instructions using an API in response to user input.

10. A system for creating and executing an automated test suite in a test and measurement system, At least one memory; at least one processor coupled to at least one of said memories; Equipped with Computer-executable instructions are stored on at least one of the memories that, when executed, cause at least one of the processors to: receiving a first input indicative of measurements to be performed on a device under test (DUT) and a first solution workflow for a first solution that constitutes an automated test suite; In response to receiving the first input, creating first solution workflow metadata associated with the first solution; dynamically executing instructions of the first solution using the first solution workflow metadata to perform measurements on the DUT without having to compile the first solution; receiving second inputs indicative of additional measurements to be performed and a different second solution workflow for the second solution that constitutes another automated test suite; In response to receiving the second input, creating second solution workflow metadata associated with the second solution; Dynamically execute instructions of the second solution based on the second solution workflow metadata associated with the second solution to perform measurements on the DUT without having to compile and without having to restart the test and measurement system between execution of instructions of the first solution and execution of instructions of the second solution. A system for creating automated test suites.

11. The computer-executable instructions, when executed, further cause the at least one processor to:

11. The system of claim 10, further comprising: building the first solution using the first solution workflow metadata to prepare the first solution for execution without compiling after the first solution is deployed to the test and measurement system.

12. A computer program product that, when executed by at least one processor in a test and measurement system, causes the at least one processor to: receiving a first input indicative of measurements to be performed on a device under test (DUT) and a first solution workflow for a first solution that constitutes an automated test suite; In response to receiving the first input, creating first solution workflow metadata associated with the first solution; dynamically executing instructions of the first solution without having to compile the first solution using the first solution workflow metadata to perform tests on the DUT; receiving second inputs indicative of additional measurements to be performed and a different second solution workflow for the second solution that constitutes another automated test suite; In response to receiving the second input, creating second solution workflow metadata associated with the second solution; Dynamically execute instructions of the second solution based on the second solution workflow metadata associated with the second solution to perform measurements on the DUT without having to compile and without having to restart the test and measurement system between execution of instructions of the first solution and execution of instructions of the second solution. Computer program.

Images