The Check for JS errors step is not working on remote execution with the Test Studio Test Runner. I have no issues when executing locally on the machine with Test Studio.
This is causing troubles for the CI builds and scheduled execution.
Currently when a test step is set to SimulateRealClick or SimulateRealTyping, the target element is unconditionally scrolled to the top of the browser window, even in cases where the element is already visible. It would be more efficient to test if the target element is already fully visible and only scroll when needed.
Really excited to have a dashboard to present to the team now
Is there anyway to configure the number of Tests that display from within a result? Right now it only looks like 5 is what is the default, that requires quite a big of pagination.
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.
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.
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.
Data bound request does not support "application/json" content type.
The exception listed in the log:
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.
How can I change the size of the element suggestion pane? I can't seem to click and drag it, and I'd like to see more than two or three options.
Currently there is only a scroll that can be used to view all options.
I have some databound parrent tests.
For these I have created seperate sheets in my excel, to ensure my part test are working i switch their databinding between the sheets to ensure them working in all environments.
Everytime i rebind a test the excel file gets corrupted! I have to restart the computer and then it works again… What is the fix for this?
I have attached an example of being unable to open the excel document!
Steps to reproduce: Using the project attached execute the test which should handle a dialog. Expected behavior: The save dialog is handled successfully Actual behavior: The dialog is not handled and the following is output in the log: System.TimeoutException: Timed out waiting '60000' msec. for any dialog to be handled '1' Result StackTrace: at ArtOfTest.WebAii.Win32.Dialogs.BaseDialog.WaitUntilAnyHandled(IEnumerable`1 dialogs, Int32 handleCount, Int64 timeoutMilliseconds, Boolean resetHandleCount) at ArtOfTest.WebAii.Win32.Dialogs.BaseDialog.WaitUntilHandled(Int32 handleCount, Int32 timeout, Boolean resetHandleCount) at ArtOfTest.WebAii.Win32.Dialogs.BaseDialog.WaitUntilHandled() at UnitTestProject2.UnitTest1.TestMethod1() in c:\Users\ittodorov\Documents\Visual Studio 2012\Projects\UnitTestProject2\UnitTestProject2\UnitTest1.cs:line 42
Changing the DPI settings to 125%, for example, on Windows 7 causes troubles with the Desktop clicks when running tests against Chrome. The click is below or above the target element. Highlighting in record mode may also be affected.
Workaround: As a workaround the Desktop clicks (MouseClick() method) can be replaced with the Click() method, which works as expected. The alternative in a non-coded solution is to disable the 'SimulateRealClick' option for the click steps.
Allow deserialization of dateTime values to strings instead of DateTime objects when extracting such with JSONPath.
When a dateTime value is returned in a JSON response ("2019-04-08T00:00:00") and a JSONPath expression is used to extract it from that response, Test Studio deserializes it to a DateTime object. This leads to losing its original format.
It will be useful to have the option to deserialize it in a plain string value.
When using the visual studio plug-in, if you update coded files (anything ending in .tstest.cs), when you open your project back up in TS standalone IDE, the changes you made to any given coded file will not automatically be detected so you must open up every .tstest file corresponding to the .tstest.cs files you changed in visual studio, and only then will the IDE see the changes