you might have to go through some tedious exploration until you find what you're looking for.
I recorded a login Load test against our website (www.telerik.com). I found the request that sends the user/password but it took some digging. I started out at the first transaction and went through no fewer than 58 requests until I got to the one I was looking for. And it was far from obvious that it was the right one:
I don't see the user name and password fields in "Bind Unique User Info" section.
But as you can see from my example - those are not always easy to find. As you can see in my example - the words "user" and "password" are in there but they're buried in a larger string. So it comes down to knowing your app and searching. I hope this helps.
I will talk to our engineers and discuss some sort of search functionality. You usecase got me thinking that this is going to be a useful edition.
Let me know if you need additional assistance.
All the best,
the Telerik team
Are you enjoying Test Studio? We’d appreciate your vote in the ATI automation awards.