ContributionsMost RecentMost LikesSolutionsA way to check if the current Test Item test run have no warnings or errorsHi, Anyone here got a script that checks for the current KeywordTests if there's a Warning or Error on the KeywordTests's entire logs? For example., Test Script is Adding a record. Once the TestScript KeywordTest run reaches its end part, it will trigger the event "OnStopTest" and then it would generate the logs (just for that KeywordTest) and report thru API or something to a central server. Im planning to build up a web app and that a VBScript on TestComplete/TestExecute will API the current status of the test run and show if it was a pass, fail or warn. Re: Search and repalce a specific operation on all KeywordTestsHi Tanya. thank you for pointing that out. I tried to add the Class using the "Add From Screen", it uses the WndClass value and playing it gave me this error: Unable to find the object SetText("act"). See Additional Information for details. The object with the specified attributes does not exist. Possible causes of the error I removed that class and added it manually as "TXTextControl.TextControl" (which is the value of ClrFullClassName There's no error but TestComplete was not able to set the text on it. As I view it while in playback, it does nothing. The control is documented here: http://www.textcontrol.com/en_US/support/documentation/dotnet/n_textcontrol.htm It looks like a richtextbox and it is intended to be an HTML editor, more like a richtextbox but for HTML editing. It also wrapped inside (its parent object) an Infragistics Ultrapanel (if that matters) What can you advise?Search and repalce a specific operation on all KeywordTestsWe are just using the default TestComplete automatic namemapping during recording and so far we have no problems with it. Our application now has a newer branch, with a support for HTML formmatting on the same spot where the normal textcontrol is - buttom line, it's a new object. I have edited namemapping mapped object to do conditional mode, to support both the old textcontrol and the HTML capable textcontrol and I am happy that it works. However, the problem now is that most KeywordTests uses the operation SetText() and the newer object doesn't have SetText() but just set_text(). The old object supports both SetText() and set_text() - so it was a poor decision of not using set_text() - well we haven't known that till now. Is there a way to do a search and replace functionality for all KeywordTests in the project to change all instances of SetText() to set_text() ? SolvedRe: KeywordTest runs script routine that uses its variables if it existsHi Tanya, I've read that there's no way to get the KeywordTest variable without getting the name, and getting the name (as you said) can only be done when running via test items. I'd like to add a request that SmartBear consider adding a routine to get the current KeywordTest name regardless if it is via Test Items or via KeywordTest Editor. This is very useful in such, as creating variables on the fly inside the Keywordtest while on the KeywordTest editorRe: Compare KeywordTests on cloned project will show a difference on its NodeBitmaps headersContacting SmartBear Support gave me an answer that this is unexpected behavior and that this will be addressed in future versions of TestComplete. Tanya: this is Issue# M0118431, we would appreciate if you can get your developers fix this issue on next major release of TestComplete. Thanks.Re: Opening the project suite. Please wait.... (Becoming too long)Tanya, thank you for your response. Please send my big Thanks to Evgeny as well for the job well done. She responded to me in a direct support e-mail. These are the steps that worked for me (provided by SmartBear support) 1. Create a backup copy of your current project. 2. Open your project suite in TestComplete 9.31. 3. Double-click the NameMapping item in the Project Explorer panel. 4. Set the "Store Code Completion Information" option to "Do not store data for Code Completion" in the Name Mapping editor. Then, click Yes. 5. Set the "Store Code Completion Information" option to "Store brief data" in the Name Mapping editor. 6. Save the changes. Close TestComplete. Then, open it again and see whether it improves the situation. --- My result is from 7-8 minutes of load time, to less than a minute TestComplete's memory consumption came down from 1+GB to 300MB Also, my Namemapping file came down from 175MB to 2MB And so far no more freeze on playback. I've realized that this whole thing started when I mapped a part of the product under test which had a grid with 6000+rows and 20+ columns. I've asked from some information on Namemapping and why it did that and I was given http://support.smartbear.com/viewarticle/26988/ Just a small suggestion: to include the information regarding namemapping "store brief" stuff to the article "Automated Test Performance Tips" To SmartBear support. Thanks!Re: Opening the project suite. Please wait.... (Becoming too long)Hi Tanya, Updating to TestComplete 3.1 did not help. Opening our Project Suite still takes the same amount of time. Also, there are times where we (for example, Undo changes on NameMapping), the memory consumption of TestComplete.exe will go as high as 2GB. This is not the case for version 9.2 and we only have added ~100 keywordtests since then. Anything else we need to check?Re: Compare KeywordTests on cloned project will show a difference on its NodeBitmaps headersFrom original TestComplete project (STABLE) <NodeBitmaps> <Bitmap Name="Aliases.OurProduct1" Data="61717A69700000000100000036040000780173F235636100033320A901C40250CCC8A000640101541EC28190FFFFFF6718CAF8D1933F0CCBD77E679834EB2B434BEF1786CE895F193A80B87DC25786D6BE 2F0C751D5F18AA9A3F3394357C06B327CFFEC6B071C75F86878F7E31FCFCF193E1F3977F0CB56D5F1822523E3284257D60B0F278C760E28CC03E911F188A6B3F332C5DF39DE1F2B53F0CEF3EFC63F8FBF71FC3A7 E7D718FE7CFF000EBB6FDFFE31C4667E04EB4D2BFCC4D03BED2BC3E9F3BF18DE7FF88B356CDF5D5BCFF0FDED5D14B9CF9FFF81DD00B2BBBAF50B8A1C72FCBC3A339BE1ED8DAD58E55FBFF9CBE01BF501ECFEA7CF FF60A8797E7A26C3C37D4D18E2C8E63F79F687C1D6FB1DC3EC45DF50D4BD383B8FE1EA123F1431647DC8EC6B377F338403C3F3FB8F7F60F56FAFAC6638DDABCCF0FBFB47A2F483CC3A7AEA3730BC7F30BCBDBD9F E1781337C397E71789D60B73CB972F3F19CEF7C832BC383B9F64BD3033DEDDDEC9F0EF1FC41F30B1E14403000773C525" /> <Bitmap Name="Aliases.OurProduct1.FormNarrativeEditor1" Data="61717A697000000001000000360400007801A5534B4EC330107D483D004760C909B245628960C319D87006EEC19E151207E000EC90104242424815E5534129A54DF38FED7C98B16393A812156DA2F12463 BF9737CFCEEE81D783BE3C1AB729369BD8C0163DD1D5CC9B1733D658EF3EDAF3B04A1C1FEE68DCCDE539541298886690E1376430819C7F41F89F10B311C4F403F9F805D97B1FE9EB03E2A73BC4FD5B872FD208A7 FB3DBC5D5DE8CC1CFCDEAEF1B3980C717D76A2EBC9F3FD2F3E8BC11CAC83D729D2C159068647F863D2415A4807D7F3D100E9F0D1E1CB3C45D170687C3C373CE15467AE713087CEA48339D837EEBF14192C07CF17 4E87AFD7B775683CE9E05E1C5EE68E83E739D80B453AAC27B66E33FB6AF1552151B6386C2FAC43EF4DEC6B4FACAF766F1CBE2CD0E11029F593902711F91A2E70D8FDB5F8BA2A51351C95128D96E51C0E5FD319FE 1707F5437BD3C12FE53067447B42BEAAC85FC47738142AF587AFC461BFCF67609560FC7A7F6F8D1F5B1D3A8B" /> <Bitmap Name="Aliases.OurProduct1.MainForm" Data="61717A697000000001000000360400007801A5534B4EC330107D483D004760C909B245628960C319D87006EEC19E151207E000EC90104242424815E5534129A54DF38FED7C98B16393A812156DA2F12463 BF9737CFCEEE81D783BE3C1AB729369BD8C0163DD1D5CC9B1733D658EF3EDAF3B04A1C1FEE68DCCDE539541298886690E1376430819C7F41F89F10B311C4F403F9F805D97B1FE9EB03E2A73BC4FD5B872FD208A7 FB3DBC5D5DE8CC1CFCDEAEF1B3980C717D76A2EBC9F3FD2F3E8BC11CAC83D729D2C159068647F863D2415A4807D7F3D100E9F0D1E1CB3C45D170687C3C373CE15467AE713087CEA48339D837EEBF14192C07CF17 4E87AFD7B775683CE9E05E1C5EE68E83E739D80B453AAC27B66E33FB6AF1552151B6386C2FAC43EF4DEC6B4FACAF766F1CBE2CD0E11029F593902711F91A2E70D8FDB5F8BA2A51351C95128D96E51C0E5FD319FE 1707F5437BD3C12FE53067447B42BEAAC85FC47738142AF587AFC461BFCF67609560FC7A7F6F8D1F5B1D3A8B" /> </NodeBitmaps> To this (DEVEL TestCompelete project cloned from STABLE). There were no code changes, but line 2 swapped places with line 3 <NodeBitmaps> <Bitmap Name="Aliases.OurProduct1" Data="61717A69700000000100000036040000780173F235636100033320A901C40250CCC8A000640101541EC28190FFFFFF6718CAF8D1933F0CCBD77E679834EB2B434BEF1786CE895F193A80B87DC25786D6BE 2F0C751D5F18AA9A3F3394357C06B327CFFEC6B071C75F86878F7E31FCFCF193E1F3977F0CB56D5F1822523E3284257D60B0F278C760E28CC03E911F188A6B3F332C5DF39DE1F2B53F0CEF3EFC63F8FBF71FC3A7 E7D718FE7CFF000EBB6FDFFE31C4667E04EB4D2BFCC4D03BED2BC3E9F3BF18DE7FF88B356CDF5D5BCFF0FDED5D14B9CF9FFF81DD00B2BBBAF50B8A1C72FCBC3A339BE1ED8DAD58E55FBFF9CBE01BF501ECFEA7CF FF60A8797E7A26C3C37D4D18E2C8E63F79F687C1D6FB1DC3EC45DF50D4BD383B8FE1EA123F1431647DC8EC6B377F338403C3F3FB8F7F60F56FAFAC6638DDABCCF0FBFB47A2F483CC3A7AEA3730BC7F30BCBDBD9F E1781337C397E71789D60B73CB972F3F19CEF7C832BC383B9F64BD3033DEDDDEC9F0EF1FC41F30B1E14403000773C525" /> <Bitmap Name="Aliases.OurProduct1.MainForm" Data="61717A697000000001000000360400007801A5534B4EC330107D483D004760C909B245628960C319D87006EEC19E151207E000EC90104242424815E5534129A54DF38FED7C98B16393A812156DA2F12463 BF9737CFCEEE81D783BE3C1AB729369BD8C0163DD1D5CC9B1733D658EF3EDAF3B04A1C1FEE68DCCDE539541298886690E1376430819C7F41F89F10B311C4F403F9F805D97B1FE9EB03E2A73BC4FD5B872FD208A7 FB3DBC5D5DE8CC1CFCDEAEF1B3980C717D76A2EBC9F3FD2F3E8BC11CAC83D729D2C159068647F863D2415A4807D7F3D100E9F0D1E1CB3C45D170687C3C373CE15467AE713087CEA48339D837EEBF14192C07CF17 4E87AFD7B775683CE9E05E1C5EE68E83E739D80B453AAC27B66E33FB6AF1552151B6386C2FAC43EF4DEC6B4FACAF766F1CBE2CD0E11029F593902711F91A2E70D8FDB5F8BA2A51351C95128D96E51C0E5FD319FE 1707F5437BD3C12FE53067447B42BEAAC85FC47738142AF587AFC461BFCF67609560FC7A7F6F8D1F5B1D3A8B" /> <Bitmap Name="Aliases.OurProduct1.FormNarrativeEditor1" Data="61717A697000000001000000360400007801A5534B4EC330107D483D004760C909B245628960C319D87006EEC19E151207E000EC90104242424815E5534129A54DF38FED7C98B16393A812156DA2F12463 BF9737CFCEEE81D783BE3C1AB729369BD8C0163DD1D5CC9B1733D658EF3EDAF3B04A1C1FEE68DCCDE539541298886690E1376430819C7F41F89F10B311C4F403F9F805D97B1FE9EB03E2A73BC4FD5B872FD208A7 FB3DBC5D5DE8CC1CFCDEAEF1B3980C717D76A2EBC9F3FD2F3E8BC11CAC83D729D2C159068647F863D2415A4807D7F3D100E9F0D1E1CB3C45D170687C3C373CE15467AE713087CEA48339D837EEBF14192C07CF17 4E87AFD7B775683CE9E05E1C5EE68E83E739D80B453AAC27B66E33FB6AF1552151B6386C2FAC43EF4DEC6B4FACAF766F1CBE2CD0E11029F593902711F91A2E70D8FDB5F8BA2A51351C95128D96E51C0E5FD319FE 1707F5437BD3C12FE53067447B42BEAAC85FC47738142AF587AFC461BFCF67609560FC7A7F6F8D1F5B1D3A8B" /> </NodeBitmaps> Compare KeywordTests on cloned project will show a difference on its NodeBitmaps headersOur test script development processes requires us to make use of TestComplete's integration with TFS and the use of "Cloning" projects to maintain . In a nutshell, we have a TestComplete project that we maintain (called STABLE), and on a bi-weekly basis we clone STABLE and have another TestComplete project as DEVEL. We do all our test script development in DEVEL and the code reviewer will merge that "by hand" from DEVEL to STABLE (literally, copying the file from one folder to another and Add Existing Item). After that, DEVEL get's trashed and we clone again and the cycle happens. We are OK with this process. But what we've observed using Visual Studio's comparison of files (diff window) shows that for a bunch of KeywordTests the only difference is that an XML node of NodeBitmaps, gets swapped to another line. This does'nt make a lot of sense. Please see next post. Notice that "FormNarrativeEditor1" just moves from line 2 to line 3 and it swapped places with "MainForm", but really that would'nt make a difference. It's just that Visual Studio is thinking that this is a code change and we have to open each and every one of these files just to make sure that there was a legitimate change. Overall, I'd like to ask is, what and how will <NodeBitmaps> attribute change and how can we prevent this from ever changing? Again, not all of our test scripts changes during cloning. Is this something that got change by accidentally opening the KeywordTest? Running it?SolvedRe: Opening the project suite. Please wait.... (Becoming too long)We use TFS integrated in TestComplete and our workspaces have local copy of the entire TFS project folder to our local drive. When we use other tools on the same machine (such as Visual Studio) and get latest version - it is quick and new stuff are sync in a few seconds.