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'"...
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.
It is rather difficult to debug tests that use nested sub-tests. You can't set a breakpoint in a sub-test (it's ignored) and you can't "Step over" and "Step into" similar to how source code debugging works in Visual Studio.
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.
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.
In record mode, select two steps to execute with Run->Selected Steps - one which triggers the dialog, and the other to handle it. Expected: To handle the dialog Actual: The Handle dialog step times out.
----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.
On the Executive Dashboard, the columns are all fixed sized, the problem with this is that it gives very little space for test and test list names and makes it difficult to view the naming.
Please provide a way to resize or view the names easily.
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.