Somtime TestComplete is crashed without special reason
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Somtime TestComplete is crashed without special reason
Hi,
I have 2 issues with version 12.0.122.7 on Window 8.1
#1. Sometime the tool TestComplete is shutdown when it is launched normally without any special reason.
The error is informed that "The TCHookX64.exe process either does not respond or does not exist."
#2. The test can not executed by the error "Project.Variables" is null ot not an object. This occurs with a frequency about 3/5 running testcase.
Notice that 2 issue does not occur when restart TestComeplete again. Please help me to give any solution for this, because it takes time to restart again. I was re-install tool again, but this issue is still occur.
Please see attachment for more details.
Thanks,
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1) I had a similar issue in a different version of TC. I believe you'll need to contact support about that one.
https://support.smartbear.com/message/?prod=TestComplete
2) You can try putting a log message right before the Project.Variables line and have it show you the value of the variable. It sounds like you're not always getting the value that you expect.
Marsha_R
[Community Hero]
____
[Community Heroes] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Heroes]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Hero] signature is used with permission by SmartBear Software.
https://community.smartbear.com/t5/custom/page/page-id/hall-of-fame
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Marsha_R,
Thanks for your replying,
#2: I was tried as your comment but this bug is still occur. I think no problem with this simple syntax to check variable is exist. This issue should be called bug because it does not occur when restart tool again.
