Test what?
summary
Decide to watch if wanting concrete rules not platitudes: the claim is that tests must tie to business value—examples are sign-in works and user can view weather—and tools don’t decide what to test. Practical notes name Appium Espresso XCUITest Postman and BrowserStack, warn about mobile OS churn and flaky CI, recommend using analytics and app reviews to pick priorities, show how API checks go beyond status codes, and advise deleting or rewriting repeatedly failing tests.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:30Testing realization story
- 6:12Automation vs manual testing
- 7:50Testing tools
- 9:02Product case
- 11:10Product value
- 12:20Weather
- 16:08Data
- 18:01Why does it matter
- 19:53Recap
- 21:54Pyramid
- 25:39Testing in project phases
- 28:44Mobile testing
- 32:19Identifying API issues
- 35:56Manual vs automated testing
- 43:02Summary
related talks
39mTesting, Testing, 1, 2, NaN
23mWhy testing is also a developer's problem
39mYou're Testing WHAT?
56mTesting for Success in the Real World
15mChoose a Mobile Test Automation Framework That Suits Your Team
18mExploration of tools, frameworks to take the pain out of mobile app testing!
29mTesting Is All About Principles
31mWriting (Really) Good Tests