>test plan can >be run in different envs with different jmeter installation paths
Do you think relative path is a viable solution? An alternative option is to have "library paths" JMeter propery, so it would lookup libraries in the given set of paths. When it comes to the UI, I would love to see the included elements, and it would be great to drill down into the implementation (e.g. to verify you call the right fragment). It would be great if UI suggested the available elements and highlighted errors like "calling a non-existing fragment" or "library file missing". I might be wrong, however, dynamic file names make it harder to implement user-friendly UI. >jmeter benefit in it's visual way of building test scenarios in just a few clicks That's fair. Vladimir
