Won't Fix
Last Updated: 20 Apr 2016 15:08 by ADMIN
Steps to reproduce:



1. Execute the test attached internally using Firefox.



Problem: 1

Expected behavior: The test should pass

Actual behavior: Step 15 fails with the following exception:



'02/08/2016 10:01:39 AM' - 'Fail' : 15. Wait for 'TextContent' 'Contains' 'Get started with your Free Membership' on 'GetStartedSpan'
------------------------------------------------------------
Failure Information: 
~~~~~~~~~~~~~~~
Unable to find the target host (Browser/SilverlightApp) to locate an element. Failure: ArtOfTest.WebAii.Exceptions.ExecuteCommandException: ExecuteCommand failed!
BrowserCommand (Type:'Information',Info:'DocumentMarkup',Action:'NotSet',Target:'null',Data:'',ClientId:'9340011e-3a1a-4995-a4d1-ad32e1bef2db',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'0',InError:'False',Response:'')
InnerException: ArtOfTest.WebAii.Exceptions.ExecuteCommandException: ExecuteCommand failed!
InError set by the client. Client Error:
mozCommandProcessor: GetCurrentDocumentMarkup(): Exception thrown while trying to serialize the Dom. Error: TypeError: this.TargetDocument is null
BrowserCommand (Type:'Information',Info:'DocumentMarkup',Action:'NotSet',Target:'null',Data:'',ClientId:'9340011e-3a1a-4995-a4d1-ad32e1bef2db',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'0',InError:'True',Response:'mozCommandProcessor: GetCurrentDocumentMarkup(): Exception thrown while trying to serialize the Dom. Error: TypeError: this.TargetDocument is null')
InnerException: none.

   at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request)
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommand(BrowserCommand request, Boolean performDomRefresh, Boolean waitUntilReady)
   at ArtOfTest.WebAii.Core.Browser.RefreshDomTree()
 ---> ArtOfTest.WebAii.Exceptions.ExecuteCommandException: ExecuteCommand failed!
InError set by the client. Client Error:
mozCommandProcessor: GetCurrentDocumentMarkup(): Exception thrown while trying to serialize the Dom. Error: TypeError: this.TargetDocument is null
BrowserCommand (Type:'Information',Info:'DocumentMarkup',Action:'NotSet',Target:'null',Data:'',ClientId:'9340011e-3a1a-4995-a4d1-ad32e1bef2db',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'0',InError:'True',Response:'mozCommandProcessor: GetCurrentDocumentMarkup(): Exception thrown while trying to serialize the Dom. Error: TypeError: this.TargetDocument is null')
InnerException: none.



The above problem is not reproduced with IE and Chrome

Problem: 2

When I do Run to Here on step 14 and try re-record step 15 the Highlighting does not work, I guess this behavior is related to the first problem when we are not able to get the Markup.

The above problem is not reproduced with IE
Won't Fix
Last Updated: 08 Mar 2016 14:24 by ADMIN
1.Using the test attached do Run to Here on the last step using Firefox.

2. When the recorder attaches try to highlight Leprosy and locate the element in the DOM.



Expected result: You should locate a label element in the DOM

Actual behavior: A span or div element is located in the DOM.

Refer to the screenshot attached internally for more details.



Also try to highlight the td elements elements above

<td width="5%">

<td width="94%">

In Test Studio their order is reversed, while when using Dev Tools for highlighting they are displayed correctly.

This works fine in IE and Chrome
Won't Fix
Last Updated: 30 Mar 2016 08:29 by ADMIN
I am not completely sure how to explain this issue.  

In one of my tests, I have a coded step.  

In Visual Studio, I have resharper and I used resharper to refactored the page declaration to this: 

public Pages Pages => _pages ?? (_pages = new Pages(Manager.Current));

There is only a compilation error in Test Studio. 

Something to do with C# updates.
Won't Fix
Last Updated: 20 Mar 2019 14:46 by ADMIN
Won't Fix
Last Updated: 15 Jan 2016 12:02 by ADMIN
When using an existing web test which contains a Handle Download Dialog, recording of the user profile stops as soon as the download dialog is successfully handled. None of the follow on test steps are executed during recording. As a result what you end up with is an incomplete user profile.

