Forum Discussion
Hi,
> It appear randomly.
I have a guess that the error appears when the test is started when the tested site is opened in the browser. Can you confirm this? (Or, maybe, the opposite - the error appears when the test is started when the tested site is not opened in the browser.)
Scenario that I am guessing:
> var titlepage = Aliases.browser...
> ...
> BrowserConfig.killBrowserProcess(...)
> ...
> titlePage.WaitProperty(...);
As it is documented, Aliases uses late binding, resolves referenced object at first use and tries to cache it.
I think that titlePage variable keeps the reference been set initially and this reference becomes invalid when the browser is closed and reopened. Obviously, when test code tries to wait for the Visible property to become true for the empty object, this never happens.
My suggestion will be to:
a) Comment out the .RefreshMappingInfo() line;
b) move the var titlepage = Aliases... line of code to follow the LoginCredentials.basicAuthenticationKeyword(...) line.
Does this help?
P.S. BTW, JScript is a case-sensitive language, but you have titlepage and titlePage variables in your test code. Is this really so?
I will your approach.
But one thing here is we already running our same firefox tests , we do not have such issues on those firefox tests .
for titlepage and titlePage - I made a mistake .
- Marsha_R4 years agoChampion Level 3
One thing from our side, if you don't give us all the details up front, then we have to keep guessing and you keep telling us no that can't be it. It works better for everyone if you give us lots of details first and then we can give a better answer. Thanks!
- Marsha_R4 years agoChampion Level 3
If what AlexKaras and I have suggested is not working for you, then contact Support directly with your question. Here's their link:
https://support.smartbear.com/testcomplete/message/
- nisgupta4 years agoValued Contributor
what details you need ?
Here are other details. We are using window task scheduler. We create a batch script to invoke the projectsuites/Project and they are running in sequence on TestExecute machine. We first run our firefox Project Suits/Project and then chrome ProjectSuites/Project.
Let me know if you need more information.
- nisgupta4 years agoValued Contributor
Has any one successfully running Testcomplete tests on chrome browser tests ?
I am getting this error This operation has been time out .
I have also increased method invoke time out to 10000 under the open applications - Under Project current properties.
Let me know if more information is required.
Thanks
NG
- AlexKaras4 years agoChampion Level 3
> Has any one successfully running Testcomplete tests on chrome browser tests ?
I am. (Though not on the latest Chrome)
- nisgupta4 years agoValued Contributor
I was working with Support on this issue.
I have submitted all the information
1. project containing the error log.
2.report generated using Report generator command utility.
But they told me as following
We have researched the bat file you sent: it looks like when you use this command: START "" "C:\Program Files (x86)\SmartBear\TestExecute 14\x64\Bin\ReportGenerator.exe" --chrome --generate-report "C:\TE Results\Work", you just save reports (memory dumps are not saved). The only possible way we can see here is to reproduce the issue manually (I mean running the test manually until the test hangs). It is very important to create dumps when the test "hangs", and only this way allows collecting dumps at the needed moment (to click the "Generate memory dump" button when TestComplete hangs).
I have a question is there any way that we can generate memory dumps automatically?
Please advise
Thanks
Nishchal
- nisgupta4 years agoValued Contributor
Support has not find any solution for the issue .
Related Content
Recent Discussions
- 2 days agovladd1