![]() ![]() One way to modify or add code in one of these predefined Callbacks is in a process called overriding the Callback. However, you may find yourself at times needing to customize TestStand to your specific needs and Callbacks provide major flexibility when architecting a solution. Callback sequences are optional and a lot of times are empty and possess no code. Callbacks, like process models, are sequences that either execute when certain points of the process model file are reached or when certain events occur in the TestStand Engine. ![]() In TestStand, there are two kinds of Callbacks Model Callbacks and Engine Callbacks. In fact, the desired sequence file and the process model file can communicate with one another. Report generation or database logging) and when it needs to tell the desired sequence file to start executing. The process model is smart enough to know when it needs to do stuff behind the scenes that you don’t need to worry about (i.e. Whenever you execute a sequence file, typically the process model sequence file is what executes first. TestStand comes with three default process models (Sequential, Batch, and Parallel) however you can custom home roll your own.Ī process model itself is a sequence file, however it contains all of the common code needed to run individual sequences and is not specific to any UUT. In TestStand, each sequence file has a setting that identifies a corresponding process model. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |