Forum Discussion
AlexKaras
14 years agoChampion Level 3
Hi Sri,
It is hard to say anything definite without seeing and any knowledge about your particulair application. The best bet may be to have a talk with developers and ask them to describe you how the tested application works.
Meanwhile I can stay with my previous explanation:
-- The browser sends request for the ReportViewer.aspx page;
-- Server processes the request and returns html page (with embedded java-script code and data (i.e. raw bytes sequence for the report)) within 9 seconds time interval;
-- Client (i.e. the browser) receives server's response (that takes mentioned 9 seconds) and from this moment no http requests are send over the network, so there is nothing for TestComplete to record;
-- Client processes java-script code within the page. The code can be quite complex and require some time to be executed;
-- Also the code may instantiate an instance of Acrobat ActiveX control within the page. Control's instantiation and initialization also takes some time;
-- Acrobat control processes report's data - one more time penalty;
-- Only now all page processing is over and end-user can see the page as loaded with the report opened. The time required to execute the page code, instantiate Acrobat control and generate report can easily be up to 30-40 seconds.
It is hard to say anything definite without seeing and any knowledge about your particulair application. The best bet may be to have a talk with developers and ask them to describe you how the tested application works.
Meanwhile I can stay with my previous explanation:
-- The browser sends request for the ReportViewer.aspx page;
-- Server processes the request and returns html page (with embedded java-script code and data (i.e. raw bytes sequence for the report)) within 9 seconds time interval;
-- Client (i.e. the browser) receives server's response (that takes mentioned 9 seconds) and from this moment no http requests are send over the network, so there is nothing for TestComplete to record;
-- Client processes java-script code within the page. The code can be quite complex and require some time to be executed;
-- Also the code may instantiate an instance of Acrobat ActiveX control within the page. Control's instantiation and initialization also takes some time;
-- Acrobat control processes report's data - one more time penalty;
-- Only now all page processing is over and end-user can see the page as loaded with the report opened. The time required to execute the page code, instantiate Acrobat control and generate report can easily be up to 30-40 seconds.