Hi,

I'm having an issue with verifying a button if it's disabled or not in a web app. I'm using the Verification - Enabled test step but Test Studio keeps returning an error saying the button is enabled even though it's already disabled/unclickable in the web. Can anyone from the Telerik Team check this?

Please see:

Disabled button - https://www.screencast.com/t/fTK7KoDw 

Error from Test Studio - https://www.screencast.com/t/aU2NAtane2a7

 

Thanks,
Roldan

Issue :

Unable to locate elements in geo location.

Scenarios :

• We have  a pre placed Device on the map  that needs to be clicked on irrespective of the location.
• Telerik identified the elements for the first time when we click, but when the location changes of the devices does not gets identified by Telerik.

Additional Informations:

Application is built with WPF.

 

I have 2 login test that are identical, the difference being the credentials used (internal vs external user). I will eventually data drive but for now I am hardcoding the credentials. The problem I am facing is when I update the credentials for one test, the credentials for the other gets updated as well. How do I make my updates applicable to just one test?

I am a Progress employee, in ADP:OpenEdge. I am using the API test studio to create some load tests. I need a license to keep operating. My trial is just about up.

I have a scenario where I need to verify data based on timezone selected. For eg:

1) If the timezoneId: 'Europe/Athens' then show Label "A"

2) If the timezoneId: 'Europe/London' then show Label "B"

So let me know how I can change timezoneid from Test Studio itself to verify correct label.

Hi! My team and I are testing our interface in Test Studio through execution engine in the command prompt . Currently, we have a question and we wanted to know if there's a way to change the test executable through the command line. 
We wanted to change some existing parameters in our interface. For example, our_program.exe -testmode
It would be very useful for us if we could do something like this.
We are also having some issues with controls switching places frequently. Suddenly, our test script breaks and the script begins to recognize other controls. Is there an update that fixes this?
Thank you!

Side panel disappearing while recording the scripts.

 

 

We are facing some issues, some of them are: in our interface, there is a DataGrid with multiple rows. When this DataGrid passes a certain number "x" of rows (we haven't figured out the number yet), the TestStudio takes a long time to become "ready to record" and frequently identifies the wrong control. Another issue: Telerik recognizes controls that do not match the parameters inserted in the script as correct. For example, a "Quantity" field recognized in a "X" field as correct.

What is the criteria for the fields? What could be the reason for this failure to be recorded as correct in the script?

 

Thanks!

private void SearchText(string itemText)
{
m_RadComboBox.Text = itemText;
m_OwnerBrowser.Actions.InvokeScript($"(function() {{ $telerik.$(\"#{m_RadComboBox.ID}\").trigger(\"keyup\") }})()");
WaitForDropDownWithText(itemText);
m_RadComboBox.Refresh();
}

We use this code to trigger keyup event after setting the "Text" field of a RadComboBox and it does not seem to work with Google Chrome.

We are using version 2022.3.1201.2

When we type in the RadComboBox the list is filtered as expected, the searched item is found and we get the exception below:

Is there a way in a coded step to accomplish the ELSE clause below?

LOOP (10) Times

IF element not present

Refresh to see if element becomes present

ELSE

Coded step to set for iteration to max so no more loops occur (or break out through other means without erroring)

Is there a way with a coded step to accomplish the ELSE clause above? I would like to fast-forward the LOOP iteration to the end by overriding the current iteration value with 10 once the element exists? Because of the required refresh, I can't just wait for it to exist.

I have workable solutions with both LOOP and WHILE, but both have drawbacks. The FOR doesn't require coded steps (only a simple coded step if the above ELSE is possible) but fills the log with iterations that don't do anything. The WHILE stops once my condition is met and doesn't do the excessive logging but requires far more complicated coded steps. This approach would be hard for me to teach to our test writers who, for the most part, are not code developers.

Thank you.