SlickRickFrequent ContributorJoined 2 years ago89 Posts24 LikesLikes received7 SolutionsView All Badges
ContributionsMost RecentMost LikesSolutionsRe: Silent install of Testexecute with credentials Oh, that seems like a quite interesting option. I will test it and keep you posted. Meanwhile ill consider this a solution. Thanks! Silent install of Testexecute with credentials So i have my VM hosting my agents and testexecute which is running my automated UI tests. Right now i use a script to install Testexecute using -SilentInstall -SLM. However i am still required to log to the VM after the install to manually enter the credentials of my account in order to use TE in my tests. This is rather inconvenient since the way my VM are structure, i could rollback to a checkpoint previous to the TE installation to perform certain maintenance on the VM and then reinstall TE. So i was hoping if there was a way to silently install TE and provide the credentials to use? Thank you. SolvedRe: Failing Tests since Feb 17 Yes this is awful, it happens so often, to the point that im scared of updating anything. In that case since im using classical pipeline, im being forced to use their updates of the testadapter. If only they would release the versions so that im offered a choice so that i can decide to use prior version. This comes at the worst possible time as we are currently in a release cycle and all our teams are monitoring our builds which now all fails... Re: Failing Tests since Feb 17 Well initially i thought the issue was with TestExecute, but thinking about it i highly think it is the TestAdapter since my builds were working find one day and suddenly all failing. Will open a case as mentionned. Failing Tests since Feb 17 Well im not sure how to really put it properly, but somehow since this Monday all my VM and tests are failing randomly with either a : Exception occurred. (Exception from HRESULT: 0x80020009 (DISP_E_EXCEPTION)) OR Value does not fall within the expected range. All the tests were behaving properly the day before. I had version 15.72.60 installed, but before that date and it seemed to be working correctly. What I tried so far without any luck: Rebooting my machines Loging Off/On of the TE accounts Reinstalling TE with the same version Reinstalling TE 15.71.4 (same problem) Running the test manually with testcomplete doesnt seem to be having this issue. I've seen other report of this issue which seems to say that it is an issue with V15.72.60 but if this was the case i would expect that rolling back would fix the issue. Any help appreciated on how to resolve this. TestExecute - Long pause between test runs Hi all, I have recently did a maintenance update on many of my UI test machines (installing windows updates, Install latest TE and TC version) and suddenly all my machines seems to be a lot slower at running my tests. For instance tests that used to run for 30min would now take more than 1h30 to run. What I notice while monitoring the VM is that once a test is launched, the test is done quickly, but when moving on to the other test there seems to be a pause of 1min before the other test is actually trigger. I am currently investigating things like anti-virus (but which i need to wait for IT intervention), TE version etc but was wondering if anyone ever experienced this and may be able to provide guidance/ideas of what could be interfering with TE. Thank you. SolvedRe: OnLogError EventHandler Not working for app crash Hi Scot, Sadly i already tried the try, catch, finally which was my first attempt at handling this case. The issue is that there is no real thrown errors. Just TestComplete not likely that the app suddenly got killed. After further investigation, in our code we are closing using App.Exit but for some reason from time to time TC seems to detect it as a crash. Will continue to investigate. Also in the doc it is explicitly mentioned (not sure how i skipped that) that this event wont be handled: OnLogError Event | TestComplete Documentation So i guess ill have to result to other alternative... Ctrl j is indeed a cool tip which i was not aware of! Re: OnLogError EventHandler Not working for app crash Hi all, Indeed I agree with all of you. However in that case we do want to kill the application. I cannot really do in the details, but this is a scenario where the application should not run and may be compromised. This is what my UI test is supposed to be testing and therefore having that message is actually what we want =D. FYI, im in contact with smartbear support to see if this can be achieved. OnLogError EventHandler Not working for app crash I already know that my question will look odd to many but i have a test where i want to ensure that for a given condition my application would get closed if the user doesn't have specific authorizations. Basically ill be killing my application in that condition and sometimes testcomplete will detect that the application crashed and therefore give me a "The XXX.exe process crashed." log error. So i though that for that particular test i would simply add a OnLogError handler and verify this message and for that particular test simply put a warning instead. This is my Handler: function TestStopEventControl_OnLogError(Sender, LogParams) { Log.Message("DEBUG: Inside OnLogError with message: '" + LogParams.MessageText + "' IgnoreVar:" + Project.Variables.ignoreAppCrashError); // Check if the error message matches the specific crash string. if (LogParams.MessageText == "The XXX.exe process crashed." && Project.Variables.ignoreAppCrashError) { // Log a warning to indicate the error was suppressed. Log.Warning(LogParams.MessageText); // Suppress the error log by marking it as locked. LogParams.Locked = true; } } For all my log errors this code seems to be run since i see my DEBUG message. However it doesn't work for the LogError im am trying to ignore.... And like i say, for any other error it seems to go inside the handler: Im guessing those are "native" error and cannot be changed, but in my case it would have been necessary... Any ideas? Re: Web browser page URL not loading Hi again, once again thank you for your help. Im away right now so i cannot test your code but i did try something very similar but without success. I will give it a try when i come back. For the moment i was doing a work around which was to verify that Sys.Browser('edge').CommandLine contained my url since all i cared about was to ensure that my application is opening the browser with the proper URL. This is not perfect since i would also want to ensure that it doesnt open on a dead link so i will definitely try to have it work and ill keep you posted on the results. Just FYI, i did try to switch to my machines to use Chrome instead of edge with the same result.