CaptureBrowser() functionality does not work as expected with Firefox browser on Windows 10 version 2004. The captured image shows only the browser frame and and white contend of the browser.
A customer application sets window.top to null or undefined at some point and thus the test execution fails to verify the state of a checkbox with the following error:Executing step 6 "Verify checked value is 'True' on 'PhysiciansCensusTypeICheckBox'"...
Using the Telerik.ApiTesting.Runner.exe to execute API tests cannot output results in junitstep format. It throws an error if using the -f junitstep option when running tests or test suite:[ERROR] Not supported test results format
I have a WPF test and converted one of the steps to code. My project is configured to use Visual Basic as coding language and the error is on line 46 of the Pages.g.vb file - BC30201: Expression expected.
There are no issues if the project is configured to use C#.
"Active browser is now null", caused from disposed Manager instance, fails randomly some of the tests. The behavior is not consistent and can't be reliably reproduced, where the same tests fail.
The version I am using is not listed below: 2020.1.403.0
I am noticing an inconsistency when using the Replace Element feature i.e. the attributes selected are not respecting the priority set in the Settings - Find Logic (Html) screen.
Please refer to screenshots attached.
Trying to open a RadComboBox with
var csBox = Window.Find.ByName<RadComboBox>(ComboBox);
Observing the automation shows we are waiting no time for dropdown to open and I am getting exceptions claiming there are no items in the list.
The cause is related to the fact that the public void WaitDropDownAnimation(int millis) method of Telerik.WebAii.Controls.Xaml.Wpf.RadComboBox is not working as expected.
Workaround: You can use Window.Find.ByType<RadComboBoxItem>().Wait.ForNoMotion(milliseconds); before selecting the item from the dropdown.
If you have opened the web test and execute a performance test list, which includes this test, the performance details will not be updated automatically in the Performance tab.
You need to reopen the web test and go to the Performance tab to view the updated details.
When using Test Studio for API standalone, the coded step is deleted after reopening API project.
Steps to reproduce:
1. Open Test Studio for API standalone and add a coded step (C#)
2. Save project then close it
3. Reopen the project in Test Studio for API standalone and the coded step is no longer there and the Test Case will now show a VB# instead of C#
4. Recreate the coded step and the method will show "A class with this name is not found in the test's code-behind file"
6. Click on open Code-Behind and the project will crash.
Note: API Test as Step in Test Studio works as expected and reopening the API project within Test Studio doesn't delete the coded step. However, we create a “common API project” that is shared with the QA team then imported into new test studio project. We have a workaround but not ideal which is to create the API project within Test Studio and copy the API test folder to share with the QA team.
Steps to reproduce:
1. Record a test against the demo page.
2. Select an item from the DropDownList control.
3. Note! the recorded step to select an item from the dropdown is not the KendoAngularList one, but is the KendoListBox.
4. Execute the test.
Expected: to pass the test.
Actual: the correct item from dropdown is selected, but the step is failing with unexpected error.
Workaround to resolve the issue: Open Project Settings and disable the Kendo UI jQuery translators (or the ListBox one only), save the changes and re-record the respective steps in a new recording session. This will record the correct steps and the execution should work as expected.
Custom WPF application with specific control - ViewBox, causes the highlighting to be misaligned.
In case the ViewBox control is removed from the application structure, the highlighting works as expected.
See the screen shot.
There are two annotation markers. For some reason, a "MouseClick:LeftClick" will appear, as it should, but then it sticks there, even as 10 or 12 other steps execute and their annotations come and go. Sometimes another MouseClick:LeftClick will appear and the old one will go away and then the new one will stick. But this does not happen every times. Sometimes a new MouseClick:LeftClick annotation comes in and goes away and the old one is still hanging around.
This happens will almost all of my scripts.
Is it because some of the mouse clicks are from recorded steps and some are from code steps? This is just a guess.
On a data driven web test, setting the DataRange property to the example "SingleRow" causes Visual Studio 2017 to crash. I have three rows of data in a data table that are bound to specific steps of my test. I was attempting to limit execution to only one row temporarily. Using SingleRow or 'SingleRow' causes Visual Studio 2017 to crash with the following stack trace as found in Windows Event log. I was able to successfully use '1:1' or ':1' as a work around.Application: devenv.exe
I had some issues with Test studio projects opening in VS. I reported this issue to Telerik Support on Ticket ID 755261. The main thing from the ticket to note is that the project would backup would throw this error: [11/07 00:23:37,devenv.exe(6016:1),ProjectModel] Project.BackupProject() : EXCEPTION! (see below) Situation: Error creating project backup Outer Exception Type: System.IO.PathTooLongException Message: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. HRESULT: 0x800700CE (Official ID (if app.) = 2147942606, Error Bit = FAILED, Facility = FACILITY_WIN32, Code = ERROR_FILENAME_EXCED_RANGE) With this in mind, I moved all automation projects' folder as close to my base C drive that I could instead of having it on my desktop with filepath of C:\users\name of user\folder... Even after moving my folders, I still had to shorten my automation folders to be a single folder deep and have my tests have shortened file name that I codified to make some sense to what the test should do. I have this problem from R1 2013 and still have this issue. Though I am not sure if others have had this particular issue happen to them, I would think that this problem causes me as a user to lost the flexibility of having my projects in a convenient location on my computer instead of having to dig through to find it.