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.
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.
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.
Multiselect control cannot be recorded against IE as expected. When selecting more than one value from it, using the Ctrl key, not all selected options are listed in the 'SelectedItems' step property.
The 'SelectedItems' step property does not display names of the selected items and it is not visible how many elements there are to be selected.
If the desired items are manually added in the mentioned property, they will be selected correctly in run-time.
The latestMongoDB 4.0.6. cannot be restarted from Scheduling Configuration setup, the mongo service config gets broken if started through the Scheduling wizard and service cannot be started anymore.
Workaround to resolve the not working MongoDB service:Using the latest version of MongoDB 4.0.6.
Test Studio Run-time edition does not deploy the TestAdapter.dll with its installation.
Thus Test Studio tests cannot be executed with the VSTestConsole.exe in a Azure DevOps (VSTS) pipeline.
The TestAdapter.dll for VS 2017 and VS 2019 is being deployed to the Test Studio installation folder (for Ultimate or Dev Edition installations) along with the respective *.vsix package. Until the misbehavior is fixed, the vsix package can be copied to the agent machine and installed with double click. Then refer the dll from the respective location.
in some cases when load run with profiling is triggered, randomly null data is returned that cannot be serialized and serialization exception is thrown in log and load result reports wrong default data