Since the post and request you refer to date back six years ago, I guess that the desired scenario can be covered with the functionalities in Test Studio nowadays.
Here is what I have in mind - you can prepare a standalone code file
in the Test Studio project, which will be accessible for all tests in the current project. This file can contain any type of custom code, which you can then reuse in coded steps
in each test. You also can include reference to any external dlls
in the project and use these in the coded files.
Then you can reuse these global variables from the Helper standalone class file across the tests - the only limitation is that you cannot use them in the UI, but need to get the variables in code. Still, if you would like to keep the visual representation in the UI, you can use Get and Set ExtravtedVariable()
methods in coded step, and then assign the variable in the UI.
Moreover, during the test execution you can access the ExecutionContext class
in a coded step and take some of the data in real time. Along with the Manager class
you can have access to all of the listed information.
Then, to cover any possible scenarios, you also have the ability to design an execution extension
if you need to customize some actions before and after test or test list run.
I hope these shared details will be helpful for you. However, if I have missed anything in the scenario you need to cover, or have misread any of the requirements, do not hesitate to get back to me with further details on the case and we can continue the discussion.
Thank you in advance for your cooperation and understanding.