TestApi Issue Tracker Rss Feed

Commented Issue: Problem closing multiple automated applications [23976]

PaulEbert — Fri, 22 Feb 2013 19:33:12 GMT

I'd like to be able to have more than one automated application running at a time. I'm able to open them and automate them, but there seems to be some sort of problem when I close them. It seems that when I close one, one or more of the remaining ones will also close. However, their associated objects appear to be intact. I get the following exception when I try to close the second application:

System.InvalidOperationException was unhandled
Message=Unsupported Pattern.
Source=UIAutomationClient
StackTrace:
at System.Windows.Automation.AutomationElement.GetCurrentPattern(AutomationPattern pattern)
at Microsoft.Test.ApplicationControl.UIAutomationApplicationImpl.CloseProcessWorker()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
InnerException:
Comments: ** Comment from web user: PaulEbert **

Attached is some code that exhibits the problem.

Created Issue: Problem closing multiple automated applications [23976]

PaulEbert — Fri, 22 Feb 2013 19:31:54 GMT

Commented Issue: Alt+Tab is doesn't work On win8 OS [23408]

xiaxing86 — Tue, 25 Sep 2012 07:14:09 GMT

Alt+Tab is work on win7 but didn’t works on win8. code as below:
Microsoft.Test.Input.Keyboard.Press(Microsoft.Test.Input.Key.LeftAlt);
Microsoft.Test.Input.Keyboard.Press(Microsoft.Test.Input.Key.Tab);
DispatcherOperations.WaitFor(DispatcherPriority.ApplicationIdle);
Microsoft.Test.Input.Keyboard.Release(Microsoft.Test.Input.Key.Tab);
Microsoft.Test.Input.Keyboard.Release(Microsoft.Test.Input.Key.LeftAlt);
Comments: ** Comment from web user: xiaxing86 **

Created Issue: Alt+Tab is doesn't work On win8 OS [23408]

xiaxing86 — Tue, 25 Sep 2012 07:12:46 GMT

Created Issue: IndexOutOfRangeException in NumberProperty.InitializeNumberCharDictionary [23138]

codekaizen — Tue, 07 Aug 2012 21:50:48 GMT

An IndexOutOfRangeException is thrown on line 89 of NumberProperty.cs due to the fact that there are 2 identical ranges in the `expectedRanges` parameter under certain conditions which I am not fully able to describe, however, it appears to be a bug with clearing the cached 'range' state in StringFactory.

This unit test fails, highlighting the issue:

[Fact]
public void ChangingStringPropertiesResetsCachedStringFactoryState()
{
var properties = new StringProperties
{
MinNumberOfCodePoints = 10,
MaxNumberOfCodePoints = 30
};
var s1 = StringFactory.GenerateRandomString(properties, 1234);

properties = new StringProperties()
{
MinNumberOfCodePoints = 10,
MaxNumberOfCodePoints = 30,
HasNumbers = true
};

s1 = StringFactory.GenerateRandomString(properties, 1234);
}

Moving the `ranges.Clear()` call in StringFactory.InitializeProperties before the conditional fixes this problem, since it appears to reset the chached state correctly.

However, I'd even say further the design of this class is suspect, since cached static state prevents any concurrency. Why is StringFactory static? Why not create a StringFactory per properties as an instance, which would allow the desired caching without the global state which causes these kinds of problems?

Closed Issue: OutOfProcessApplication [18170]

ivom — Thu, 10 Feb 2011 22:50:34 GMT

I’m running into some exception/limitations using the OutOfProcessApplication class.

Basically I just need a way to send command arguments to an outOfProcessApplication even if I have already started the application.

When I initially start the outOfProcessApplication I can set the ProcessStartInfo to contain the command arguments I want to start the process with, but if I try and change the arguments and call Start() again then I get an exception that the process is already started. This makes sense, but it does not work how the Diagnostics.Process class works, which allows you to call Start() even on an already running process and it just sends the command line parameters to the application.

Is there a way to send command line arguments to an already running outOfProcessApplication?

