Forum Discussion
HKosova
Alumni
14 years agoHi Baba,
If you mean that the old value is still displayed in the Task editor, this is normal. Any changes made at run time are preserved only during the test run and not applied to the original recorded requests. The load test log, though, will display the actual URL in the Headers panel.
If the URL isn't actually getting updated, I suggest that you debug the event handler to see why this could happen. That is, set a breakpoint inside the event handler and when the test is paused, inspect the Request parameter in the Locals panel before and after the replace operation.
It is also possible that you need to use case-insensitive replace because aqString.Replace is case-sensitive by default. To do this, add False as the last parameter of the method call:
the string replace that you have suggested is also not working. it is still displaying the old value after doing a string replace.
If you mean that the old value is still displayed in the Task editor, this is normal. Any changes made at run time are preserved only during the test run and not applied to the original recorded requests. The load test log, though, will display the actual URL in the Headers panel.
If the URL isn't actually getting updated, I suggest that you debug the event handler to see why this could happen. That is, set a breakpoint inside the event handler and when the test is paused, inspect the Request parameter in the Locals panel before and after the replace operation.
It is also possible that you need to use case-insensitive replace because aqString.Replace is case-sensitive by default. To do this, add False as the last parameter of the method call:
Try that and let me know the results.