Learner Tester

There is huge growth in mobile devices, the number of apps and, not coincidentally, the number of mobile apps That need testing. With problems like device fragmentation and varying orientation, there is a lot That Can go wrong with  the mobile app. If you are new to testing mobile apps, here are some things to do before testing the app and some important things to check while testing the app. Before Starting Know the Apps Limitations Before start starting testing it is useful to speak With The developers. And learn about any Known faults and Limitations like problems with scalability and response time. This helps reduces the invalid bug count later in. the test cycle. Be comfortable With The device Before start starting testing, the tester Should Have to feel for the device and know how Apps are supposed to work and feel. This will help spot Both user interface and performance issues. Check the Mobile Device Hardware and Software Check That

Identification of Signed and Unsigned Android APK file. Goto command prompt.  C:\prgram files\java\jdk1.7.0\bin>jarsigner.exe –verify –verbose –certs “D:\shared folder\Armstrong.APK” or you can use C:\prgram files\java\jdk1.7.0\bin>jarsigner.exe –verify “D:\shared folder\Armstrong.APK”   - Enter. It prints jar verified. If you see “S   ------ META-INF/MANIFEST.MF” at the end, it means your apk is signed . If it prints “no manifest” jar is unsigned, it means your apk is unsigned . There are two modes to build an app 1) Debug mode 2) Release mode. When using debug mode to build your app, the SDK tools invoke Keytool to automatically create a debug keystore and key . This debug key is then used to automatically sign the APK , so you do not need to sign the package with your own key. By default, your IDE will sign your apk with a debug key, which will allow users to install it on their device if they check the "use for development" boxes in the Settings.   In