I have code from an older project which wraps Process.Start() to add my wanted functionality I can dig up if this is not an already supported function.
Comments:

Oliman,
I am closing this issue. Let us know if you have a reliable repro and we will investigate.
ivo

Closed Issue: Target App Gets Exception when Launched via AutomationHelpers.StartProcess [12712]

ivom — Thu, 10 Feb 2011 22:49:55 GMT

I was able to recreate a similar sample project based upon your sample project from scratch and run it successfully.
However, when I tried to do this again for a larger project, it is not able to launch the target application due to the following error:

'InstInfo.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll', Symbols loaded.
'InstInfo.exe' (Managed): Loaded 'C:\NextGen\Inc1\Week3-TestingWpfApps\InstrumentInformatics\TestResults\pfeffjd_ADDEMAL030907 2009-02-27 14_44_22\Out\InstInfo.exe', Symbols loaded.
'InstInfo.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\PresentationFramework\3.0.0.0__31bf3856ad364e35\PresentationFramework.dll', Symbols loaded.
'InstInfo.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\WindowsBase\3.0.0.0__31bf3856ad364e35\WindowsBase.dll', Symbols loaded.
'InstInfo.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll', Symbols loaded.
'InstInfo.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\PresentationCore\3.0.0.0__31bf3856ad364e35\PresentationCore.dll', Symbols loaded.
An unhandled exception of type 'System.Windows.Markup.XamlParseException' occurred in PresentationFramework.dll

Additional information: Cannot find type 'InstInfo.Shell'. The assembly used when compiling might be different than that used when loading and the type is missing. Error in markup file 'InstInfo;component/Shell.xaml' Line 1 Position 17.

'InstInfo.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Configuration\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll', Symbols loaded.
'InstInfo.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll', Symbols loaded.

Can you provide advice on how to debug this? It cannot launch the test project "instInfo" from this line:

Process appProcess = AutomationHelpers.StartProcess(new ProcessStartInfo("InstInfo.exe"), out rootElement);

Note that InstInfo.Shell is the main StartupUri WPF window of the target application:

<Application x:Class="InstInfo.App"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:Presenters="clr-namespace:InstInfo.Presenters"
xmlns:Model="clr-namespace:InstInfo.Model"
StartupUri="Shell.xaml">

Also, I'm not sure if any of this is important, but it is a RibbonWinow:

<r:RibbonWindow x:Class="InstInfo.Shell"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:r="clr-namespace:Microsoft.Windows.Controls.Ribbon;assembly=RibbonControlsLibrary"
xmlns:me="clr-namespace:InstInfo"
xmlns:uc="clr-namespace:InstInfo.UserControls"
Title="Target Test App"
WindowStartupLocation="CenterScreen"
Background="{DynamicResource WindowBackground}"
AutomationProperties.AutomationId="autoShellWindow" >

Note this same target process can be successfully launched through the VS2008 IDE or be double clicking on the InstInfo.exe located
either in the test project or original target project bin/Debug directory:

Here is the call stack when attaching to the failed target app process.

