Contributions
Mapping FindChild object to Alias?
I have a popup window in a Desktop app that script recording creates an alias for automagically. However, playing the script back doesn't work because it fails to find the popup object on subsequent attempts and I'm not sure how to fix this yet. Being new to TC I then started fiddling with FindChild which finds exactly what I'm after. However, the aliased names e.g. pageLines.ListBox.ClickItemXY(...); no longer works as it can't find "ListBox" on my dialog. Is there a cunning way to map a FindChild object to an existing Alias so I can continue using the name mapping entries that TC10 has already created?3.3KViews0likes12CommentsRe: Issue with Firefox not responding when recording script
Ahh, thanks, dganov, that seems to have really helped. I have had Firefox stop responding once, but it's been much improved since I toggled that setting. As mentioned I'm doing desktop testing. Firefox just happens to be running with SmartBear web pages open for reference purposes.2.1KViews0likes0CommentsRe: Handling potential alert boxes via WaitWindow or aliases?
You're not wrong, it's not that long a delay, 2s maybe. Just that I can control it in one way via Sys.Process so things move along, hence I was wondering if I was tackling the 'problem' in the right way given the two approaches I've found thus far. I haven't quite figured out the name mapping system yet I must admit. I like the idea of an indicator message though.1.4KViews0likes1CommentHaving to kill TC10 via Task Manager all the time when closing it
I'm exploring TC10 at the moment, fiddling around with various things in my trial. I'm noticing that after I've been working with my project for a while, when I come to close TC it pops up the message about "Closing the project suite. Please Wait...", gets rid of everything from the Project Explorer, and then stops responding. I have to kill it via Task Manager every time it does this. If I start TC, open my project, close it, this doesn't occur. I normally close it via the [x] button in the top-right corner of the screen. I'm running TC10.60.3387.7 on Windows7/x64. Is this common or am I doing something funky?1.5KViews0likes6CommentsRe: Handling potential alert boxes via WaitWindow or aliases?
I now see I could use aqFile.Delete to remove the file so I never see the prompt, but I'm interested in how to handle alert message boxes in general. I'm just using the save/as operation as an example as that's where I've just solved it.1.4KViews0likes0CommentsHandling potential alert boxes via WaitWindow or aliases?
So I'm learning how to use TC10 and doing some experimentation with writing my own scripts to find out what I can do. I've come across an issue handling sort-of-unexpected (but not entirely unexpected!) dialog boxes appearing. By recording scripts I have acquired TC script code that does the job but I wanted to know if I was doing this right. I'm testing a Windows Desktop app and my example scenario is a File/SaveAs operation. If the save as filename already exists you get a prompt asking if you want to overwrite it. So the first run the save-as filename won't exist and hence no prompt will appear, but might thereafter. So I want to handle the prompt dialog appearing or not for a robust test. I can test for this alert thus and press Yes to confirm the overwrite: if (myApp.dlgConfirmSaveAs.Exists) myApp.dlgConfirmSaveAs.Confirm_Save_As.CtrlNotifySink.btnYes.ClickButton(); But this results in a noticable delay while the tell-tale indicator says it's waiting a few seconds for dlgConfirmSaveAs. I have found that I can also do this: if (Sys.Process("MyApp").WaitWindow("#32770", "Confirm Save As", 1, 500).Exists) myApp.dlgConfirmSaveAs.Confirm_Save_As.CtrlNotifySink.btnYes.ClickButton(); I don't really know where this "dlgConfirmSaveAs" came from or whether I can use that alias/namemapping (?) more directly than going via Sys.Process and using WaitWindow. As mentioned I'm exploring options, learning as I go, and wondering about better techniques.1.4KViews0likes4Comments