- Perform exploratory tests to determine the reasonableness of the app. Of course this is subjective based on your perspective, but naturally you will come up with dozens, if not hundreds, of questions. Document these questions and present them to the business analyst/product owner. These questions should cover basic functionality, as well as all of the nuances that are unique to mobility. (Costa teaches a half-day workshop for BA/QA professionals that covers the latter. Write to him at firstname.lastname@example.org if you are interested in more information.)
- If time permits, offer to write the requirements yourself (at least the first draft). I have done this in the past and it’s proven fruitful in that the product owner realized what they underestimated, and assumed way too much. This can prove be an effective catalyst to getting good dialog going between team members, and everyone on the path to better requirements/tests all can agree on.
- Install/test similar apps from competitors to get ideas on things you should look for. Again, document for discussion with your BA/PO/Dev.
- Review user feedback in the app store on both your app and competitors’ for additional perspectives on missing requirements/tests, and incorporate these into future releases.
Thanks again to Costa for these great tips on dealing with Requirements for Mobile Testing. We know it’s not a perfect world out there and that we need all the help we can get. View our webinar with Costa entitled Designing a Mobile Device Lab here in case you missed it: