ContributionsMost RecentMost LikesSolutionsRe: Does TestComplete supports Mercurial Source Control System?Hi Ory, I could not find any free tool that will integrate TestComplete with Mercurial, however there are few paid providers which I did not try because of the cost involved. Regards, Harshad KashikarRe: NameMapping: Property values of objects getting modified at runtimeHi Alex, Thanks for the reply. I will not be able to send you the project suite, but have sent the crash dumps and screen captures to support team on the link link provided by you. Regards, Harshad KashikarRe: My NameMapping changes with each runHi Kevin, From your code "Aliases.ceraexe0471.wndAfx.MDIClient.wndAfxFrameOrView8018.AfxWnd80.AfxWnd80", it seems that the parent object of "AfxWnd80.AfxWnd80" also has some numbers postfixed which are also getting changed. Have you modified the properties of that object (wndAfxFrameOrView8018) as well in the NameMapping by putting anasterisks? I would recommend you to check every parent object in the hierarchy, whether it is recognized by TestComplete or not. You can do that by doing right click on the object and selecting "Highlight on screen" option and see whether the object is actually getting highlighted or not. (Make sure that the object exists and is visible on screen before highlighting it). If this also do not help,try using some other properties such as Name or any other property that can be used to recognized the object uniquely. Regards, Harshad KashikarRe: NameMapping: Property values of objects getting modified at runtimeHi Alex, Thanks for the reply. Just to clarify that we are not using the Record/Playback approach and all the UI objects are mapped manually using the "Object Map" functionality of TestComplete. Also it would be difficult to do recording of this issue as we cannot say that mapping of which particular obejct is causing properties of other object to change (Since we have many objects and mapping of one object changes properties of any other object). If we try to see the properties of object which was not recognized at runtime, TestComplete crashes as soon as we click on that particular object. I will definitely upload the TC logs after reproducing this issue. By, any chance, is it possible that TestComplete is re-writting the property values of object in the NameMapping file? Regards, Harshad Kashikar Re: how to ignore breakpointsHi Anders Wittrup You can disable the debugging option while running the overnight scripts. To do this, just click on "Enable Debugging" menu item from the "Debug" menu. While testing scripts, you can enable debugging again by clicking on "Enable Debugging" menu item from the "Debug" menu. Regards, Harshad KashikarRe: My NameMapping changes with each runHi Kevin, You can try using wild-card character asterisks (*) to get through this issue. To do this, open the NameMapping file, go to the object "Aliases.ceraexe0471.wndAfx.MDIClient.wndAfxFrameOrView8018", in the right pane the property value of object should display something like "wndAfxFrameOrView8018", edit this value and to remove the number and put an asterisks there. e.g. "wndAfxFrameOrView*". This should allow identification of object even though the number changes. Regards, Harshad Kashikar NameMapping: Property values of objects getting modified at runtime Hi I am using TestComplete 7.5 to automate a dot net WinForms application. I am facing an issue with NameMapping functionality of TestComplete. Please find below the description of the problem Problem: Name-Mapping properties of certain object gets updated automatically at runtime by TestComplete. Details: When an object is mapped, TestComplete stores some properties of the object and their values to identify that object uniquely. We are facing a weird issue with some of the objects which is explained below with the help of an example. Consider an object "object1" is mapped which has property value pair as "NativeClrobject.Name = value1" and after that if another object say "object2" is mapped which has property value pair as " NativeClrobject.Name = value2" (Note that same property is being used to identify both the objects and the objects will be distinguished on the basis of the values of this property), when we execute the script, it was observed that TestComplete always fails to recognize either Object1 or Object2. When observed these objects in the NameMapping, we see that the property of object1 is automatically updated to " NativeClrobject.Name =Value2" by the TestComplete causing failure in recognizing "object1" and hence the test cases that are using "object1" fails saying that the object is not found. “NativeClrobject.Name” is taken just as an example, if we use any other property such as Name or WndCaption, these properties also change at the runtime. Please let me know what best can be done in this case. Thanks in advance. Regards, Harshad Kashikar Does TestComplete supports Mercurial Source Control System?Hi, I am using TestComplete v 7.52 and has setup Mercurial as a source control system. However I cannot find any SCC for Mercurial supported by TestComplete. Does TestComplete supports Mercurial Source Control System? If it does then can anyone post here the link for SCC that will work with TestComplete? Thanks in advance. Regards, Harshad KashikarRe: Description.TCLog file not foundThanks for your suggestions Gennadiy. Is the functionality of "restarting testcomplete and resume tests from a particular folder in a project" while running a test suite, by any chance, implemented in TC8? If not this can be taken as an improvement, because if we want to run test that may last for 2 or 3 days, we will not be able to use "Test Suite" feature of TestComplete and will have to rely upon CLI execution. Regards, HarshadRe: Description.TCLog file not foundThanks Gennadiy for your reply. I have tried running the tests (in parts) through testcomplete CLI - I also made sure to close/reopen the AUT/testcomplete. So it looks like I can run the tests in this way. However, by using CLI method, <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> <meta content="Word.Document" name="ProgId" /> <meta content="Microsoft Word 12" name="Generator" /> <meta content="Microsoft Word 12" name="Originator" /> &amp;amp;lt;BR /&amp;amp;gt; &amp;amp;lt;!--&amp;amp;lt;BR /&amp;amp;gt; /* Font Definitions */&amp;amp;lt;BR /&amp;amp;gt; @font-face&amp;amp;lt;BR /&amp;amp;gt; {font-family:"Cambria Math";&amp;amp;lt;BR /&amp;amp;gt; panose-1:2 4 5 3 5 4 6 3 2 4;&amp;amp;lt;BR /&amp;amp;gt; mso-font-charset:1;&amp;amp;lt;BR /&amp;amp;gt; mso-generic-font-family:roman;&amp;amp;lt;BR /&amp;amp;gt; mso-font-format:other;&amp;amp;lt;BR /&amp;amp;gt; mso-font-pitch:variable;&amp;amp;lt;BR /&amp;amp;gt; mso-font-signature:0 0 0 0 0 0;}&amp;amp;lt;BR /&amp;amp;gt;@font-face&amp;amp;lt;BR /&amp;amp;gt; {font-family:Calibri;&amp;amp;lt;BR /&amp;amp;gt; panose-1:2 15 5 2 2 2 4 3 2 4;&amp;amp;lt;BR /&amp;amp;gt; mso-font-charset:0;&amp;amp;lt;BR /&amp;amp;gt; mso-generic-font-family:swiss;&amp;amp;lt;BR /&amp;amp;gt; mso-font-pitch:variable;&amp;amp;lt;BR /&amp;amp;gt; mso-font-signature:-1610611985 1073750139 0 0 159 0;}&amp;amp;lt;BR /&amp;amp;gt; /* Style Definitions */&amp;amp;lt;BR /&amp;amp;gt; p.MsoNormal, li.MsoNormal, div.MsoNormal&amp;amp;lt;BR /&amp;amp;gt; {mso-style-unhide:no;&amp;amp;lt;BR /&amp;amp;gt; mso-style-qformat:yes;&amp;amp;lt;BR /&amp;amp;gt; mso-style-parent:"";&amp;amp;lt;BR /&amp;amp;gt; margin-top:0in;&amp;amp;lt;BR /&amp;amp;gt; margin-right:0in;&amp;amp;lt;BR /&amp;amp;gt; margin-bottom:10.0pt;&amp;amp;lt;BR /&amp;amp;gt; margin-left:0in;&amp;amp;lt;BR /&amp;amp;gt; line-height:115%;&amp;amp;lt;BR /&amp;amp;gt; mso-pagination:widow-orphan;&amp;amp;lt;BR /&amp;amp;gt; font-size:11.0pt;&amp;amp;lt;BR /&amp;amp;gt; font-family:"Calibri","sans-serif";&amp;amp;lt;BR /&amp;amp;gt; mso-ascii-font-family:Calibri;&amp;amp;lt;BR /&amp;amp;gt; mso-ascii-theme-font:minor-latin;&amp;amp;lt;BR /&amp;amp;gt; mso-fareast-font-family:Calibri;&amp;amp;lt;BR /&amp;amp;gt; mso-fareast-theme-font:minor-latin;&amp;amp;lt;BR /&amp;amp;gt; mso-hansi-font-family:Calibri;&amp;amp;lt;BR /&amp;amp;gt; mso-hansi-theme-font:minor-latin;&amp;amp;lt;BR /&amp;amp;gt; mso-bidi-font-family:"Times New Roman";&amp;amp;lt;BR /&amp;amp;gt; mso-bidi-theme-font:minor-bidi;}&amp;amp;lt;BR /&amp;amp;gt;.MsoChpDefault&amp;amp;lt;BR /&amp;amp;gt; {mso-style-type:export-only;&amp;amp;lt;BR /&amp;amp;gt; mso-default-props:yes;&amp;amp;lt;BR /&amp;amp;gt; mso-ascii-font-family:Calibri;&amp;amp;lt;BR /&amp;amp;gt; mso-ascii-theme-font:minor-latin;&amp;amp;lt;BR /&amp;amp;gt; mso-fareast-font-family:Calibri;&amp;amp;lt;BR /&amp;amp;gt; mso-fareast-theme-font:minor-latin;&amp;amp;lt;BR /&amp;amp;gt; mso-hansi-font-family:Calibri;&amp;amp;lt;BR /&amp;amp;gt; mso-hansi-theme-font:minor-latin;&amp;amp;lt;BR /&amp;amp;gt; mso-bidi-font-family:"Times New Roman";&amp;amp;lt;BR /&amp;amp;gt; mso-bidi-theme-font:minor-bidi;}&amp;amp;lt;BR /&amp;amp;gt;.MsoPapDefault&amp;amp;lt;BR /&amp;amp;gt; {mso-style-type:export-only;&amp;amp;lt;BR /&amp;amp;gt; margin-bottom:10.0pt;&amp;amp;lt;BR /&amp;amp;gt; line-height:115%;}&amp;amp;lt;BR /&amp;amp;gt;@page WordSection1&amp;amp;lt;BR /&amp;amp;gt; {size:8.5in 11.0in;&amp;amp;lt;BR /&amp;amp;gt; margin:1.0in 1.0in 1.0in 1.0in;&amp;amp;lt;BR /&amp;amp;gt; mso-header-margin:.5in;&amp;amp;lt;BR /&amp;amp;gt; mso-footer-margin:.5in;&amp;amp;lt;BR /&amp;amp;gt; mso-paper-source:0;}&amp;amp;lt;BR /&amp;amp;gt;div.WordSection1&amp;amp;lt;BR /&amp;amp;gt; {page:WordSection1;}&amp;amp;lt;BR /&amp;amp;gt;--&amp;amp;gt;&amp;amp;lt;BR /&amp;amp;gt; I am unable to use the ‘test suite creation’ feature of testcomplete- this feature allows to block the child tests if the parent test is failed, or I can select/deselect the tests as required etc. So rework will be needed to current scripts in this case to accommodate this change/logic- if testsuite needs to run using testcomplete CLI. Is there any way by which we can achieve this from testcomplete UI, that means - closing the testcomplete (exit) and reopening it by resuming the tests from where testcomplete was exited from the specified folder in the testsuite. Your inputs will greatly help me. Thanks in advance! Regards, Harshad