Sample web test to reproduce the problem is attached.
Won't Fix
Last Updated: 24 Dec 2015 08:39 by ADMIN
Steps to reproduce and access to the application are in the internal description.
Won't Fix
Last Updated: 20 Mar 2019 15:02 by ADMIN
Created by: Ahamad
Comments: 0
Type: Feature Request
0
Baan automation testing challenging job for most of the companies . please give us solution for  baan automation testing using telerik test studio.
Won't Fix
Last Updated: 22 Aug 2016 06:10 by Chad
A customer specific application is crashing as soon as you try to select an item and move to the next window. A copy of the application plus a video demonstration of the problem will be included in the internal bug report. In the Windows Event Viewer is this stack trace.
Application: ClientDebugger.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
Stack:
   at Telerik.TestStudio.Wpf.RecordingSurface.WpfRecordingSurfaceManager.UnBind()
   at ArtOfTest.WebAii.Design.RemoteRecorder.WpfRemoteRecorder._watcher_WindowDestroyed(System.Object, ArtOfTest.Common.Win32.WindowEventArgs)
   at Telerik.TestingFramework.XamlExtension.TechSpecific.OnWindowClosed(ArtOfTest.Common.Win32.Window)
   at Telerik.TestingFramework.XamlExtension.TechSpecific._watcher_WindowDestroyed(System.Object, ArtOfTest.Common.Win32.WindowEventArgs)
   at ArtOfTest.Common.Win32.WindowWatcher.OnWindowDestroyed(ArtOfTest.Common.Win32.Window)
   at ArtOfTest.Common.Win32.WindowWatcher._windowsWatcherHook_HookInvoked(System.Object, ArtOfTest.Common.Win32.HookEventArgs)
   at ArtOfTest.Common.Win32.LocalWindowsHook.OnHookInvoked(ArtOfTest.Common.Win32.HookEventArgs)
   at ArtOfTest.Common.Win32.LocalWindowsHook.CoreHookProc(Int32, IntPtr, IntPtr)
   at ArtOfTest.Common.Win32.NativeMethods+User32.CallNextHookEx(IntPtr, Int32, IntPtr, IntPtr)
   at ArtOfTest.Common.Win32.LocalWindowsHook.CoreHookProc(Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.HwndSubclass.DefWndProcWrapper(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
   at System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message ByRef)
   at ArtOfTest.Common.Win32.GenericWindow.WndProc(System.Windows.Forms.Message ByRef)
   at Telerik.TestStudio.Recorder.RecordingSurface.RecorderNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.UnsafeSendMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr)
   at System.Windows.Window.InternalClose(Boolean, Boolean)
   at System.Windows.Window.Close()
   at System.Windows.Window.set_DialogResult(System.Nullable`1<Boolean>)
   at ClientDebugger.ApplicationNameSelectorWindow.btnSelect_Click(System.Object, System.Windows.RoutedEventArgs)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
   at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
   at System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs)
   at System.Windows.Controls.Primitives.ButtonBase.OnClick()
   at System.Windows.Controls.Button.OnClick()
   at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(System.Windows.Input.MouseButtonEventArgs)
   at System.Windows.UIElement.OnMouseLeftButtonUpThunk(System.Object, System.Windows.Input.MouseButtonEventArgs)
   at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(System.Delegate, System.Object)
   at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
   at System.Windows.UIElement.ReRaiseEventAs(System.Windows.DependencyObject, System.Windows.RoutedEventArgs, System.Windows.RoutedEvent)
   at System.Windows.UIElement.OnMouseUpThunk(System.Object, System.Windows.Input.MouseButtonEventArgs)
   at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(System.Delegate, System.Object)
   at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
   at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
   at System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs)
   at System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs, Boolean)
   at System.Windows.Input.InputManager.ProcessStagingArea()
   at System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs)
   at System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputReport)
   at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32)
   at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef)
   at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
   at System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message ByRef)
   at ArtOfTest.Common.Win32.GenericWindow.WndProc(System.Windows.Forms.Message ByRef)
   at Telerik.TestStudio.Recorder.RecordingSurface.RecorderNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Window.ShowHelper(System.Object)
   at System.Windows.Window.Show()
   at System.Windows.Window.ShowDialog()
   at ClientDebugger.Program.Main(System.String[])
Won't Fix
Last Updated: 20 Mar 2019 15:03 by ADMIN
Please add the ability  to automatically update the linked AC's when the test run successfully.
Won't Fix
Last Updated: 20 Mar 2019 15:05 by ADMIN
The way currently Test Studio works with Remote Scheduled run using external references is the following: you must have any assemblies being referenced inside your project root directory in order for them to be deployed when running remotely, which requires additional changes at customers site to comply with this requirement. There should be an out of the box way to deploy proper references without user additional interaction.
Won't Fix
Last Updated: 20 Mar 2019 15:14 by ADMIN
ADMIN
Created by: Ivaylo
Comments: 0
Type: Feature Request
2
Add a setting in the UI for the ability to execute a specific step when test fails. Currently this is only possible using execution extension. 
Won't Fix
Last Updated: 20 Mar 2019 15:17 by ADMIN
We have no need ever for the Team Pulse docked window.  It would be nice to be able to keep this optional docking window from displaying at all.
Won't Fix
Last Updated: 20 Mar 2019 15:44 by ADMIN
Having the ability to move an automated test over to a manual one.  Would also be nice to export the automated tests to excel.
Won't Fix
Last Updated: 20 Mar 2019 15:46 by ADMIN
TTS opens and closes browser even though command line test does not require any browser interaction. It increases test execution time. 

Add n option not to launch browser would be helpful to speed up the test execution and save processing power. 
Won't Fix
Last Updated: 19 Jan 2016 07:28 by ADMIN
Steps to reproduce and access to the application are in the internal description.
Won't Fix
Last Updated: 09 Apr 2019 14:03 by ADMIN
Displayu the full test list name/Execured browser in the tooltip in the same way as it is in the calendar view on results tab.

Refer to the attachment provided internally
Won't Fix
Last Updated: 01 Apr 2019 14:45 by ADMIN
Connecting to pop-up is successful. Using coded step and activebrowser.navigateto(url) to some specific url i.e. "http://www.google.com" results in a "Wait for condition has timed out" error. 

Full error description:
System.TimeoutException: Wait for condition has timed out
   at ArtOfTest.Common.WaitSync.CheckResult(WaitSync wait, String extraExceptionInfo, Object target)
   at ArtOfTest.Common.WaitSync.For[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout, WaitResultType errorResultType)
   at ArtOfTest.Common.WaitSync.For[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout)
   at ArtOfTest.WebAii.Core.Browser.WaitUntilReady()
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommand(BrowserCommand request, Boolean performDomRefresh, Boolean waitUntilReady)
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommand(BrowserCommand request)
   at ArtOfTest.WebAii.Core.Browser.InternalNavigateTo(Uri uri, Boolean useDecodedUrl)
   at ArtOfTest.WebAii.Core.Browser.NavigateTo(Uri uri, Boolean useDecodedUrl)

Why, because page loads successfully?
Won't Fix
Last Updated: 09 Apr 2019 14:04 by ADMIN
ADMIN
Created by: Cody
Comments: 0
Type: Feature Request
1
When DBMigrator is in progress all you see is "Please wait...". There's no indication how far it's gotten nor how much farther there is to go. The user can't tell if he needs to wait another 5 minutes or another 5 days, or even if anything is actually happening. Some sort of feedback needs to be shown the user indicating progress is actually being made by the migration process.

In addition, when the process is completed, it would be useful to show something like "N records migrated" to indicate success or failure of the migration process. Instead currently when the process is finished the "Please wait..." is removed. The user can only assume the process was successful and how much data was migrated.
Won't Fix
Last Updated: 31 Mar 2017 13:08 by ADMIN
The application starts with a log in screen. After login in it disappears and the actual application is launched, however Test Studio has no time to connect to the second window and throws the following exception:

Element was 'not found'. Criteria: Element 'Exists'.

Page being searched 'WpfWindow_16450718'.

The workaround is to insert an execution delay more than 5 secs after the login. 

The steps to reproduce and access to the application are in the internal description.
Won't Fix
Last Updated: 28 Oct 2015 12:14 by ADMIN
In a customer specific application is a popup context menu which is opened via a right click. When recording Test Studio records clicks on wrong items in the menu. The problem is specific to IE 9. It does not repro in IE 10 or Google Chrome. Customer requires IE 9 as their application is only supported on IE 9.

Repro steps will be given on the internal bug report.