> PresentationFramework.dll!System.Windows.Markup.XamlParseException.ThrowException(string message, System.Exception innerException, int lineNumber, int linePosition, System.Uri baseUri, System.Windows.Markup.XamlObjectIds currentXamlObjectIds, System.Windows.Markup.XamlObjectIds contextXamlObjectIds, System.Type objectType) + 0x1bf bytes
PresentationFramework.dll!System.Windows.Markup.XamlParseException.ThrowException(System.Windows.Markup.ParserContext parserContext, int lineNumber, int linePosition, string message, System.Exception innerException) + 0x58 bytes
PresentationFramework.dll!System.Windows.Markup.BamlRecordReader.ReadRecord(System.Windows.Markup.BamlRecord bamlRecord) + 0x75f bytes
PresentationFramework.dll!System.Windows.Markup.BamlRecordReader.Read(bool singleRecord = false) + 0x1c bytes
PresentationFramework.dll!System.Windows.Markup.TreeBuilderBamlTranslator.ParseFragment() + 0xc9 bytes
PresentationFramework.dll!System.Windows.Markup.TreeBuilder.Parse() + 0xf bytes
PresentationFramework.dll!System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream stream, System.Windows.Markup.ParserContext parserContext, object parent, bool closeStream) + 0xc7 bytes
PresentationFramework.dll!System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream stream, System.Windows.Markup.ParserContext pc) + 0xb6 bytes
PresentationFramework.dll!System.Windows.Application.LoadComponent(System.Uri resourceLocator, bool bSkipJournaledProperties) + 0xcf bytes
PresentationFramework.dll!System.Windows.Application.DoStartup() + 0xe4 bytes
PresentationFramework.dll!System.Windows.Application..ctor.AnonymousMethod(object unused) + 0x36 bytes
WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate callback = {Method = {System.Object <.ctor>b__0(System.Object)}}, object args = null, bool isSingleParameter = true) + 0x8a bytes
WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.TryCatchWhen(object source = {System.Windows.Threading.Dispatcher}, System.Delegate callback, object args, bool isSingleParameter, System.Delegate catchHandler = null) + 0x4a bytes
WindowsBase.dll!System.Windows.Threading.Dispatcher.WrappedInvoke(System.Delegate callback, object args, bool isSingleParameter, System.Delegate catchHandler) + 0x44 bytes
WindowsBase.dll!System.Windows.Threading.DispatcherOperation.InvokeImpl() + 0x5d bytes
WindowsBase.dll!System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(object state) + 0x38 bytes
mscorlib.dll!System.Threading.ExecutionContext.runTryCode(object userData) + 0x51 bytes
[Native to Managed Transition]
[Managed to Native Transition]
mscorlib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x67 bytes
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x45 bytes
WindowsBase.dll!System.Windows.Threading.DispatcherOperation.Invoke() + 0x63 bytes
WindowsBase.dll!System.Windows.Threading.Dispatcher.ProcessQueue() + 0x127 bytes
WindowsBase.dll!System.Windows.Threading.Dispatcher.WndProcHook(System.IntPtr hwnd, int msg, System.IntPtr wParam, System.IntPtr lParam, ref bool handled) + 0x63 bytes
WindowsBase.dll!MS.Win32.HwndWrapper.WndProc(System.IntPtr hwnd = 529260, int msg = 49785, System.IntPtr wParam = 0, System.IntPtr lParam = 0, ref bool handled = false) + 0xbe bytes
WindowsBase.dll!MS.Win32.HwndSubclass.DispatcherCallbackOperation(object o) + 0x7a bytes
WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate callback = {Method = {System.Object DispatcherCallbackOperation(System.Object)}}, object args = {MS.Win32.HwndSubclass.DispatcherOperationCallbackParameter}, bool isSingleParameter = true) + 0x8a bytes
WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.TryCatchWhen(object source = {System.Windows.Threading.Dispatcher}, System.Delegate callback, object args, bool isSingleParameter, System.Delegate catchHandler = null) + 0x4a bytes
WindowsBase.dll!System.Windows.Threading.Dispatcher.WrappedInvoke(System.Delegate callback, object args, bool isSingleParameter, System.Delegate catchHandler) + 0x44 bytes
WindowsBase.dll!System.Windows.Threading.Dispatcher.InvokeImpl(System.Windows.Threading.DispatcherPriority priority, System.TimeSpan timeout, System.Delegate method, object args, bool isSingleParameter) + 0x91 bytes
WindowsBase.dll!System.Windows.Threading.Dispatcher.Invoke(System.Windows.Threading.DispatcherPriority priority, System.Delegate method, object arg) + 0x40 bytes
WindowsBase.dll!MS.Win32.HwndSubclass.SubclassWndProc(System.IntPtr hwnd = 529260, int msg = 49785, System.IntPtr wParam = 0, System.IntPtr lParam = 0) + 0xdc bytes
[Native to Managed Transition]
[Managed to Native Transition]
WindowsBase.dll!System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame frame = {System.Windows.Threading.DispatcherFrame}) + 0xc7 bytes
WindowsBase.dll!System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame frame) + 0x49 bytes
WindowsBase.dll!System.Windows.Threading.Dispatcher.Run() + 0x4c bytes
PresentationFramework.dll!System.Windows.Application.RunDispatcher(object ignore) + 0x1e bytes
PresentationFramework.dll!System.Windows.Application.RunInternal(System.Windows.Window window) + 0x6f bytes
PresentationFramework.dll!System.Windows.Application.Run(System.Windows.Window window) + 0x26 bytes
PresentationFramework.dll!System.Windows.Application.Run() + 0x19 bytes
InstInfo.exe!InstInfo.App.Main() + 0x4c bytes C#
Comments:

