| || |
Mobile Application Testing in different OS
Currently, I am learning the Mobile Application testing
I would like to acquire a few thing which is if the requirement supposed to test the mobile application in different Operating systems then how should we proceed further? either manually or automation? And explain the reason why?
Also, Please suggest me the best open source automation tool?
It would be very helpful for me to gain more knowledge in Mobile Application Testing.
Thanks in Advance,
Are you in a regulated industry? If yes, the FDA has some guidance on mobile apps at Mobile Medical Applications and http://www.fda.gov/downloads/Medical.../UCM263366.pdf
As far as testing for different operating systems and using automated testing tools (ATT), it depends on the amount of time you have to test and the amount of testing that needs to be done. If you're already using ATT, it's easy to use them for any new systems because you already know how to use the tool. The only time needed is to input new tests. If you're not using ATT now, you have to add in the time it takes to come up to speed on how the ATT works. In my experience, we've never had the time to do that due to very tight project schedules, so all testing was done manually. When we had to test across numerous operating systems, we simply made copies of the tests scripts and ran a set against each operating system. We did the same any time an operating system was upgraded.
Also, if you're a regulated company you have to validate the testing tool for its intended use. I don't know of any open source ATT. I work in a medical device/pharma/surgical regulated environment and stay away from open source programs due to the issues involved with using it.
I'm not sure you received an appropriate answer to your question, but manual testing or automation testing mobile apps depends on what you're testing. Simply put, manual testing is the most inexpensive, effective, and common place to begin. Manual testing allows you to quickly test according to specs/requirements, exploratory testing (discovery) , and document these steps as test steps (and/or as part of your product documentation, if this is also part of your responsibility).
There are a few online companies that offer many devices (Apple, Android, Google, Motorola, Nokia, etc..) configured in different versions (1.0, 2.2, etc..) of many platforms (Windows, Android, iOS), where you login to the test website, choose and connect to a device, load your app and run your tests. At times, performance can be issue when executing manual tests to a remote device, so this is where Automation testing is beneficial. I am not aware of any open source Automation testing frameworks, and those that are sold online are very expensive, so it will depend on your ability to pay and your level of knowledge of that software. Otherwise, you may be spending more time trying to learn the framework rather than actually testing. Automation testing will also need a very detailed set of test cases with detailed test steps (steps and expected results), which can be obtained in the initial phases of manual functional testing. Automation tools are evolving and each has their benefits (functional, load/performance, unit testing), so you'll need to know how to test your app, on what platform (versions and devices) are important/critical to testing your app, and what your test coverage will be.
Good Luck. Have fun during the process.
One more thing Kalees, the test steps you develop in manual testing can be reused to create your automation test suite as well. In this Forum, there are multiple discussions about Mobile Testing, and one thread discusses a software application for mobile testing...called SeeTest. You'll need to determine if it meets your testing needs as well, the level of complexity to use, and cost.
Mobile application testing- Its a process by which application software developed for mobile devices is tested for its functionality, usability and consistency.Now a days multiple mobile operating system are available in the market.The major ones are IOS, Android, Symbian, BREW, Symbian, Windows and BlackBerry etc.
Mobile application testing is very challenging as now a days we have variety of mobile devices to test with different operating systems. Even multiple mobile networks are present today and each network operator uses a different kind of network infrastructure and this limits the flow of information.
As devices are differ in input methods,menu structure,keystrokes and display properties. So we can say that a single script does not function on every device.
So the best thing we can do here:
1) First thing you need to ensure the priority of OS i.e. most widely accepted.
So according to the requirement of client be ensure on which country the particular application is going to be used most widely
Second thing you need to ensure the OS version and Devices and their versions on which application need to be test
Third thing In practical scenario it is not possible to test on all the devices due to devices unavailbility so it's better to take the help of any Tool like https://www.utest.com/mobile-app-testing
uttest is pretty good for testing tools.
Originally Posted by Poojagupta
Using manual approach or automated testing for Mobile applications depends on the kind of app you are testing. This also applies to web apps, for that matter.
Sometimes, manual testing might just be enough and automating it may not reap the desired results - so if you do the right ground work, you can take a wise decision whether to automate or stick to manual suite. Manual tests aren't bad - they’re critical to many QA workflows but the challenge most of the times is, teams can easily become over-reliant on them, which doesn’t scale well given how fragmented the mobile ecosystem is.
I can recommend UIAutomation tool.
You can test any iOS applications, including production builds. No need to compile additional libraries are required. You can run scripts from the console.
For basic app functionality testing, mobile emulators are quite effective, and also facilitate test scripting languages and simulated live environments.
The use of such emulators, however, does not negate testing on actual hardware. This is absolutely crucial to assess and understand the activity of a given app in real-time situations.
Beta testing, for instance, allows an application to be tested in the real world, across time zones and networks. This is of course better off on actual devices rather than on emulators.
The benefits of beta testing are that QA teams can evaluate variation in app behavior on different devices and operating systems, the way in which users interact with the app, the effect of app usage on battery life and OS performance, and the variations in network usage, both cellular and WiFi, that come about because of the app’s introduction on a particular platform.
Thanks for sharing information.
Originally Posted by Poojagupta