02-14-2022 09:20 PM
Hello Everyone,
I am newbie to learn more about TestStand Architecture.
I would like to understand about TestStand plugins. What is the advantage of using plugins? We should be able to modify the process model call back sequence to perform the same operation.
Solved! Go to Solution.
02-18-2022 11:49 AM - edited 02-18-2022 11:52 AM
I'll throw my 2 cents into the hat here.
Plugins are one of the best improvements to TestStand in a long time. Basically what they've done is abstracted the report generation/database logging out of the process models. It used to be that back in the day you had to edit the process model to customize the report, or override a callback as you mentioned. But now that is all abstracted out.
Doing this did several things:
To your specific question about overriding callbacks. Callbacks are meant to be used when you want to deviate from the default behavior. So it all depends on your use case. Also, with callbacks you are only limited to the callbacks defined in the plugin or process model. So you are really just taking an out of the box plugin and changing some behavior for that specific client file.
My rule of thumb is this: If it is just for this test and the plugin supports what I want then do it in a plugin. If I want it for all tests and/or the functionality doesn't exist then create a plugin. Example being an Excel plugin (which I've created).
Hope this helps,
02-20-2022 07:36 AM
In addition to Sam's answer here is my presentation about the subject (more about how it works than when to use it but since you are calling yourself a newbie you might find it useful).
02-23-2022 01:57 AM
Thank you so much for detailed explanation about plugins and callbacks.
02-23-2022 02:00 AM
Thank you Michal. Very good presentation.