For certain control Test Studio can record elements using chained queries - include parent and child element. If one wants to create such manually or modify an existing element to use chained query, needs to use the coded approach to define elements' queries. There is no way how to adjust an element's query to be chained if using the Edit element pane in the UI.
It will be really useful to add the ability to modify the elements queries and transform these to chained queries.
I have a screen with multiple KendoNumericTextBox. After trying to use recorded and coded step to handle the second KendoNumericTextBox in the page using KendoInputValue, these same problem occurs to me:
1. The function "ClearBeforeTyping" clears the first KendoNumericTextBox instead of the second one but correctly input the data in the second one.
2. The function "UseClientAPI" clears and input data in the first KendoNumericTextBox instead of the second one.
When i validate and locate each of the element, the tool is able to locate them correctly. In coded step, I only use the second textbox , not the first one but in execution, it still edit the first textbox and the problems mentioned above happened.
What should i do to be able to handle this type of textbox correctly?
We are trying to record mobile web tests, but after visiting the first page the device gets disconnected.
A loading screen appears in the DOM explorer, but after a while it stops without recording the second page.
The switching between pages is with normal anchors on the website.
This happens on certain pages with large DOM size.
A popup with "End of Central Directory record could not be found." error shows up when I try to add a custom step from the step builder.
When I restart Test Studio, the test works fine.
I have a project with load test. The test has many user profiles and I need to add more in some cases. When they become too much, I can not save my changes in Test Studio.
The .tstest file is about 40-50 MB when I have this issue.
I was able to add a custom dynamic target and bind it to a data source. When I do the same for another custom dynamic target with the same Field Name and save the changes, the data binding breaks.
Both dynamic targets are changed to the first target with the lower destination step.
Wait for exists step is failing with the error below, when Test Studio is not able to find the element:
Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an object.
As a result the conditional steps are not working as expected and the test fails.
The workaround for this issue is to change the WaitForExists step to VerifyExists step and the test works.
The selection from a KendoAngularList dropdown is defaulting to the recorded selection, when the step is data driven.
The temporary workaround is to convert the step to code from the context menu, after it is all configured.
After installing my DevCraft package, my keyboard has limited functionality, when trying to create a new project/solution in Visual Studio 2019. I am able to use "space" and "backspace" keys, but not letters and numbers.
Uninstalled Test Studio Dev or disabling Telerik.TestStudio extension and I have full keyboard functionality on screen for creating a new project in Visual Studio 2019.
As a workaround I am able to use CTRL + V to paste any text from my clipboard.
Android mobile app cannot be configured with Android Gradle plugin 3.4.2 and no test can be recorded against that.
Steps to reproduce:
1. Open an Enter password step and expand in the step pane
2. Set the encrypt property
Expected: All fields with the actual text entered should be masked with *
Actual: If the step is expanded the actual text entered field does not change its value.
Note: Reopening the test fixes the visual glitch.
When using a builtin step for checking rowscount of a table that uses "greater than" or "less than" it fails even though it should not.
"Equals" works fine.. but if I use any other TableVerificationType than "equals", then it fails.. unless if I convert it to a coded step.
So to reiterate: If I convert the step to a coded step then it works.
We have several test projects that now have failing tests because of this.
Attached test project that showcases the problem.
The step gets successfully executed but fails with the following exception:
InError set by the client. Client Error:
Cannot read property 'toggle' of undefined
BrowserCommand (Type:'Action',Info:'NotSet',Action:'InvokeJsFunction',Target:'ElementId (tagName: '',occurrenceIndex: '-1')',Data:'$("th:eq(1)").data("kendoFilterMenu").popup.toggle()',ClientId:'663fc963-6051-4044-9dfb-ce01ca15339d',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'True',Response:'Cannot read property 'toggle' of undefined')
Workaround: Record the click step to open the filter without using the Test Studio translator, or in other words against the span element directly.
Data bound request does not support "application/json" content type.
The exception listed in the log:
When the element's find expression fails to find the element it should log in the execution log, that alternative method of verification is used.
The Wait for Exists step does not log the usage of image verification, even though the find expression fails.
The behavior with click step is as expected and the log is correctly generated.'17-Jul-19 14:10:30' - 'Pass' : 2. Click 'BtnKSubmit'
During the trial period of Test Studio, by each start of Test Studio or Visual Studio there is a prompt window to continue the trial or activate a purchased license.
The license prompt window of the Test Studio plugin (part of the DevCraft Ultimate package as well) in Visual Studio 2019 start window prevents typing in the following native VS windows - Create project and Clone/Checkout code.
I. Change how Visual Studio 2019 starts:
1. Open any existing project in VS 2019
2. Open Tools-> Options-> Environment -> Startup
3. Select any of the other listed options in the dropdown on the right - Most recent solution or Empty Environment.
II. For the cases when DevCraft Ultimate is installed and the Test Studio plugin is not the current focus of evaluation.
1. Disable the Test Studio extensions.
2. Open any existing project in VS 2019
3. Open Extensions -> Manage Extensions -> disable the following extensions: