New answers tagged ios
Personally I always get a bit concerned about "what should I test" questions around security testing, because if you need to ask, you really shouldn't be doing security testing. That said you need to start with a threat model do determine the potential attack vectors and then proceed from there. Your application really needs to follow some form of Security ...
Have you looked at the OWASP top 10 mobile risks? https://www.owasp.org/index.php/Projects/OWASP_Mobile_Security_Project_-_Top_Ten_Mobile_Risks Compare those to the ones in your list
Hope the below link is helpful for you... http://palpapers.plynt.com/issues/2009Apr/mobile-application-security-testing/
Firstly you need to become a member of Apple's developer program, and understand how in app purchase works. As a starting point you should look to Apple's documentation here: https://developer.apple.com/in-app-purchase/. Apple provides sandbox environments to facilitate testing, and it is all covered in the documents and past WWDC sessions. Once you ...
You can figure out the possible test area by asking a few questions to your team. Such as how many products should be offered, what their prices are, and if their purchase is restrained in some way (time window, inventory limit, account status, etc). From this you can start making tests that canvas the in-app purchase functionality.
I would like to share my point of view on mobile testing. I'm an engineer at Neotys, editor of NeoLoad. NeoLoad is a load testing solution designed for web and mobile applications to realistically simulate users activities and monitor servers behaviors. First of all, mobile testing raises the need to perform different tests. On the device point of view, ...
Top 50 recent answers are included