Hi Billy,
So this is an interesting discussion that we have been having internally. Similar to my reply to your question about inserting new pages in LC4, this is also related to the concept of simulating parallel requests like a browser. There was actually a bug in LC3 that would start a new connection whenever you created a new page, which is not realistic. It did not have a huge impact on performance metrics, but we like realistic tests. :)
In LC4, we implemented automatic "connection think time" to account for this discrepancy. If you go to the new Timeline tab for any page in the scenario editor, you'll see all of the connections and the wait times. You can manually adjust these by dragging the connections.
However, we have already improved upon this mechanism to preserve realistic connection handling but also account for some logical inconsistencies in the connection think time approach. I've tested the new implementation and it's much closer to what you'd expect, as in LC3. We anticipate this update to LC4 will be delivered along with those other bug fixes in the next week or two.
Best,
Thanks, I will looking connection think times you mentioned. I thought the generic think time value account for this. I appreciate the quick response.
Sounds good. That's part of the discussion we've been having here at SmartBear... we now have (at least) three ways of controlling think time in your scenarios. At the page level (as in LC3), at the request level, and at the connection level (and not counting new operations like Delay). This is great in terms of flexibility, but makes it difficult when you want to control all timings at once. We are hoping to deliver an option to remove all think times in a scenario with a single click, which may or may not be coming in this next update. The other side of the argument is that by removing all think times, you could actually be generating more load than real users would, but my opinion is that it's easier to start from zero and add in think times that are logical to you (or set a random range for think time at the test level).
I agree from zero and working up would be much more intuitive than start with random values and then try to dial each one in.
Thanks I look forward to the update.
Wow, that is really annoying have to go in and tweak every single connection think time. The dragging bar looks nice but it's a pain when you have a page with many connections of varying length. At least clicking on the think time square and being able to edit there instead of dragging everything around would be nice.
Hi Ryan,
Was the feature to set the think time for requests, connections, pages, etc. in bulk completed? I am using the latest TestComplete and having to go thru each request to adjust think time is extremely annoying.
Hi iggz83,
The new release of LoadComplete will be available tomorrow (March 2, 2016) and will contain fixes and improvements related to timings... one of which is the ability to bulk change recorded think times.
