ContributionsMost RecentMost LikesSolutionsRe: Test Execution Summary is null We raised a ticket and had to roll back to an older version and as tsand mentioned is related to the dark theme. Rolling back is a major hassle as it means uninstalling as installing an older version isnt allowed. That means backing up settings, templates, dockings etc. Not everything gets backed up which is annoying. Re: File System Testing Another way of opening files from the browser is using the file:// url eg file://C:/Windows/ . You can click-navigate the directory and file structure, however to run tests on the opened file you may need the desktop module. Most browsers can open text, CSV, PDFs, Excel so it may not be needed depending on the file. Re: Test Execution Summary is null Same here. Do you guys actually test stuff before releasing. Ironic a QA product is having so many issues. Was OK until about 3 years ago but now its becoming too unstable with critical issues and we are looking at other products. Also noted this issue a few days old and has not been fixed. I have logged a ticket but thats another 2-3 days of delay. Its so frequent it is impacting our testing operations and new test coverage. Re: How to call/get a keyword test ID in Testcomplete? We have a similar requirement in our tests with validations on 1 or more delayed events. We do it similar to the way AlexKaras said and run a number of creation tests, run some other tests then at the end of the tests run the corresponding validations. TestComplete unfortunately does not have table dynamic variables otherwise you'd be able to maintain a table to maintain the states of the different tests. For another system we have a two delays of 10 minutes which we had reduced to 5. Even then its inefficient. Another way we do it is to create a bunch of things and update spreadsheet with their unique IDs, validation status, date-time etc. Then when the test runs it first checks the spreadsheet for past untested items then validates them updating the spreadsheet logging errors in the testlog. At the end it creates more items for future tests that will run next time around. We have 2 stages of delays so that process run again to see if the 1st stage has passed, test the 2nd stage and update the spreadsheet. For DevOps tests we can email the spreadsheet if needed. Re: Azure pipeline - All test pass by timeout occurs The only way I can reproduce that is by canceling the job myself. Is there a someone else who could have cancelled it? How was build job triggered a schedule, CI/CD code changes? I remember seeing something similar when a time limit was added to a build job, or a certain number of failures. Delaying/queueing Checkpoints We have an application where some of the test results are only available after a scheduled process runs every 20 minutes. If we have to run lots of tests its not feasible to run 1-by-1 sequentially so we want to run the the tests and store expected results for later. Also the tests run in DevOps so deploymenents reset all TestComplete variables to defaults. Has anyone else done this? We are thinking of using Excel to store test expected unique data which is then used to by the test case later to validate the results. Tests can be run multiple times and the list will grow. Once the test result is established the test is closed but nothing is deleted. Any ideas are welcome. Thanks Ability to run tests from logs - Could be used to quickly re-run all failed tests This would allow the running of tests from a log summary page. If the "Failed" tab is clicked all test could be selected and re-run. This would be very handy for when a single issue has caused many tests to fail - eg authentication time-outs in our case. Testing a Citrix application via Citrix Viewer and the IQ module We need to test a Citrix hosted application and are havving trouble with the ClickNextTo function in the Citrix Viewer: Laptop running TestComplete: ---> Citrix Viewer -----> Server: Citrix AUT Originally a keyword test was used uising the OCR Action ClickNextTo but there is problem with a long delay with the message "Waiting until the window is activated. The Click action works fine. function EnterUserNameAndPassword() { // Recognize the text of the tested application's main window var wnd = Aliases.Citrix_Viewer.Form.WinForm.Panel.ATL.Server.wMFService.CtxICADisp; var obj = OCR.Recognize(wnd); // Find the "Customer Name" label var t = obj.BlockByText("user"); // Enter "John Smith" in the text box to the right of the found label t.ClickNextTo(toRight, 25); t.SendKeys("John Smith", toRight, 25); t.Click(); var t = obj.BlockByText("Password"); t.ClickNextTo(toRight, 25); t.SendKeys("pass", toRight, 25); t.Click(); } With the above setup TC has trouble with the ClickNextTo and SendKeys. Click is OK. The identical test was then re-run as follows over Remote Desktop remoting onto a VM running Citrix Viewer: Laptop running TestComplete: ---> RDP - -----> VM running Citrix Viewer -----> Server: Citrix AUT The RDP window was mapped and the same code used which worked fine even though it is looking at the same thing. As a test the AUT was replaced Notepad was used displaying the required text and this worked. It appears TestComplete is not able to use the CitrixViewer with certain OCR actions (SendKeys) and ClickNextTo. Clicking and SendKeys is fine. RDP access is fine. Has anyone had the same issue? Re: Image comparison for scalable elements I did it a few years ago with checking and clicking things on maps in .NET/desktop. I set the size of the screen to known zoom levels before doing a comparisons. Also having reference markers of known size and reducing the zoom in steps until found using a find-image function. Once found panning the image to make it central then using that as reference for other elements being tested, eg map icons etc. It was extremely slow! Re: Resizing the desktop when connected remotely via RDP to Windows Server 2016 Hi Alex, Thanks for the solution which is the best as it changes the console default resolution in the registry. I will give it a try. As it is I used this which runs first before any applications are opened: getActiveXObject("WScript.Shell").Run("powershell -command Set-DisplayResolution -Width 1920 -Height 1080 -Force"); Jonathan