Jon,
I am closing this issue.
Please, reactivate if you have a reliable repro and we will investigate.

Thanks!
Ivo

Closed Issue: CommandLineParser Exception [13638]

ivom — Thu, 10 Feb 2011 22:49:11 GMT

var cmd = CommandLineDictionary.FromArguments(Environment.GetCommandLineArgs()); throws following exception:

System.ArgumentException was unhandled
Message="Unsupported value line argument format.\r\nParametername: D:\\_Workspace\\Projects\\TheGamesFramework\\bin\\x86\\Debug\\TheGamesFramework.Engine.vshost.exe"
Source="FrameworkUtilities"
ParamName="D:\\_Workspace\\Projects\\TheGamesFramework\\bin\\x86\\Debug\\TheGamesFramework.Engine.vshost.exe"
StackTrace:
bei Microsoft.Test.CommandLineDictionary.AddArgument(String argument) in D:\Downloads\Development\Libs\TestApi v.0.2\Sources\FrameworkUtilities\CommandLineDictionary.cs:Zeile 189.
bei Microsoft.Test.CommandLineDictionary.FromArguments(IEnumerable`1 arguments, Char keyCharacter, Char valueCharacter) in D:\Downloads\Development\Libs\TestApi v.0.2\Sources\FrameworkUtilities\CommandLineDictionary.cs:Zeile 91.
bei Microsoft.Test.CommandLineDictionary.FromArguments(IEnumerable`1 arguments) in D:\Downloads\Development\Libs\TestApi v.0.2\Sources\FrameworkUtilities\CommandLineDictionary.cs:Zeile 71.
bei TheGamesFramework.Core.Managers.ConfigManager.ProcessCommandArgs() in D:\_Workspace\Projects\TheGamesFramework\Core\Managers\ConfigManager.cs:Zeile 59.
bei TheGamesFramework.Core.Managers.ConfigManager.LoadConfiguration(Boolean processCommandArgs) in D:\_Workspace\Projects\TheGamesFramework\Core\Managers\ConfigManager.cs:Zeile 174.
bei TheGamesFramework.Engine.MainWindow..ctor() in D:\_Workspace\Projects\TheGamesFramework\Engine\MainWindow.xaml.cs:Zeile 37.
bei TheGamesFramework.Engine.App.StartupClient(StartupEventArgs e) in D:\_Workspace\Projects\TheGamesFramework\Engine\App.xaml.cs:Zeile 65.
bei TheGamesFramework.Engine.App.OnStartup(StartupEventArgs e) in D:\_Workspace\Projects\TheGamesFramework\Engine\App.xaml.cs:Zeile 42.
bei System.Windows.Application.<.ctor>b__0(Object unused)
bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
bei System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
bei System.Windows.Threading.DispatcherOperation.InvokeImpl()
bei System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
bei System.Threading.ExecutionContext.runTryCode(Object userData)
bei System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
bei System.Windows.Threading.DispatcherOperation.Invoke()
bei System.Windows.Threading.Dispatcher.ProcessQueue()
bei System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
bei MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
bei System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
bei System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Boolean isSingleParameter)
bei System.Windows.Threading.Dispatcher.Invoke(DispatcherPriority priority, Delegate method, Object arg)
bei MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
bei MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
bei System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
bei System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
bei System.Windows.Threading.Dispatcher.Run()
bei System.Windows.Application.RunDispatcher(Object ignore)
bei System.Windows.Application.RunInternal(Window window)
bei System.Windows.Application.Run(Window window)
bei System.Windows.Application.Run()
bei TheGamesFramework.Engine.App.Main() in D:\_Workspace\Projects\TheGamesFramework\Engine\obj\x86\Debug\App.g.cs:Zeile 0.
bei System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
bei System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
bei Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
bei System.Threading.ThreadHelper.ThreadStart_Context(Object state)
bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
bei System.Threading.ThreadHelper.ThreadStart()
InnerException:
Comments:

