Double Ten technology about TestStand open architecture
Process Model(Process model)
Section 3.2 describes the Execute; Single Pass "and" Execute; Test UUTs "executes the main sequence, and
The "Execute" of Chapter 2; Run MainSequence "compared to the first two to perform 7 additional operations, such as input
Serial numbers, generating reports, and displaying test results are some of the more common operations. Focus on the sequence text first
The "Computer Motherboard Test Sequence.seq", as an example, contains very much
More steps, these steps are specific to the computer motherboard this particular UU, when click menu command
"Execute; After running MainSequence, TestStand performs only the steps in the main sequence (Figure 3-4)
As shown).
At the top of the standard automated test system architecture, test management software provides modular testing
Framework. In TestStand, this testing framework is called Process Model, while using
The Sequence File of the process model is called the Client Sequence File. Review # 1
Chapter introduces the composition of automatic test system, test software is subdivided into test program, automatic test box
Shelf, which corresponds to the test program in TestStand, the client sequence file, and the test framework, the process model. in
The main sequence of the client sequence file is just one of many common operations that are included in the process model
The process model defines the framework and reserves a place for the client sequence, which the developer is responsible for filling out
Part is OK.
As shown in Figure 3-5, if the process model is used, TestStand will not only perform the tests once they are started
The houseside master sequence also performs all operations in the order defined by the process model, as shown in simplified Figure 3-5
Meaning process, that is, common operation, client sequence. General operation. In this form, TestStand will be a lot
Common operations such as serial number tracking, flow control, report generation, and data storage are provided directly to the developer
Storage, user interface updates, configuration and prompt Windows, user management, and so on, developers no longer need to start from scratch
This part is working. The extra work TestStand needs to do is to resolve between generic operations and client sequences
Communication and data sharing problems. In fact, the process model is conceptually simple. It is a combination of generic operations and specific operations
Operations are grouped together to form larger test sequences. How and what general operations are included
Process model decision. The process model itself is a sequence file, and TestStand comes with three process models
, respectively are sequential process model, parallel process model, batch process model, the latter two have parallel testing
Users can also create new process models as needed.
Execution Entry Point Execution entry point
The process model defines the testing framework and common operations. In practice, different projects use procedures
Model, with different requirements for the common operations it contains and the order in which they should be executed,
So each time you have to modify the process model, or create a new process model, over time, the process model becomes more and more
The more you come. To avoid this, TestStand introduces the concept of execution entry points. Take Figure 3-6 as an example, false
Let the process model have three different execution entry points A, B and C, and the difference between A and B lies in general operation 2
And MainSequence in order of 7, while in C common operations 1 and MainSequence are in the loop
In. Therefore, choosing different execution entry points means different ways of running. To put it bluntly, or
These operations are simply rearranged and combined to meet the needs of different applications. As in section 3.2
Single Pass and Test UUTs are two different execution entry points for the same process model, Test UUTs
It tests different UU numbers consecutively, as opposed to a Single Pass, for that reason. Each process model can
To have any number of execution entry points, you can create and add as needed.

Callback Sequence(Callback sequence)

Using execution entry points, you can define your own sequence execution style, whereas execution entry points contain
In these common operations, their functions are predefined, and developers may need to modify the default functions
Yes. By default, TestStand displays a window that prompts the user to enter the sequence manually
Column number, but in the actual production line is often the use of bar code gun directly scan, do not need to manually input, which is required
The general operation of modifying or overriding sequence number input. How do you modify it? The most direct way is in the execution entry
Point to directly modify common operations, which can cause potential problems if the product is upgraded or completely updated
These common operations have to be adapted to the new product, and the common operations at the execution entry point need to be modified
Or create a new execution entry point. As the number of products increases, the number of modifications to the entry point increases,
Or as the number of them increases, system maintenance becomes very difficult. To avoid this, TestStand cites
Enter the callback sequence. TestStand sets common operations that are frequently modified to a sequence of callbacks, each sequence of callbacks
There are default functions defined, but they can be overridden by client sequence files. As shown in Figure 3-7, the incoming command is executed
Three callback sequences are defined in the interface, and callbacks 1 and 3 are overridden in the client sequence file. when
When TestStand executes each callback sequence under the procedure model framework, it checks to see if the callback sequence is
Overridden by client sequence file, if so performs the definition in the client sequence file, otherwise performs the default
Operation. In this way, common operations can be customized, and this part of the work is placed on the customer
End sequence file, reducing changes to the process model and execution entry points. Through the process model, execution
TestStand has three different levels of interfaces: entry points and callback sequences
Show it step by step.
Overview of the TestStand architecture
Chapter 2 introduces the TestStand system components (see Figure 2-5), including the TestStand engine and the sequence programming
The integrator, user interface, module adapter, deployment tools, TestStand engine is the most core part of it
Holding everything together, the sequence editor and user interface interact with it through the TestStand API.
TestStand needs a module adapter to call code written in other application development environments.
This chapter introduces the concepts of process models, execution entry points, and callback sequences, which are TestStand representations
The concrete implementation of a powerful and flexible open architecture, and because of this, TestStand is much more than just a test actuator
Easy. In a nutshell, TestStand system components support test management, process control, process modeling,
Execution entry points, callback sequences, and client sequence files materialize these functions, which are integrated in
Together, it forms the entire structure of TestStand. Open the TestStand Architecture Overview document '
TestStand
/ Doc/Manuals/TestStandSystemandArchitectureOverviewCard. PDF, as shown in figure 3 to 8
Show. The relationship between the TestStand system components is consistent with that shown in Figure 2-5. On this basis, it is added
Details of process model, sequence file execution. The operation of the process model is also powered by the TestStand engine
It accesses the engine through the TestStand API, and the sequence file execution underlying is also done by TestStand
The engine takes over. Expand sequence File Execution so that only the sequence file is executed if no process model is used
The steps included; If a process model is used, the execution proceeds in the manner specified by the process model
Row, execution procedures produce test results, common operations in the process model are collected and generated
Report, record database or do data offline analysis. That's basically what the TestStand architecture is all about
A surname.