Contributions
release 15.59.7.7 cannot detect embeded chromium content
Tests started to fail on web related tests after upgrade to15.59.7.7. It cannot detect web or embeddedchromium contentalthough Testcomplete web module licence is connected. *Logout and login did not help. *Downgrade the testcomplete to 15.41.9.7,Left the Testexecute on15.59.7.7. * Testcomplete could detect web and embeded chromium content., tests run successful with testcomplete, but problem remain when running the same tests with test execute. * Downgrade the test execute alto to release 15.41.9.7, all worked back again. Note: did not touch project or any settings at any point and it was already working before the upgrade, so downgrading resolved.259Views0likes6CommentsRe: same kind of event handlers for different events
Your answer has reallyenlightened me and provided a basic idea of what I can or can't do with Test Complete. I really appreciate that. But that is really not a solution for me, but again thank you for your answer. Ps: There are still things that I could not understand about test complete event handlers. If Test Complete can add different unexpected windows handlers to different units, where each unit is a test case, which means each test case has its own individualunexpected windows handler. Basically, ifI run test unit 1 and get an unexpected window through this test case, I would expect only the handler in test unit 1 to be triggered. But in reality, all other unexpected window handlers are being triggered. There is no point in triggering the unexpected window handlers in test units 2 and 3 and so on... If one "unexpected window" triggers all the event handlers, what is the point of having more than one event handler? And why is test complete capable of adding several event handlers to several units. Even with different names. That is what I observed. Next week I will try to examine more if I have a chance. cheers... Regards Mustafa915Views0likes2Commentssame kind of event handlers for different events
Hi, Here is the imaginary scenario that resembles the issue that I have in a simpler explanation. 1) I created a desktop test, it has Test1, Test2 and Test3. Each test case handles different tasks. 2) When there is an unexpected window that pops up at any of these tests, I want to be informed by email. So I created 3 different event handlers asEventControl_Test1,EventControl_Test2 andEventControl_Test3. 3) Then for each event handler, I added the general events: OnUnexpectedWindow. Until here, you can see the explanation in picture 1. 4) After adding the general events: OnUnexpectedWindow, respective test scripts had the eventHandler functions at the bottom of the test scripts. As a result, for each separate test case, I created a separate event handler (EventControl_Test1_OnUnexpectedWindow,EventControl_Test2_OnUnexpectedWindow, EventControl_Test3_OnUnexpectedWindow), which is expected to be triggered in case of having unexpected windows. I added an email sending function into each eventHandler function. You can see the explanation in Picture 2. This picture is for test1 but, it is also the same for test2 and test3, only handlers and test cases are different. Expected result: When I run test1 and when I encounter an unexpected window, I would expect "EventControl_Test1" to be triggered and the respective email to be sent. Actual Result: When I run test 1 and encounter an unexpected window, all of theEventControl_OnUnexpectedWindow handlers are triggered. I mean even if I have an unexpected window while running test1, unexpected window event handlers of test2 and test3 are also triggered. The stranger part is, this happens even when I do only run test1, and get an unexpected window, event handlers of test2 and test3 are all triggered, then send emails. This can be seen in Picture 3. Is this a bug, or should I make another assignment? Or is the way I try to implement it wrong? Picture1: Picture 2 Picture 3Solved1KViews0likes7CommentsRe: onerror save the screenshot of desktop
Thank you for your answer. Yes, I tried to use it. After step 3, the procedure to implement the handler to the script is really not clear. 1) Add an Event Control to Your Project 2) Add Needed Events to the Event Control 3) Create an Event Handler Should "function EventControl1_OnLogError" be used as the main function to call other test case routines? Like a big try block? function EventControl1_OnLogError(Sender, LogParams) { testCase1(); testCase2(); . . . testCase10(); } I cannot find any example or demonstration of how to implement an event handler to a script. Actually, that is a general problem which I really don't like with test complete desktop test module, lack of examples. I do not understand why there is no repository showing how to use a specific function. Please correct me if I am wrong.719Views0likes2Commentsonerror save the screenshot of desktop
Hi, I am automating a desktop app by using JavaScript. I want to take the screenshot and save it on the computer whenever the script encounters an error, warning or problem. Currently, testcomplete saves the last screen with error on its script logs, but my aim is to save the error screen on the computer. I know there is a method as shown below, but it is useless for me because I have to call it when the error occurs and I do not know when the error occurs. Sys.Desktop.Picture().SaveToFile("D:\\screenshot") So in summary, let's say I have 400 lines of code, whenever an error occurs call the above method to save the screen on the computer. I tried "try and catch" but it doesn't help, as the error we have is not a code error. There is a property on the "Execution Plan" test execution window called "on error", but it doesn't have the possibility to call another function. It would be great something like, when function encounters an error then call a user-defined function, then I would write a function to take screenshots. Maybe you would say put assertions like if (!object.exists) { takeScreenshot } but the errors that I have database related and I cannot figure to when to see and what to see. So I need something, whenever I have an error, that causes the script to stop, take the screenshot and save it on computer. This is what built-in script logs do, I just want the same thing in my hands, then I can email the error screens to my colleagues externally. function testDesktopApp() { line1.... line 2... . . . line 400 } With regards MustafaSolved794Views0likes4Comments