Overlord,
I am closing this issue. Please reactivate if you still need help.
ivo

Closed Issue: In-Process control, start application ==> app.MainWindow = null [13500]

ivom — Thu, 10 Feb 2011 22:48:30 GMT

Hello,
Could you please clarify following about In-Process control?
I'm trying to start my application using EXAMPLE #2 from the Concepts.doc, so my code is:

---------------------------
InProcessSettings ips = new InProcessSettings("D:\\prj\\TheApplication.exe",
"TheApplication",
OnMainWindowCreated,
OnExit);

AutomatedApplication a = AutomatedApplication.Start(ips);

---------------------------
Upon execution I get a.MainWindow = null.
So, the question is - am I missing something for starting target application using in-process control?
Comments:

Closing, as the issue has been resolved.

Closed Issue: FindElementsByName does not work... [12168]

ivom — Thu, 10 Feb 2011 22:47:31 GMT

see the below code --
AutomationElement rootElement;
Process appProcess = AutomationHelpers.StartProcess(new ProcessStartInfo("SampleApp.exe"), out rootElement);

AutomationElement inputTextBox = AutomationUtilities.FindElementsById(rootElement, "inputTextBox")[0];
AutomationElement inputTextBox = AutomationUtilities.FindElementsByName(rootElement, "inputTextBox")[0]; ---> line of failure

FindElementsByName() seems to fails
Comments:

