Re: iOS UI Tests

2016-05-12 Thread Steph Leroux
Hey Farhan, I was seeing this crash on a KIF test I was writing last week but has since been resolved on master from Emily's changes here [1]. If you haven't written the test yet it would be best to start up a new UITesting target that uses the new UITest framework instead of KIF. Rebasing master

Re: iOS UI Tests

2016-05-12 Thread Emily Toop
Farhan, It would be really great if new UITests were written using the new UITesting framework rather than expanding on the existing KIF tests. Any chance you could create a new target for UITesting and write these new tests in there? Once the target is there it will be easier to start adding to t

Re: iOS UI Tests

2016-05-11 Thread Farhan Patel
Hey James I've been trying to write tests for the third party search engines and am having issues getting many of them to run. When I try to run the UI tests I get the error /UITests/AuthenticationManagerTests.swift: test failure: -[AuthenticationManagerTests testChangedPasswordMustBeNew()] fa

Re: iOS UI Tests

2016-05-04 Thread James Hugman
Michael, Thanks, that's a really good tip. It works like a charm in the TestAppDelegate . (the AppDelegate is the functional equivalent of `android.app.Application` object). We get to choose which one

Re: iOS UI Tests

2016-05-02 Thread Michael Comella
Hey. I'm missing context but... On Sun, May 1, 2016 at 5:32 PM, James Hugman wrote: > I thought this might be a set of fixes which roughly translate to > "sprinkle in a few `tester().waitForAnimationsToFinish()` statements", but > it turns out to not be as simple as that. > It doesn't sound li

Re: iOS UI Tests

2016-05-01 Thread Aaron Train
Thank you for this investigation James. Catalan and I can spend an additional cycle of manual coverage on the continuing finicky and disabled tests to at least ensure we aren’t flying blind. Aaron Train Sr. QE Engineer Mozilla Corporation https://quality.mozilla.org > On May 1, 2016, at 8:32 PM

iOS UI Tests

2016-05-01 Thread James Hugman
Hey, I've spent a few spare cycles looking at the UI tests, which are currently failing consistently. I thought this might be a set of fixes which roughly translate to "sprinkle in a few `tester().waitForAnimationsToFinish()` statements", but it turns out to not be as simple as that. I'll probab