• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
UI Test
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

UI Test


  • Subject: UI Test
  • From: Daniel Phillips <email@hidden>
  • Date: Wed, 16 Dec 2015 13:27:05 +0000

Hello Xcode Users,

I am new to UI testing/automation. I intend to use an Xcode UI Testing bundle to automate UI testing for my app. 

As always, the WWDC examples are always super simple cases, so I have some questions about UI Testing which hopefully someone can help me with.
  • Backdoor: Is it standard/good practise to program in a “back door” to setup some initial state the app should be in? For example:
    • Some test scenarios I have been given start with “given the user is not logged in…” - Of course I persist some data when the user logs in, so I guess I would need to have UI Test path going to a logout screen and optionally logout if the user is logged in. Is this what is recommended?
    • I have a “what’s new” splash screen, which is shown only once per app version. If I want to UI Test this, I would need to either reinstall the app each time, or somehow reset the user defaults to bypass the flag which I had set when the screen was first seen. What approach would be recommended?
  • Stubbing: I have a lot of data coming into the app via an external API service, it’s a travel app so I need to be aware that my UI Tests could fail if I did a train times search at 3am, if I tested that I have some train times coming back, my test would fail; so, is stubbing network tasks recommended for UI tests? Or is the point to test this app “in the wild”? Again if I did want to stub then I would probably begin to need to bundle stub responses within my apps bundle (given the intension of using continuous integration, I would end up shipping stubs within my binary). I don’t suppose this is recommended.
I guess there’s a fine line between a UI Test and an Integration Test, and probably this means that I should probably provide stubbed network responses for certain tests. But this must mean I cannot (or should not) have a single binary, which has the knock on effect of hindering my companies continuous delivery requirement.

Any thoughts welcome on this. 

Thanks
- Daniel
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Prev by Date: Re: Xcode 7.2 deadlocks freqently
  • Next by Date: Re: Xcode 7.2 deadlocks freqently
  • Previous by thread: Re: Xcode 7.2 deadlocks freqently
  • Next by thread: Re: Xcode-users Digest, Vol 12, Issue 355
  • Index(es):
    • Date
    • Thread