We had several questions during the webinar with Costa Avradopoulos last month. One that we didn’t get to with respect to Requirements for XBOSoft Knowledge Center Blog - software testing, QA companyMobile Testing was:
“Effective testing is always linked with requirements. MOST of these apps are written on the fly with NO documented requirements. How does a tester account for this?” 
Unfortunately this is quite common with developing mobile apps.  We were able to discuss these issues with Costa, and he said:
While it’s not unique to mobile, mobility certainly exacerbates the issue because you have more nuances/variations than non-mobile apps to deal with (i.e. interruption test scenarios).  Even when you do have pretty good requirements, I still find many significant gaps that a good document inspection or peer review will uncover.  So what to do if you have none?  The best solution is to reject the build and not allow testing to even start until you have some requirements (even if they are not good/complete).  Regardless of whether that is an option or not, follow these tips to get back on track:
  1. 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 costa@avracom.com if you are interested in more information.)
  2. 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.
  3. Install/test similar apps from competitors to get ideas on things you should look for.  Again, document for discussion with your BA/PO/Dev.
  4. 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: