Follow

Testing Checklist

Testing app/build against:

  • Boilerplate test planner per platform
  • Release/build notes
  • Fixed issues/JIRA tickets/issues raised in previous build/commit history
  • In addition to app functionality and content, also likely to be testing (integration of) third party services

Not testing against:

  • Features in the boilerplate that the app doesn’t have (i.e. ensure you know what the app is supposed to do)

Testing on:

  • Relevant devices i.e. supported platform/OS version [ensure this is clear e.g. Kindle only vs. Android testing; iPad only vs. iOS testing]
  • A range of device types/screen sizes/OS levels
  • For some platforms (e.g. iOS) there’s a limited amount of device types, easy to choose representative sample, for others (e.g. Android) this is not the case and need to test on as wide a variety of devices as possible
  • Physical devices, as well as with simulator/emulator (iOS Simulator with Xcode for iOS; Eclipse or intelliJ IDEA; Genymotion for Android) as relevant

Document everything because:

  • May want records of the results in the future
  • May be relevant to other work so should be fed back
  • Testing is iterative

Do testers have:

  • The testing hardware (inc. infrastructure like chargers/USB cables; device logins)
  • Emulator/simulator
  • Debugging set up/tools
  • (Ability to put) build on devices (consider also provisioning profiles)
  • Correct info about the app’s expected behaviour (e.g. up to date release notes)
  • Test accounts (e.g. for testing sharing; purchasing)

Instructions for testing:

Edgecase testing:

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk