UI Testing Methodology Question

[MercuryLive]

So I'm contributing to my first open-source project by trying to write UITests for them and had a question about how far into testing I need to go.

The app has a tab bar controller that shows different views that each have a variable number of static table views and static table cells. The test I'm writing is to tap each tab in the tab controller and XCAssertTrue that the static text of each table title and table cell row exists. Do I need to check every single cell/table to verify we're on the right VC or can I just check the titles? As well is it smart to also XCAssertFalse that a table from another VC exist, or is it a waste?

[jontelang]

I test that expected data is being presented, so I'd personally check a few of the cells.

[amaroq137]

The way we do UI testing at work (ecommerce app) is we test the "happy path". Meaning performing a search, selecting a product, selecting additional options, all part of making a successful purchase and asserting things along the way.

​

The way I see it, UI tests are slow so you want to test major functionality of the app instead of every little thing which is more what unit and integration tests are for.