Bug 6848 - UIAutomation does not work when using story-boards
Summary: UIAutomation does not work when using story-boards
Status: RESOLVED ANSWERED
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 5.99.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-09-03 03:00 UTC by cpdigger
Modified: 2016-02-17 18:50 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED ANSWERED

Description cpdigger 2012-09-03 03:00:36 UTC
I would like to use UIAutomation for UI-Testing.
Unfortunately the accessibility-flag of all the controls is disabled. Therefore UIAutomation does nit work. 
When I set the accessibility of all controls manually, I am able to use UIAutomation. But the settings are not saved and I have to set them all the time.
Can I set the accessibility globally and have it it saved?
What am I to do to be able to use UIAutomation with mono-touch?
Comment 1 Rolf Bjarne Kvinge [MSFT] 2016-02-17 18:50:14 UTC
UIAutomation works fine for testing (Xamarin TestCloud uses it extensively for exactly that purpose for instance), so I don't think this is a bug in Xamarin.iOS.

If you still think I'm wrong, please attach a test project, explaining exactly the steps you're doing and what you expect to to happen, so that we can reproduce any issues ourselves.