exdunepilot
Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Re: Network Suite Replacement
Thank-you Julia. Re: "But each process can trigger the test on a remote machine." Parallel.RunTests( tests ) does not return a list of processes (doesn't return anything). So how do I trigger the remote tests? And where do I intialize the IP, User, Pwd information in order to connect to the remote machine? Thanks Again.1KViews1like1CommentUnable to open TestComplete 14.74
We have a "special" install executable from SmartBear. It installs on several boxes, both Win 7 & 10, no issue. However, on one Win10 box when trying to open we get an error dialog: "A referral was returned by the server." We also noticed this same error occurred near the end of the install (we've tried numerous uninstall/install sequences). We clicked "OK" on the dialog box and the install appeared to continue w/o issue. Then trying to open, the error is always thrown.594Views0likes2CommentsRe: [Poll] Do we like to preserve the Synchronization Point functionality of TestComplete?
We absolutely would like to retain the capability of Network Suite & synch points. Parallel Environments with Selenium Grid only partially replaces. However, we need the capabiity for desktop apps. Why deprecate Network Suite in the first place?1.9KViews0likes0CommentsNetwork Suite Replacement
I understand the recommendation to move to CI/CD build tool for the distributed processing use case. However, another use case is to work with multiple environments/remote computers. For example, executing a test step on one computer and verifying the correct behavior on another app located on another computer (both with TC or TE installed). The new Parallel Environment is only web-based and Selenium grid required. We need remote/multiple functionality for desktop apps. What is the suggested workaround for that use case? TIA.1.1KViews3likes5CommentsRe: Does SessionCreator have a similar capability for ExportLogToXML
Thanks Justin for the reply. In our situation, we export each test individually as it completes (700+). When using "html" as the log format (Log.SaveResultsAs) along with launching TC with the /exportLogToXMLAlso flag (either shortcut or in command line) each test will have a root.xml file generated along with various xml & html. Unfortunately, SessionCreator does not have the /exportLogToXMLAlso flag so we're stuck. We would have to re-write our webapp if SessionCreator doesn't support or I suppose call SessionCreator RunTest 700+ times!711Views0likes0CommentsDoes SessionCreator have a similar capability for ExportLogToXML
We use command line to launch our tests with the /ExportLogToXML flag. But recently discovered SessionCreator may be a better fit for our CI Pipeline. Documentation shows exporting test results in XML is not supported by SessionCreator. If that is true, are there any other recommendations? We need the XML format as we parse data in order to publish to an internal webapp Dashboard. Thx!749Views0likes3CommentsTestComplete 14.0 Crash - References aqDbgHelp.dll
On my Windows 10 desktop, TC 14.0 appears to run fine, including Object Spy. However, we also use Windows 10 VMs and there, executing tests is so slow it is mostly unusable. I end up stopping execution or it has crashed a handful of times over the last few days. Trying to use Object Spy while in a "paused" state seems to make things even worse. It may take 10 minutes for the red outline highlighter to appear, if at all. Today, I finally paid attention to the error: "TestComplete has encountered an error in module unloaded aqDbgHelp.dll and needs to close. Also, I reinstalled TC 14.0. When trying at first the uninstaller said a TC process was open. However, no such process existed (at least with TestComplete in the name). I restarted the VM and then was able to continue the reinstall. It was like a ghost process reference lingered. Anyway, the end result was no help.780Views0likes1CommentRe: Python Error Handling Not Executing Finally Block - TestComplete 14.0
Yes, I have read your replies. Thank-you for quick responses. 1) All 3 settings in Playback Error handling are "Continue running" 2) All settings for tests in "test items" "on error" are "Use project's 'On Error' property" [so that I can set groups globally as needed]. I've also tried the other settings to check behavior. It appears that Python's try/except/finally overrides all TC settings & worse, masks other exceptions/call stack. At least that's the behavior I see. Take out the try/except/finally block and everything runs as in previous TC versions.2.8KViews0likes2CommentsRe: Python Error Handling Not Executing Finally Block - TestComplete 14.0
More info: * All settings within TC appear correct * I no longer get a full stack trace in TC 14.0 "Script Test Log" only the error caught in the "except" statement (12.6 did not have this issue) * When I remove the try/except/finally I get a full stack trace and more exact error message (which is clickable to the code). The problem of course, is that I need the finally block. * It seems to me TC 14.0 is not correctly handling the Python try/except/finally blocks (again, no issues at all with 12.6)2.9KViews0likes4CommentsRe: Python Error Handling Not Executing Finally Block - TestComplete 14.0
Yes, I believe you are correct. However, the e had no problems converting in 12.6 (or older versions for that matter). Something seems to have changed in debugging. I'm noticing more cryptic debug messages and missing call stack items overall. May need to rollback to 12.6. I'll post more when I can be more exact!2.8KViews0likes6Comments