Forum Discussion
Hi Marcl and All
I appriciate this was nearly three years ago! But I came across this post looking for the same answer to Marcl.
To my avail I managed to work out something that worked for me to have the assertion to spit out the Value when it fails, so that you can clearly see which value is failing when load testing massive amount of data.
All you need to do is set a "count" assertion and have it look for the: ${DataSource#}
This in turn spits the "missing token" that is the value / data in the LoadUI log
Provided this will only work if response contains the value your entering!
For me this works perfectly as I am testing over 610k values aka pieces of data.
Hopefully this helps someone somewhere!
- TanyaYatskovska7 years agoSmartBear Alumni (Retired)
Hi Christian,
Thanks for sharing your solutions with us.
This helps the Community a lot!