Skip to content
This repository has been archived by the owner on Feb 9, 2018. It is now read-only.

Test cases

Vicky Chijwani edited this page Feb 25, 2017 · 21 revisions

Also see: What To Test | Android Developers

Test with a RELEASE build (because of Proguard).

Device configurations:

  • APIs 15 through 23 + N preview
  • Different manufacturers: LG, Samsung, Motorola, HTC...
  • Screen rotation
  • Incoming call (APIs 15 through 19)
  • Multi-tasking scenarios
  • Tablets

Blog configurations:

  • Last 2 minor versions of Ghost - 0.6 and 0.7 as of this writing
  • HTTPS
  • Ghost Pro
  • Blog under example.com/blog/ (e.g., issue #161)
  • Hundreds of blog posts + drafts: test usability, network usage, battery usage
  • Multi-author setups
  • Tens of blog posts with large cover images (may crash because we don't ask Picasso to downsample while decoding)
  • Very long posts (1000s of words) => test Markdown preview performance
  • Long string in UI (check ellipsizing / text-wrapping)
  • Blog down

Features:

  • Offline mode
  • Slugs (post URLs)
  • Crash reporting (Crashlytics; Proguard may mess with source line mappings)
  • Interaction among offline mode, auto-saves, explicit saves, publish/unpublish state change, ...
  • Every single transition in the Post State Machine
  • Refresh token expiry / GhostAuth code expiry / password change - edit some posts offline => expire token / change pwd => go online => login => edits should be preserved
  • ...