fujunxu
Contributor
Joined 12 years ago
User Profile
User Widgets
Contributions
Textexecute still show up in task manager even after I used /exit in windows 10.
I recently upgraded my machine to windows10 and testcomplete to 14. After I coverted my testscript to 14 version. I tried to run it using testexecute command line on windows10 machine with /exit option. Everything works fine except testexecute is still showing up in task manager. And system was getting slowly and slowly. I also test the command line using windows 7 and testexecute quit without any problem. Is there any extra steps I need to prepare for the window10 ? Thanks !!Solved1.7KViews0likes3CommentsRe: Error No debug information was found for MFC control.
NisHera wrote: dose this helps you? Thanks. NisHera. It turns out on the machine I installed the TC 12.30 I don't have those pdb files(I guess because I didn't install visual studio on it). After I copied the pdb files it works fine now.3.2KViews1like0CommentsError No debug information was found for MFC control.
I am upgrading my Testcomplete from 10 to 12. I got Error message" No debug information was found for MFC controls". when I test my testscript using Testcomplete 12.30(tried to click one of the Tab: var afxWnd110u = Aliases.RRD.wndAfx.Afx3.AfxWnd110u; afxWnd110u.ClickTab("Properties"); Everything works fine on TestComplete10. I checked the properties window for the window control and found that on TC 12.30 some of the properties shows "No debug information was found for MFC control" too. I had attache two screen capture to this message. Thanks.Solved3.3KViews0likes5CommentsRe: With error message "The process ... was not found" Runner.Stop(true) stop the whold test.
2nd test item only send logs using email. It doesn't communicate with my application. TC behave differently: 1. I killed my application(process) when the script tried to find the my process using (Sys.Process()). it would raised the "The process ... was not found " and Runner.Stop(true) stopped the whole project. 2. I killed the process when the script tried to find certain window. It would raised "control not found..." and Runner.Stop() stopped the 1st test item and then go to start 2nd test item. I thought Runner.Stop should always stop the current testitem and go to next testitem. Thank.1.3KViews0likes0CommentsRe: With error message "The process ... was not found" Runner.Stop(true) stop the whold test.
I need to call Runner.stop even the tested app is not running. I can check if the process is Exists and then rasie my own error message to make sure it didn't raise the "The process ... was not found" error. But I want to know why Sys.Process caused the Runner.Stop behaved differently. Maybe I miss something ... Thanks.1.3KViews0likes0CommentsWith error message "The process ... was not found" Runner.Stop(true) stop the whold test.
I have two testitems. Testitem1 is the real testing script. Testitem2 is the one send result to users and cleanup... I used the Runner.Stop(true)in GenaralEvents_OnLogError() so when the first testitem failed I can stop and move on to testitem2 (send result to users). It works fine for most of the time. But sometimes I found if my application was crashed during testing the whole test stopped. It looks like when my script run “myprocess= Sys.Process("My Application")” and at the same time my application was crashed my testscript will stop the whole test(it will not run testitem2). It looks like Runner.Stop(true) couldn't handle "The process ... was not found" error or have I miss somthing ? Thanks,1.3KViews0likes4CommentsRe: There is one method(open application) return an object which is string how can I get the string ?
Here is the method signature: const CString CTechBaseGrid::GetStringValue( long a_lCol, long a_lRow ) const. I inspected the object in the "Evaluate Window" and found the value shows "[Object]". After I added it to the watch list it shows two properties: ClassName(ATL::CStringT<wchar_t,StrTraitMFC_DLL<wchar_t,ATL::ChTraitsCRT<wchar_t> > >) and InstancePtr(801881552) Thank you very much for your help!1.4KViews0likes2Comments