The code that is below is something that I quite frequently have to use in order to export data from my application and handle the overwrite box if it pops up. My issue is, I have to copy and paste this in every single new test that I do and make sure I change all the right values. What I would like to do is put this in a 'library' file so I can just access a single function call in each test that will handle all of this, instead of copying and changing ALL of this text every single time. This is in an attempt to make my project a little smaller, and make it easier to maintain and create.
However. The manager class, and call to the element to open the dialog handler are getting in my way to moving this into a separate class file. Does anybody know of a way I might be able to accomplish this?
GenericDialog genDialog = new GenericDialog(Manager.ActiveApplication, "Save As", false, 6);
SaveAsDialog saveDlg = SaveAsDialog.CreateSaveAsDialog(Manager.ActiveApplication, DialogButton.SAVE, queryFilePath);
Manager.DialogMonitor.AddDialog(saveDlg);
Manager.DialogMonitor.AddDialog(genDialog);
Manager.DialogMonitor.Start();
// Wait for '1000' msec.
// Handle the overwrite box on save.
Applications.dTIMSexe.dTIMS_V9_For_Windows.ExportAllTextblock.User.Click(ArtOfTest.WebAii.Core.MouseClickType.LeftClick, 23, 19, ArtOfTest.Common.OffsetReference.TopLeftCorner, ArtOfTest.Common.ActionPointUnitType.Percentage, ((System.Windows.Forms.Keys)(0)));
saveDlg.WaitUntilHandled(60000);
Manager.DialogMonitor.Stop();
Manager.DialogMonitor.RemoveDialogs(saveDlg, genDialog);
Hello! Quick question regarding how data driven test structure works.
Let's pretend I have test A which logs into a website. Test B will now now use test A using 'test as a step' to get to the webpage and do additional things on the page.
Now let's say I want to want to use different accounts for test A to log into the website so test A is now data driven. However, the content on the website changes for each different account so if I turn test B data driven as well, I need to verify certain elements that correspond to the account that was used to log in.
If I follow this workflow however, and use data driven test A as a 'test step' inside test B, test A will run through all of it's data driven iterations before running anything in test B.
I want each the data for test A and B to be executed in tandem so the flow becomes:
log into account 1, verify on the website data belonging to account 1
log into account 2, verify on the website data belonging to account 1
How it currently works however, given my test flow, is:
log into account 1
log into account 2
verify on the website data belonging to account 1,
verify on the website data belonging to account 1
..which is not what I want. The only alternative I can think of is not using 'test as a step' to bypass the way the data driven logic is currently behaving. If there is any other way to switch up the order of how data driven tests work, please let me know, thanks!
I am trying to click "Yes" in an IE Security Warning Modal. My test passes, but it is not clicking the "Yes" button and closing the modal. I have spent far too much time on this. What am I missing?
GenericDialog SecurityWarningDialog = new GenericDialog(browser, "Security Warning", "Yes", true); // Click on the Yes button manager.DialogMonitor.AddDialog(SecurityWarningDialog);
manager.DialogMonitor.Start();
//Click the link that launches the security dialog
ClickLink();
SecurityWarningDialog.WaitUntilHandled(60000);
manager.DialogMonitor.Stop();

Hi Telerik, here's the scenario:
1. Click a button on the main window to open a new window called xWindow. WaitForWindow("xWindow Caption", 10000) works just fine and returns xWindow. Close xWindow by clicking a button on it plus checking: xWindow.Window.WaitForVisibility(false, 10000) and xWindow.Window.exists is false.
2. Click that button again to open xWindow the second time. WaitForWindow("xWindow Caption", 10000) fails and throws a TimeoutException. The funny thing is that the exception lists the current existing windows including "xWindow Caption".
Please have a look at my situation.
Thank you,
URL: https://classiccars-test.com/listings/find/all-years/ford/mustang
Using Firefox browser. This problem does not exist in
Chrome.
I’m using “Highlight Element” and hovering over certain
elements it appears Test Studio is “off by one” meaning it THINKS I’m hovering
over the previous element.
In the first screenshot it thinks I’m on “(CC-85973)”
In the second screenshot I moved down and picked up “1966
Ford Mustang”.
The DOM in this part of the page follows.
See attachment for screenshots.
This seems wrong. Can you shed more light on it?
Hi All.
Me see demo item and test sample but not auto close other item click.
plz help me in code.
thank you.
Hi,
Wondering if there are any plans for supporting Angular2?
Cheers,
T.
I have a control that looks like this and I could not test this using telerik testing framework.
<select id="xxx" multiple="multiple" kendo-multi-select="vm.xxx" style="width: 100%;"
k-data-source="vm.xxxDS"
k-data-text-field="::'Text'"
k-data-value-field="::'xxxID'"
k-highlight-first="::false"
k-ng-model="vm.xxxId"
k-on-change="vm.xxxChange(kendoEvent)"
k-value-primitive="::true"></select>
AFAIK there is no translator for Kendo UI multi select. Any example you have will be appreciated.
The approach that we have taken is to use the batch script to start the Telerik test scripts execution (ArtOfTest.Runner.exe) and then check the out through a custom C# console program that checks the output for execution status (Pass/Fail).
When we are executing the Telerik batch file without using Hudson the test script shows successful execution and simultaneously the C# code picks the same status. But when we are trying to execute the same through Hudson the test script executes but shows Fail status.
One thing that we did notice was that in the non-Hudson execution the Runner simulates the test script by opening the browser but in the Hudson environment the browser simulation is not executed by the Hudson environment as it is executing it as a background process. This might be a potential cause of the issue.
