iOS Instruments Automation "setValue" not working

Question

I just want to test my iOS UI with UI Automation but I got stuck when it comes to enter text into UITextFields. The documentation says that the method "setValue(...)" should do the trick but it doesn't.

I always get this error:

Script threw an uncaught JavaScript error: Unexpected error in -[UIATextField_0x9952690 setValue:], /SourceCache/UIAutomation_Sim/UIAutomation-271/Framework/UIAElement.m line 1142, kAXErrorSuccess on line 15 of login.js, #0 setValue() 

The code looks like this:

var textfields = UIATarget.localTarget().frontMostApp().mainWindow().textFields();
username = textfields["username"];
username.setValue("test");

The username field is not null or undefined.

My second solution was this JS project: https://github.com/alexvollmer/tuneup_js#readme It has a "typeString" method for text fields but it is a little bit buggy and fails when it comes to enter numbers and capital letters.

I'm working with iOS6.1, Instruments Version 4.6 (46000), Xcode Version 4.6 (4H127).

Any help is appreciated!

Answer 1

Check if below works for you,

target.delay(1); UIATarget.localTarget().frontMostApp().mainWindow().textFields()["username"].tap(); target.delay(1); UIATarget.localTarget().frontMostApp().mainWindow().textFields()["username"].setValue("test");

Check for correct hierarchy if it does not work for you..

Answer 2

I came here struggling to understand how UI Automation scripting works, as the documentation and example code out there is really lacking (or written from a very specific point of view that doesn't explain all cases).

Here are two things on the subject I learned:

1. First and foremost, you must enable Accessibility on the element. I had disabled it in my trials and things were behaving very strangely until I re-enabled it (getting a similar "unexpected error" as you). So make sure you have Accessibility turned on. But note that some things still work with it disabled. For example, you can still look up the element by its name (accessibilityIdentifier), but you won't be able to tap it or call setValue().

2. You have to dig through your application hierarchy. My assumption was that giving an element an accessibilityIdentifier would allow me to simply look up the element with that identifier like HTML's getElementById. But it is not like this at all. You have to dig through your hierarchy level by level, even when using an accessibilityIdentifier. Luckily you can use UIAElement.logElementTree() to get some clues as to the correct hierarchy to use.

So far I am NOT at all impressed with this framework, but I am ever so slowly making progress.