Byron,
As Elaine said, the property loader is used in the same way for every step type. Specifically for the multiple numeric limit test there is one scenario where the property loader will throw an error. If you set the property loader to load limits for 2 measurements in a multiple numeric limit step (e.g.
Step.Result.Measurement[0].High AND
Step.Result.Measurement[1].High),
then all your Multiple Numeric Limit Steps (that are listed in your file from where you'll import the properties) in your sequence should be configured to have at least 2 Measurements. Otherwise (if one of them is set to have just 1 Measurement for example), the property loader will throw an error saying that it failed to import or export properties.
I assume th
at this is what you mean when saying that the property loader doesn't handle multipe numeric limit steps. There's no problem with the simple Numeric Limit Tests since these type of steps will always have one property called Limits.Low and one Limits.High, whereas the multiple numeric limit test can have multiple Limits.High and Limits.Low.
In order to make the property loader work without throwing an error is by simply setting it to "Ignore Run-time errors" (double-click on the property loader step to open its properties window. Switch to the Run Options Tab and uncheck the "Ignore Run-time errors" checkbox at the bottom of the screen).
This way, if a multiple numeric limit step just has 1 measurement (along with the properties Step.Result.Measurement[0].High/Low/Comp) and the property loader is configured to also load properties for a second measurement (Step.Result.Measurement[1].High/Low/Comp), you will get an error but it will be ignored and the properties for the first measure
ment will still be loaded.
I hope this will solve your problem. Let me know if the above is not clear, if you need further information or if this is not the scenario where you were having problems.
Regards,
Carlos Leon