MulgraveTester
Frequent Contributor
Joined 14 years ago
User Profile
User Widgets
Contributions
Feature request - Black box screen recording
When trawling through long logs to find out what lead to an error I often cannot replicate the fault, despite logging every step. Sometimes a screen grab is not enough because an error dialog masks the form content that produced it. What would be useful is a screen recorder that runs throughout the test. This would normally generate a huge file, so like a dash cam black box in a car crash, it would be useful if TestComplete could store x seconds leading up to the warning/error as well as y seconds after the event to show how the robots attempt to recover from the fault was met by the software under test.912Views1like1CommentRe: Why does "Stopping..." take so long?
Hi Marsha, I didn't see how that link was relevant. I had to kill TestComplete in the Task manager after it hadn't stopped after 45 minutes. I have my "Save log every" set to 2 minutes. So there should only ever be 2 minutes worth of log to process before stopping. The script crashed at 1:02:23 a.m. because the sys.Desktop.activeWindow was not identified. I stopped the code at 7:34:25 a.m. At 8:15 a.m. TestComplete was still "Stopping..." with no way to force it to stop other than kill TestComplete1.4KViews0likes1CommentHow to avoid "Can't find window..." when testing if sys.desktop.activewindow.exists?
Hi, Occasionally my code crashes when I test if sys.desktop.ActiveWindow.exists because "Cannot find the window with handle xxxxx". The line immediately before the condition is sys.Refresh so I would have to be extremely unlucky for my object to be destroyed in the milliseconds since the refresh but it keeps happening. Ho do I test this? Do I need to use isnull(sys.Desktop.ActiveWindow) instead?Solved1.4KViews0likes2CommentsWhy does "Stopping..." take so long?
During the day, when I run a test and it crashes I address the crash and the IDE reports "Stopping..." while it builds the log file. When I run a script over night and it crashes the IDE is obviously idle until I come in in the morning to halt execution. The "Stopping..." message can take 30 minutes or more to go away. What causes the delay during "Stopping..." and why is it proportional to the amount of time that the IDE has been idle after a crash?1.5KViews0likes4CommentsRe: Win a $100 gift card to share what you would like to see in TestComplete!
Add native support for PDF files without having to rely on java or dotnet plugins. Many desktop applications generate reports in the form of PDF documents and we need to test that the contents of those reports are correct. Additionally make the Java Bridge a programmable parameter so that it can programmatically be updated if a later version of java is detected.926Views1like0CommentsRe: Stripping data of pdf files - used to work, now has error "Object doesn't support this action"
So that my script doesn't fail every time Java updates and to remind me of what I have to do to fix it I have added this VBS code to test that the current Java Virtual Machine is referenced before I start working with it. function isCompatibleJava 'The Java Bridge is set in Tools\Options >> Engines\Java Bridge 'Since each Java update moves this file this reference needs to change to point to the current Java Virtual Machine. 'This parameter cannot be set programmatically so all we can do is test that the current Java is compatible with what we have set. 'Returns TRUE if compatible. isCompatibleJava = false on error resume next set someObj = JavaClasses.org_apache_pdfbox_pdmodel if err.number = 0 then isCompatibleJava = TRUE else log.Warning("Your Java install is incompatible with this script. In TestComplete open Tools\Options, navigate to Engines\Java Bridge and point it to your current Java virtual machine e.g. C:\Program Files\Java\jre1.8.0_141\bin\server\jvm.dll") end if on error goto 0 'turn off error handling end function4.1KViews2likes0CommentsJavaClasses - Object required
This VBS code reports Object required: 'JavaClasses'. sub testPDF fileName = "mypath\test.pdf" set PDFReport = JavaClasses.org_apache_pdfbox_pdmodel.PDDocument.load_3(fileName) End Sub I was reading PDF files successfully in TC11 (here) even after Java updates (here) I haven't run this test for a long while and now find that it is broken in TC 12. I updated the java bridge in Tools \ Options \ Engines \ Java Bridge to point to the current Java VM (C:\Program Files\Java\jre1.8.0_141\bin\server\jvm.dll) My Java Bridge in Tools \ Current project properties \ Java Bridge is still configured as before "..\pdfbox-app-1.8.12.jar", which I know was working before in TC11. Java Application Support (File \ Install Extensions \ Desktop \ Java Classes Support) is installed. Can anyone, who is actually reading PDF files in TC 12, please help shed light on this. Many thanks.Solved1.2KViews0likes1Comment