I have no up to date mobile phone personally, and we don't have any in our team to allow us to test mobile versions of our ASP.Net websites.
We have now been asked to provide a mobile version of our website (which is a fairly busy site) but I have no means to check the mobile pages.
Any suggestions? Are there emulators or would it better to have the real thing?
It's always better to have the real thing, but if that's not an option, I have used a plugin for FireFox called "User Agent Switcher"
Another route you could go is to get the Android SDK and load up an emulator. It runs a full version of android, so you could open the browser from there (You could also change screen size/device type) - a little more heavy than the first solution, but potentially another route worth exploring.
You can use simulators/emulators - Android, iPhone etc.
Well Apple provide an iOS emulator, which you can download in the developers section of Apple's own website.
Outside of that, the only other testing environment I'm aware of is Ripple, which is a plugin for Chrome, designed to emulate a range of mobile devices. You can find that at: http://ripple.tinyhippos.com/.
As others have answered there is a lot of different tools to do the testing and that is all fine to a certain extent, for daily testing by developers and testers.
But with 15 years of testing behind me I would never let the site go untested with a few different real devices if the site is an important service - usually this can be done with "staff" phones at no cost if the cost is the problem. I would more or less say; can your company live with publishing a site out there and there might be a risk it won't work on some mobile platforms?
DeviceAnywhere is the tool that we have used a lot. It provides you access to numerous mobile devices using which you can test both apps and websites. They have placed several physical devices which you can see and operate remotely.
It is always better to test on real devices instead of emulators. During development phase, emulators are helpful but for final delivery it is best to test on real phones. Mobile web browsers may or may not support HTML,CSS,JS completely and their individual implementation could be different.
Related
We are using webspeech(https://www.drupal.org/project/webspeech) module for text-to-speech in one of our project. Basic functionality is working fine. But when we open this site in mobile devices (samsung, apple, sony) TTS feature is not working and no error is also being displayed.
We have tried to debug the problem but not able to do so.
Any help will be much appreciate.
If you read the module requirements it says specifically
Flash 9+ is required on client web browser. Modern browsers those
support HTML5 may also work but not guaranteed.
I see you opened an issue with the maintainer, which will probably be your best source of information, but it looks like you might be hit or (mostly) miss on mobile devices for now.
I need to put together a mobile version of my site, but I don't have
an iPhone, all I have is this MacbookPro w/Lion, 17-inch.
All I have is this laptop. How do I go about building a mobile
version of my site? I'm looking for general suggestions; thanks.
There are numerous tools, like https://developer.mozilla.org/en-US/docs/Tools/Responsive_Design_View that help you emulate mobile browser.
There are some really good mobile emulators to help you developing a mobile website:
http://iphone4simulator.com/
http://developer.android.com/tools/help/emulator.html
Using those emulators should enable you to design and develop a quite good mobile website.
An iPhone wouldn't be enough either. You would have to test many phones. :)
In general, you can do a lot of testing by making your browser window smaller. This will at least trigger the CSS media queries and you can test if they work.
There are also many tools online that either are almust full emulators, or are just sites that check for common errors. Take a look at 10 excellent tools for testing mobile sites.
This question has been asked before, but not this year - there is no concrete consensus and I know this is a hot topic. In addition, technology changes rather quickly, and the other questions seem to relate to only using the <input type="file>. I am looking for a more verbose modern way to handle these requests. Although I have been developing in ASP.NET C# MVC3, I have been looking into weather ASP.NET MVC4 Mobile will support mobile file upload. From what I have read, it does not, or it has not been covered in the new release notes.
http://www.asp.net/vnext/overview/whitepapers/whats-new
http://www.asp.net/mvc/tutorials/mvc-4/aspnet-mvc-4-mobile-features
From the research I have done jQuery-Mobile seems rather gimmicky.
http://www.parorrey.com/blog/jquery-mobile/file-input-field-uploading-using-jquery-mobile-framework-form-submission-with-ajax-disabled/
http://forum.jquery.com/topic/jquery-mobile-seems-to-clobber-ability-to-upload-files-via-forms
An example that was posted did not work on my iPhone, as the <input type="file" still existed and was therefore grayed out as inaccessible.
http://filamentgroup.com/examples/jquery-custom-file-input/
Another suggestion I have come across involves forcing the user to email the photo to a user-specific email which doesn't really appeal to me or the customers I deal with - this approach also seems like it could be vulnerable to security breaches.
IS there a way to do this that I have overlooked? How can I show a file dialog on a mobile device?
The Safari browser does not support file uploads. You can see this by visiting many of the mobile sites in the actual browser BUT the actual apps will allow this.
So if you are making a mobile web app that you wish to deploy as a native app, you can use phonegap as a layer to do this.
http://docs.phonegap.com/en/1.4.1/phonegap_file_file.md.html#FileTransfer
Also, it is supported in:
Android
BlackBerry WebWorks (OS 5.0 and higher)
iOS
Windows Phone 7 ( Mango )
I use jquery mobile in a production app and it works just fine. I don't do file upload with it; however, that isn't jquery mobile's job anyhow. JqueryUI has issues with its dialog and file upload as well. There are a number of scripts that help with that. I use ajaxfileupload: http://www.phpletter.com/Our-Projects/AjaxFileUpload/ there are better ones out there now though.
I digress. As far as mobile is concerned it is more useful to have camera features involved rather than pure fileupload. No one knows where they store things on their phones, which is part of the problem. For that case you may want to try phonegap. Try this: http://wiki.phonegap.com/w/page/18270855/Image%20Upload%20using%20JQuery%20and%20Python
Yes we can upload picture through mobile,
Face book is a live example for this.
It works for me on Android.
You can see how facebook does it here: https://m.facebook.com/home.php?refsrc=http%3A%2F%2Fm.facebook.com%2F&refid=8&_rdr
<input type="file" name="file1" data-sigil="photo-input" />
Try going to www.tinypic.com and uploading a photo. I can test on iPhone tonight.
This works fine on Android 2.2+. You can upload photos from your gallery or use the camera to take a new picture for uploading. Any other apps that expose similar behaviour like sound recorders, the camcorder and music apps will typically offer alternatives. If you have a good filesystem app installed this will normally allow you to upload arbitrary files.
On iOS, you have to use an app to upload files. Since this is such a glaring omission in this age of web apps, it is very likely this feature will be added in the next major release of iOS although that is likely a few months away still.
Try this:
<input type="file" accept="image/*;capture=camera">
This should be supported in most mobile browsers and should offer the user a chance to choose a local file (image) or one some modern devices even allow them to capture one in the process.
Hope this helps!
Use Phonegap to bridge the gap between client side libraries and native applications. While the client side libraries give a good handle and easy way to set UI things up, you can use the capability of phonegap to perform device specific operations like camera, scanning, call etc.
Mobile browsers in Android (pre 2.2 it seems) and iOS do not allow file system access. And when it does on Android 2.2+ it isn't full access - it is filtered via apps that hit the FS like Gallery or Music.
I need to setup a testing infrastructure to test combinations of cookies enabled/disabled, Sliverlight and Flash plug-ins enabled/disabled, and javascript enabled/disabled. For starters, I need to test on IE6, IE7, IE8, IE9, Chrome, FF 3.6, FF 4.0, Safari 5 and Opera 10 on their most likely OS.
Longer term, I get as close as possible to testing on every "relevant" browser including mobile devices. I'll also want to include testing IE, for example, on XP, Vista and Win 7.
Even if I pick a single OS per browser, I have more than 100 host setups. What tools or strategies can bring sanity to this process?
(My current thinking suggests that screenshots alone will not be sufficient. It could be that I can develop a basic smoke test which gives me some indication of a problem and is verifiable through screenshot alone.)
Have you looked at Selenium, specifically Selenium Grid? It's not going to cover every single one of your test setups, but it'll get you a lot of the way there.
Selenium Grid transparently distribute [sic] your tests on multiple machines so that you can run your tests in parallel, cutting down the time required for running in-browser test suites. This will dramatically speeds up in-browser web testing, giving you quick and accurate feedback you can rely on to improve your web application.
See also:
Which is the most comprehensive browser compatibility testing tool?
How to automate testing of a browser-based app?
https://stackoverflow.com/questions/2565505/whats-the-best-way-to-do-cross-browser-testing
All that said:
It really might not be worth testing every single browser/version/OS combination. Part of this is because, at least on desktop OSes, most variations will show up across browsers (and to a lesser extent, browser version), and have much less to do with the OS version.
Chances are that the users of your site will not have equally distributed browsers/versions/OSes. It's basically a case of the 80-20 rule: the majority of your users will be using the minority of browser/version/OS combinations. So, at least in the short term, you get much more for your effort if you focus on ensuring that the site works on only the most popular OSes and browsers.
I'd also expect that your site, like many mobile-friendly sites, has a separate mobile view (reduced JavaScript, less content per page, simpler CSS, etc.). In that case, you'd only need to test the mobile version on mobile browsers and OSes, and the full version of the site on desktop browsers/OSes.
Please take a look at the following tools:
Automated Testing Tools – TestComplete
Automated Testing Tools for Web Application Testing | Telerik
Is WML and WMLScripts are used anymore ? I remember writing WML apps with classic-asp on server-side and we used interact with phone functionality from client using WMLScript and WTAI and do some cool things like, adding phone numbers to address book, trigger a call from WMLScript and much more. I still miss those things. I really want to know if modern web-browsers on phone have replaced WML with rich HTML support.
I also found that one of the most active WML and WAP forum Openwave Developers of our time is now discontinued which is no less than a shock to me. The forum also provided a nice WAP development SDK for testing WAP gateway simulation and WAP-pages on openwave browser simulator. All of these is now not seem to be available.
BEFORE DOWN VOTING EXPLAIN WHY, IF IS JUST BECAUSE OF IGNORANCE THEN STAY AWAY.
It is not dead yet.
It is used by some POS systems such as POSWEB, I have been developing on it for years in conjunction to ASP.NET to generate dynamic WML cards or downloadable catalogs, receipts, etc.
APPI Tecnologia's POSWEB Solution
Also another similar platforms do exist such as VERIWEB which are intended for the same purpose. Also I heard about similar ported WML/WMLScript being used in compact network enabled devices such as food / groceries dispensers, traveling card machines, etc.
This implementations supports mostly of the WML/WMLScript standard however it usually integrates additional functionality (depending on the target device), such as Smart Card processing, Simetric and assimetric cryptography, flat and indexed files creation and so on.
WML is still alive and in use many modern browsers doses not supporting WML for example andoid browsers like Firefox, Chrome but Opera still support WML for mobile and for web browsers also.
WML is more friendly to old phones but xHTML MP is the future in mobile WAP sites.
I would say, it's becoming less and less common out there in the wild.
You might find the odd device coming through that only does WML, but the effort to support those few might not be your goal in which case starting at html should be OK.
The users of those older phones typically already accept that their phone isn't the best and can't do as much as other phones.
Check out 0.facebook.com! There's been some resurgence of WML interest among some companies, mine included after Facebook Zero. The idea is that much of the technology still used in the developing world utilizes old technologies like WML, and coding up modern pages in WML will increase access in the developing world.