Looping and Measuring Steps

Thanks for the answer.

These testplan loop structures can get huge, take hours, even days to complete for R&D tests.

When using the OnTestStepRunCompleted to handle loop parameter logging we first have the full list of parameters when the most outmost loop step is done, and first then we can store the results with reference to the list of all loop parameters. So, the logger must collect data for hours before we have a complete data set. Not nice if something goes wrong, then hours of data is lost.

I can also see that Jason Hicks are make a hack in his else very help full Mongo DB listener example

MongoDB anyone? - #14 by jason.hicks.

In the example Parameters / Meta data are stored as results and he is distinguishing parameters from results solely by the structure of the data. This is a hack and will limit test step writers a lot in how to publish results. Do we have other solutions? Do we need to make a new requirement to the listener system?