Forum Discussion

sdruker's avatar
sdruker
Contributor
11 years ago

Http Trafic handling

Hi,



Is there a way to track http traffic in testcomplete? I see that in the past it was possible by using load test tasks but now this feature is not available anymore. (I have testcomplete 10.3)



I am testing a web application, and I want to track the browser http trafic.

for example, when a chckbox is checked in my webpage, there are 2 http request that are sent:

1. post

2. get

I want to verify that the get response has recevied and her status is ok 200 and just after verifying , continue to the next step.



I read all the articles regarding this subject, and I saw the solution of "MSXML2.XMLHTTP". object. But this is not sutiable because by using this object, the script is sending the request,

In my case I want that test complete will change the checkbox state to true, and after that search for the response somewho.



any ideas?
  • AlexKaras's avatar
    AlexKaras
    11 years ago
    Hi Sivan,



    I am afraid to say that TestComplete does not support the functionality you are talking about.

    All former Load Testing functionality of TestComplete was moved to the LoadUIWeb product (http://smartbear.com/products/qa-tools/load-testing/ and don't miss LoadUIWeb with LoadUI (http://smartbear.com/products/qa-tools/web-service-load-testing/) - these are different products).



    However, I am not sure if you are not mixing two testing approaches here...

    TestComplete is primarily designed to check the functionality of the tested application from the end-user point of view. And as the end user, I have no idea of what happens when I am checking some check-box. What I do care in this case is that the check-box is ticked and this either results in some on-screen action or has some (defined!) influence on my subsequent actions and observed results. And this is what can be implemented and tested using TestComplete.

    All at all, I think that this is not check-box that issues http request when been ticked, but some script triggered with onclick action. This means that if the script for some reason was not executed (blocked or not linked to the check-box control), the check-box will still be ticked (as this is internal functionality of the control which is controlled by the browser), but there will be no expected result of this tick and this can be detected by TestComplete.



    On the other hand, LoadUIWeb is designed to record all requests issued by the tested application when end-user performs some actions and then replay recorded requests unattended (i.e. without the necessity the tested application be running) and check that obtained responses match those that were received during recording.

    So, with the LoadUIWeb it is possible to record the request issued when the check-box is ticked and replay this request later and check that the obtained response has code 200.
  • AlexKaras's avatar
    AlexKaras
    Champion Level 3
    11 years ago
    Hi Sivan,



    I am afraid to say that TestComplete does not support the functionality you are talking about.

    All former Load Testing functionality of TestComplete was moved to the LoadUIWeb product (http://smartbear.com/products/qa-tools/load-testing/ and don't miss LoadUIWeb with LoadUI (http://smartbear.com/products/qa-tools/web-service-load-testing/) - these are different products).



    However, I am not sure if you are not mixing two testing approaches here...

    TestComplete is primarily designed to check the functionality of the tested application from the end-user point of view. And as the end user, I have no idea of what happens when I am checking some check-box. What I do care in this case is that the check-box is ticked and this either results in some on-screen action or has some (defined!) influence on my subsequent actions and observed results. And this is what can be implemented and tested using TestComplete.

    All at all, I think that this is not check-box that issues http request when been ticked, but some script triggered with onclick action. This means that if the script for some reason was not executed (blocked or not linked to the check-box control), the check-box will still be ticked (as this is internal functionality of the control which is controlled by the browser), but there will be no expected result of this tick and this can be detected by TestComplete.



    On the other hand, LoadUIWeb is designed to record all requests issued by the tested application when end-user performs some actions and then replay recorded requests unattended (i.e. without the necessity the tested application be running) and check that obtained responses match those that were received during recording.

    So, with the LoadUIWeb it is possible to record the request issued when the check-box is ticked and replay this request later and check that the obtained response has code 200.