| || |
TestComplete 4 As a http proxy and a hosts file
I'm a new test complete user and am using it to test an application that is based heavily on web browser requests. Unfortunately, it utilizes the hosts file in windows to redirect traffic back to a local service running on the computer. When you use test complete as a proxy, the traffic goes to the proxy successfully, but unfortunately test complete does appear to utilize the hosts file. Can you suggest any alternatives to allow test complete to record traffic and forward select traffic to the localhost?
Secondly, I've been able to manually edit Tasks to immitate the browser requests I want simply by editting fields in the actual task. However when I run loadtests that use these tasks they never seem to complete. Is this because I'm manually editting the tasks?
Is there anyway for me force testcomplete to end these tasks? Or how can I get them to end themselves?
Anyway, thanks in advance for your help.
Re: TestComplete 4 As a http proxy and a hosts file
Our Support Team has already anwered you via E-mail, here is their answer in case you haven't received it:
<font size="2" face="Verdana, Arial, Helvetica">The Hosts file utilization is not driven by a client application (browser or any other client application) - it is used by the system when resolving host names to IP addresses. TestComplete does not influence the way Windows uses the Hosts file, it just sends the recorded requests as if they were sent by a web browser.
When you use test complete as a proxy, the traffic goes to the proxy successfully, but unfortunately test complete does appear to utilize the hosts file.
You can learn more about the Hosts file here:
What makes you think that there are problems with the Hosts file when you use TestComplete for recording?
<font size="2" face="Verdana, Arial, Helvetica">Most probably, you have edited the requests incorrectly and either TestComplete fails to send the modified requests to the server, or the server does not respond to those requests (in the second case, TestComplete will wait until the "receive timeout" elapses - please see the HTTP Load Testing Options help topic for details).
However when I run loadtests that use these tasks they never seem to complete.
Please consult the HTTP specification to make sure that you are editing the request header correctly: