Thank you for the response. Regarding script generation:
Currently I am modifying the script's XML directly. I was just wondering whether there is a more elegant way to do that. Additionally looking at the XML I am bit confused about the structure. The HTTP Sampler and the HeaderManager (or better the hashtree containing it) are at the same hierarchy level. Processing it using a "regular" XML library might not preserve the order of the elements which then would mess up the scripts. I also wanted to get rid of this manual step to perform. Using the proxy recorder seems to be a good approach. If I understood you correctly I could access all request/response content there (what I was referring to as context) and also add my additional header to the script. The header would contain a key of timer name - as it is named in most load testing tools - to identify the request in a more human friendly way than just the URL. By default the timer name would be used - that's why I need access to it. Is there a standard way to hook into the Proxy Recorder or would I have to develop my own one by subclassing. I am looking for the easiest and also less maintenance intensive way to do that. Add-Ons: I had a look on how to write add-ons however this was only related to adding components to the UI. Possibly I just did not find the right place. Test Start/Stop Hooks: My question on session recording might have been a bit misleading. I meant that our tool automatically records diagnostics data during test execution. This means I would require some hook when a test run starts and ends, where I could invoke custom code. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
