1. Create local data for a test.
2. Data bind the same test to external data source.
3. Remove the data binding to the external source.
At this point I can't use the local data for data driven test steps or find expressions.
The workaround is to right click on the test and go to Properties. Then enable both DataEnabled and DefaultToGrid.
When you are in recording mode (with the Recorder attached to the browser) and execute a Test as Step with Run -> From Here or Selected option, the dialogs in that test are not handled.
The dialogs are handled, if you open the test from the Test as Step and use the same options Run -> From Here or Selected for the test itself.
----2013.1.1210----- While making changes to an element's find logic, I received an error. After this error happened, it broke every element and then I had to relaunch test studio to get rid of this compiler error. [12/09 10:21:29,Telerik.TestStudio.exe(6040:27),ProjectModel] Project.RegenerateElementsCode() : EXCEPTION! (see below) Situation: Trouble generating project elements file on first attempt Outer Exception Type: System.InvalidOperationException Message: Collection was modified; enumeration operation may not execute. HRESULT: 0x80131509 (Official ID (if app.) = COR_E_INVALIDOPERATION, Error Bit = FAILED, Facility = FACILITY_URT, Code = 5385) Call Stack: at System.Collections.ArrayList.ArrayListEnumeratorSimple.MoveNext() at Microsoft.CSharp.CSharpCodeGenerator.GenerateNestedTypes(CodeTypeDeclaration e) at Microsoft.CSharp.CSharpCodeGenerator.GenerateType(CodeTypeDeclaration e) at Microsoft.CSharp.CSharpCodeGenerator.System.CodeDom.Compiler.ICodeGenerator.GenerateCodeFromType(CodeTypeDeclaration e, TextWriter w, CodeGeneratorOptions o) at Microsoft.CSharp.CSharpCodeGenerator.GenerateTypes(CodeNamespace e) at Microsoft.CSharp.CSharpCodeGenerator.GenerateNamespace(CodeNamespace e) at Microsoft.CSharp.CSharpCodeGenerator.System.CodeDom.Compiler.ICodeGenerator.GenerateCodeFromNamespace(CodeNamespace e, TextWriter w, CodeGeneratorOptions o) at Microsoft.CSharp.CSharpCodeGenerator.GenerateNamespaces(CodeCompileUnit e) at Microsoft.CSharp.CSharpCodeGenerator.System.CodeDom.Compiler.ICodeGenerator.GenerateCodeFromCompileUnit(CodeCompileUnit e, TextWriter w, CodeGeneratorOptions o) at System.CodeDom.Compiler.CodeDomProvider.GenerateCodeFromCompileUnit(CodeCompileUnit compileUnit, TextWriter writer, CodeGeneratorOptions options) at ArtOfTest.WebAii.Design.ProjectModel.Project.CreateElementsCodeFile(CodeDomProvider provider, Boolean& codeFileCreated, String& codeString, Exception& ex) at ArtOfTest.WebAii.Design.ProjectModel.Project.RegenerateElementsCode()
I have a project configured to Run Locally and a scheduled test list for execution in the future. The error message appears also if you have scheduled a recurring test list.
When I make a change in any of the tests, that are part of the test list, I get the message "Storage service unreachable". My setup does not have an use a Storage service and the test is actually updated and executed as expected.
Please fix the cases when this message appears unnecessarily.
I created a Drag & Drop step from the Step Builder during test recording and picked a specific target element for the Drop location. The steps is created and executed correctly, but I am not able to copy or delete it.
I can disable it, so it does not execute, but it remains in the tests as a step.
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.