Hello Jean-Pascal Van Der Endt,
Thank you for the sample project. I do see what you're talking about. I am not certain but I suspect it has something to do with the cache in IE. I found that by putting the test into a loop via this code:
"Elapsed time for NavigateTo (ms): "
answer = Console.ReadLine().Trim().ToLower();
again = answer ==
After the first time NavigateTo the rest execute at a normal rate. Fiddler must be doing something to IE when it installs its hooks... maybe clearing the IE cache?
the Telerik team
Check out the Test Studio roadmap
to find out more about the new performance testing functionality coming in our R2 2011 release this September!
Have you looked at the new Online User Guide
for Telerik Test Studio?