Unfortunately, I don't think the WebTest Export extensibility enables the level of customization you seek. The extensibility model enables plugins to skip writing certain steps to the test, and add extraction/validation rules, but it doesn't provide any mechanism to change the XML of the step as it's written to the file.
Fiddler does promote the Session's ui-comments
flag to a CommentText
element in the XML, but I assume that Visual Studio isn't smart enough to fallback to the comment if the ReportingName
I could probably tweak the code such that Fiddler sets the ReportingName
attribute if the your plugin sets a WebTest-ReportingName
flag on the Session?
With regard to the "replace a value with a WebTest parameter"-- I don't know enough about your scenario to understand what this would entail? It may already be possible to do this with your PreWebTestSave event handler...
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.