What's the best practice for testing the performance of mobile sites in a realistic way?
I'm not interested so much about the collection of the metrics per se, but more about how to drive real devices (iOS, Android) from selenium (or other). Or to use simulators that have similar characteristics (emulating CPU and memory of the targeted devices).
At least for Nokia handsets, you have the Nokia Remote Device Access available. http://www.developer.nokia.com/Devices/Remote_device_access/
Not sure if the other manufacturers offer such a service with dev access on real devices on live networks.
I believe what your looking for is Selenium's built in AndroidDriver. It does exactly what you want:
Android WebDriver test can run on emulators or real devices for phone
and tablets.
Check out this link for more info
Edit: Here is the iOS driver
Good Luck!
Related
I wrote tests in Robot Framework with Appium. I test the same app on both Android and iOS.
I want to find out a cloud-based native mobile app testing vendor where (a) I can test the app on various mobile devices and (b) I could also run the tests in the cloud.
I am looking into perfecto, Kobiton and HeadSpin, which seem only to provide access to devices. Are there vendors that allow running tests in the cloud as well?
With BrowserStack you get to run your tests on 100% real mobile devices on our infrastructure via cloud.
While I cannot say about the others names mentioned, but with BrowserStack you can easily get access to 3000+ real devices which will help you to ensure your application is tested on a variety of different specification devices of various screen sizes and from different vendors.
With BrowserStack's devices you can easily switch between OS versions and other device specifications in a jiffy.
For more information and better understanding, try a demo here: https://www.browserstack.com/
I need to know the difference between Mobile Labs Device Connect and Perfecto Mobile. I don't see much links stating
is there any other differences? Kindly suggest me which one is the best cloud based testing tool.
Thanks
There are many differences between the 2 tools and vendors
1) Perfecto is the leading tool vendor around continuous quality solutions for mobile apps. It backs the solution with a robust mobile quality lab which offers various cloud models (Private Hosted or on premise, Public (top 100 devices always on!), and local devices connected (No hardware required).
2) Perfecto offers open APIs and large set of connection to leading tools (Selenium, Appium, Calabash, HP UFT, Microsoft, IBM, CA, Jmeter, Neotys)
3) Perfecto offers end to end life cycles solutions from manual, automation, performance and monitoring with easy scripting which works on multiple platforms and runs in parallel (in opposed to the MobileLabs only UFT solution which required serial execution)
4) Perfecto offers selenium remote webdriver solution for selenium users DIRECTLY from within the Eclipse IDE (this is the only solution in the market offering cloud connection from eclipse for selenium development). No evidence!! for mobile labs selenium solution
Thanks
i wanna test my game that uses google play services api(for realtime multiplayer). But i don´t have an android phone or tablet, i only use the emulator.
Is there a specific model of phone that i should buy to use google play services or will it work on any android device?
On emulators, there´s a "target name" called google APIS, so i was wondering about the device.
I have already made my game work on emulators, but even of ButtonClicker example, there´s a delay on the timer on one of the emulators and not on the other. Maybe i should try with a real device?
It will work on any Android phone (not Android compatible). Avoid devices like the Kindle Fire that are compatible, but not actually Android. If it has the Google Play app and it's running Ice Cream Sandwich or higher, you should be set.
The Nexus devices tend to be developer favorites, as they have no customization from carriers or manufacturers and are fairly cheap. Developer Editions would be a good alternative.
When building websites I commonly use tools such as Browsershots to ensure that my pages looks reasonably OK in the different browsers. I am however starting to get complaints about a heap of mobile browsers running on different portable devices.
My question is simply how do one best carry out mobile cross-browser tests ? (answers that does not require me to install a ton of different mobile emulators will be preferred).
DeviceAnywhere can do this, but not for free.
The answers are old.
Nowadays, there are many more options.
Check out "Browserstacks", or google for "alternatives to Browserstacks". Some services offer (paid) automation for testing across devices.
http://validator.w3.org/mobile/ will provide you with several good advices, but won't provide any mobile devices' screenshots...
I'm afraid Felipe's right, the only way to know how your website interacts is to do it yourself.
at first i thought with Titanium, i can develop for Mobile and Desktop over AIR on Desktop only, but a quick look at the AIR Site, i guess i am wrong.
Benefit from a consistent, flexible,
and visual development environment for
applications on multiple platforms and
devices such as smartphones,
smartbooks, tablets, netbooks, and
PCs.
so my question is are there any major differences of titanium over air that i shld be aware of?
if no, i guess now air maybe better documented and has the backing of a more recognized company? after working with titanium desktop for a while i felt abit helpless and the docs are not really helping much
There are a lot of subtle differences, of course, and there are advantages and disadvantages to working in either, but the largest difference is that Titanium can produce apps for the iPhone/iPad, and AIR can't (well, at least not conveniently).
AIR can produce iPhone apps that you can deploy using the ad-hoc provisioning, but you can't distribute via the app store.
I've got desktop apps on both and am making a mobile app right now. Titanium desktop will cut your dev time to 1/3 of the time you'll take jumping through AIRs various sandboxes and security measures. Best yet, the code I wrote for my Ti desktop app is all javascript with about 3 Ti API calls and can be taken anywhere. The AIR app is all mangled by the wild structure you have to use with AIR apps and 1 million api calls.
The downside to Ti desktop is the API isn't as fully featured, and the Ti team pushes 4 times as many updates for the mobile API as the desktop API. Also, you won't be able to port your app from desktop to mobile easily as they are two different structures and APIs.
That said, developing for iPhone and Android on Ti is the same exact process and that won't happen on AIR.
Lots to weigh, but for my money it's Ti over AIR.
Hope this helps.