How does one deal with iteration in loadUI?
Hi I'd like to create a project in loadUI that implements a scenario in which a number of virtual users are ramped up to a certain number, and then each virtual user should iterate over a number of...
Forum Discussion
SmartBear_Suppo
Alumni
AlumniHi Lars,
sorry for the long delay; your questions started a bunch of internal discussions on how this should be best handled :-)
For now the current runner components just add their response times to the incoming message before they pass it to the output, so you should be able to create a component that adds a "sessionId" property to the message before it is sent to the first runner, the same component could have a separate input that would come from the last runners output (just like you describe), in which it would see the sessionId and could add/increase a counter property "sessionCounter" before it gets dispatched to the first runner again (if desired).
Does that make sense? If you get this working ok, please don't hesitate to submit your component to our component-competition :-)
regards!
/Ole
eviware.com
sorry for the long delay; your questions started a bunch of internal discussions on how this should be best handled :-)
For now the current runner components just add their response times to the incoming message before they pass it to the output, so you should be able to create a component that adds a "sessionId" property to the message before it is sent to the first runner, the same component could have a separate input that would come from the last runners output (just like you describe), in which it would see the sessionId and could add/increase a counter property "sessionCounter" before it gets dispatched to the first runner again (if desired).
Does that make sense? If you get this working ok, please don't hesitate to submit your component to our component-competition :-)
regards!
/Ole
eviware.com