Prakash,
I am closing this issue as I believe it has been resolved (see Peter's comment).
Please reactivate it if that is not the case.
Ivo

Closed Issue: Run NUnit sample from v0.3 and v0.4 ==> FailedSystem.InvalidOperationException: No process is associated with this object. [13749]

ivom — Thu, 10 Feb 2011 22:46:36 GMT

TestAPI 0.3, NUnit Sample.

I'm getting following upon an attempt to run VerifyWindowAppearance() test :

VisualVerificationTests.VerifyWindowAppearance : FailedSystem.InvalidOperationException: No process is associated with this object.
at System.Diagnostics.Process.EnsureState(State state)
at System.Diagnostics.Process.get_HasExited()
at Microsoft.Test.ApplicationControl.UIAutomationApplicationImpl.Close() in c:\dd\WPF\src\wpf\test\Infra\TestApi\TestApiWpf\Code\ApplicationControl\UIAutomationApplicationImpl.cs: line 185
at Microsoft.Test.ApplicationControl.AutomatedApplication.Close() in c:\dd\WPF\src\wpf\test\Infra\TestApi\TestApiCore\Code\ApplicationControl\AutomatedApplication.cs: line 183
at VisualVerificationTests.VerifyWindowAppearance() in VisualVerificationTests.cs: line 76

Note: the application is not closed.
Comments:

NLord,
Is this still an issue? If so, please rectivate.
Ivo

Commented Issue: OutOfProcessApplication [18170]

ivom — Thu, 10 Feb 2011 22:43:21 GMT

Is this still an issue?

Closed Issue: TestAPI 0.4, getting 'System.InvalidOperationException' upon calling AutomatedApplication.Close() [15264]

ivom — Thu, 10 Feb 2011 22:42:23 GMT

Hello,
the issue looks similar to http://testapi.codeplex.com/WorkItem/View.aspx?WorkItemId=13749 but has its own nuances:

We have a set of tests built over TestAPI v0.2, each test has tear-down method which calls App.Close(), where 'App' is OutOfProcess AutomatedApplication.
After switching to TestAPI v0.4 We've started to get following upon calling App.Close():

System.InvalidOperationException: Exception of type 'System.InvalidOperationException' was thrown.
at System.Windows.Automation.AutomationElement.GetCurrentPattern(AutomationPattern pattern)
at Microsoft.Test.ApplicationControl.UIAutomationApplicationImpl.CloseProcessWorker() in c:\dd\WPF_1\src\wpf\test\Infra\TestApi\TestApiWpf\Code\ApplicationControl\UIAutomationApplicationImpl.cs: line 250
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

Note: The work-around suggested in http://testapi.codeplex.com/WorkItem/View.aspx?WorkItemId=13749 (calling sampleAppPath.Replace("file:\\", string.Empty)) doesn't work for our set of tests.

The issue is quite painful since we'd like to engage new features in TestAPI but we can't due to the issue.
Thank you in advance.
Comments:

NLord,
I am closing this issue as it appears to no longer repro.
Please, reactivate if you have a reliable repro and we will investigate.

Thanks!
Ivo

Closed Issue: EntryPointNotFoundException when debugging on AutomatedApplication [13304]

ivom — Thu, 10 Feb 2011 22:41:09 GMT

I have been trying to debug into a test that I have that simply launches a new WPF Window. I am using the OutOfProcessSettings on the AutomatedApplication and calling its Start method. At this point I get an EntryPointNotFoundException, with a message of "Unable to find an entry point named 'nonexistent_dummy' in DLL 'MSVCR80.dll'."

I am running Vista 64, VS 2008 SP1, .Net Framework 3.5 SP1

Can someone suggest some pointers? Without debugging ability this awesome library becomes completely unusable for my team.

Thanks in advance.
Comments:

Closing due to no traction.
Pavan, please re-activate the issue if you still see it.

Closed Issue: Use System.Windows Geometry types, rather than those from System.Drawing [13168]

ivom — Thu, 10 Feb 2011 22:02:22 GMT

The UIAutomation api uses System.Windows geometry types (For example, AutomationElementInformation.BoundingRectangle returns a System.Windows.Rect). For consistency then, methods like Mouse.MoveTo (contained in the tellingly-named assembly WpfUtilities) should surely be using System.Windows.Point rather than System.Drawing.Point?
Comments:

Peter is right.
The goal was to provide a "lowest common denominator" solution and that on Windows turned out to be classic Win32 screen coordinates. Otherwise, we would have introduced a dependency on WPF structures, which are not necessarily present on some machines.

Closed Issue: CommandLineParser cannot handle Application path [13968]

ivom — Thu, 10 Feb 2011 15:48:43 GMT

The commandline parser cannot handle the first argument when Environment.GetCommandLineArgs() is used, which is always the application path or String.Empty. It always throws an exception even without any arguments supplied by the user.
http://msdn.microsoft.com/en-us/library/system.environment.getcommandlineargs.aspx See Remarks.
Comments:

Closed Issue: v0.4, Can't enter Cyrillic/Japanese text into an edit box. [18042]

ivom — Thu, 10 Feb 2011 15:45:45 GMT

Hello, I'm using following mthod for typing a value into an edit box:

public void TypeText(string inputText)
{
AutomationElement.SetFocus();
Keyboard.Type(inputText);
}

it works for numerics and Latin characters, but invoking

TypeText("ФЫВА") or TypeText("十") doesn't, the field-under-test is not populated.

Looks like VkKeyScan(char ch) works only with Latin.
Are there any work-arounds?
Comments:

TestApi 0.6 now supports input injection of non-ascii strings.

Commented Issue: v0.4, Can't enter Cyrillic/Japanese text into an edit box. [18042]

ivom — Wed, 11 Aug 2010 16:53:45 GMT

Btw, just to close down this thread, we have implemented support for non-ASCII characters and will release this support with the next version of TestApi.
Ivo

Created Issue: OutOfProcessApplication [18170]

Oliman — Thu, 08 Jul 2010 21:00:57 GMT

Created Issue: v0.4, Can't enter Cyrillic/Japanese text into an edit box. [18042]

NLord — Tue, 22 Jun 2010 10:06:32 GMT