Thanks for your input! > Have you explored the possibility of "Import Element"? > In other words, an element that would "import a jmx file" into the > namespace of the current test plan. > Then Module Controllers should be able to reference the nodes of the > imported JMX. > For example, "Import auth_lib.jmx as UserAuthentication", "Module > Controller, element=UserAuthentication / login"
Yeah, I was thinking about something like that - using a merge feature. However, it doesn't seem to not be an optimal solution for the case when I have 20+ "libraries" with a certain level of depth each having multiple nested modules/elements that also can reference other external libraries. Eventually the test plan still would look huge and hard to read/navigate. If I understand your idea correctly. Getting back to the solution I'm thinking about - I see a challenge to properly resolve a tree assuming the external modules could potentially be cross-referenced. Do you think it makes sense? //Lena
