Have done a lot of searching and still not found a site that offers real-user testing across the range of browsers including Ipad 1,2,3 in a non-virtual or automated way.
We recently had a site that crashed Ipad 1 (the client's Ipad of course) but could not be replicated in any of the online services so we now want to send our completed websites out and get back a report that it works across IE 7-10, Chrome and all Ipad generations etc.
Does anyone know of such a service. As said, it must be on actual devices not virtualised one.
Thanks in advance.
Related
I am developing a web application with Meteor and WebStorm as IDE.
This application can be called from a PC, a tablet or a phone, which does not pose a problem of execution since it is called in the browser.
On the other hand problems appear, which are due to the size of the screen and the positioning portrait or landscape.
To test, a solution is to deploy the app, open it in the phone browser and see what works or does not work. A bit heavy ...
Is there a method to test a web application on a device connected to the development PC, through WebStorm, can be with an added package, or with another tool
Any leads or ideas would be welcome.
Thank you for your answers
YC
I have had a similar issue, I used Ghostlabs (https://www.vanamco.com/ghostlab/), to test different screensizes simultaneously. You will need to have physical devices present and connected to your development machine.
Saucelabs(https://saucelabs.com/) in my opinion is an extension of Ghostlabs, with the advantages of using the cloud.
One other tool I would recommend is Browser stack (https://www.browserstack.com/) it gives similar benefits as Saucelabs.
These tools I find are very effective for cross browser testing too.
I have got a DNN website and would like to test the site on multiple devices. I currently use Google Chrome, but it is not always as accurate. Is it possible to use Xamarin Test Cloud or any other software? My company do not want to spend money on a Device Board.
Have to tried https://www.browserstack.com.
It allows you to test the site across many devices and browsers but it does have some limitations. It only gives you a screenshot of the page and the page must be publicly view-able.
We have an issue where we have a website for test and an equivalent website for live. What we are finding is that due to carelessness our testers are using the wrong site (e.g. testing on the live site!).
We have total control over both sites, but since the test site is for acceptance testing by the users we don't want to make them different in any way. The sites must look the same and there is also a layer of management that will kick up a storm if the test and live sites are in any way different.
How have other people solved this problem? I am thinking of a browser plugin to make the browser look different somehow (e.g. changing the colour of the location bar when on the test website). Does anyone know of a plugin or a technique that would work? (We primarily use Firefox and Chrome)
Thanks,
Phil
UPDATE
We eventually settled on a program of: different credentials for the test and live site (this was not popular!) and making a series of plugins available for those who wanted them (colourize tabs for Chrome and Firefox users - we never did find a good plugin for IE).
Thanks to those who answered.
In our company we use different site's names:
www.dev.site.com - for developers
www.qa.site.com - for QA's
www.site.com - production site
Another good practic is to use different users credentials for dev\qa and prod sites.
I'm in the process of developing a Mobile version of some websites using the MVC4 *.mobile.cshtml system.
Everything is working great except when I try and view the sites on my HTC 8x. I get an outrageously large viewport, no javascript executing, offline touch regions and all-around incomplete pageload such that it doesn't function at all. I'm trying to diagnose/debug and not having any luck.
Using IE10 locally with a User Agent string for Windows Phone 8 doesn't show the same behavior. Further, using my exact UA string in any browser locally does not replicate the behavior. I've tried the various viewport workarounds posted on the internet and those have had no impact either.
I'm not on a Windows 8 machine, so I can't install the SDK/Emulator, but I suppose I could upgrade if no other options present themselves.
Anyone have any additional ideas as to how to test/diagnose/replicate this? I've been Googling for days and haven't been able to find any significant resource about this sort of thing.
This was a combination issue with Output Caching and the MVC DisplayModes bug.
I'm not really sure how to word this exactly, so hopefully someone can make sense of it. I've been working on an iPad app that syncs files from a server to your iPad and lets you build presentations with the various files. The corporation I'm working with on this app has a wireless network that requires you to re-authenticate every hour. So every hour instead of getting the expected JSON api response, any HTTP request pulls down the page needed to reauth with the wireless network. I was wondering is there is a specific HTTP response code related to getting sent that page or a "best-practice" way of testing for that page as opposed to JSON.
Granted I could just test to see if the response is HTML, but that doesn't account for other redirect responses that I haven't found yet. I could just test part of the HTML to see if it matches a predetermined portion of the html, but I'm an outside contractor. I can't guarantee they won't change the markup or verbiage of the page after I've made my deliverable.
So does anyone out in the ether know a "best practices" methodology for testing if the app needs to reauth before syncing?
I noticed that on Mac OS X and maybe even iOS, when you connect to a new Wi-Fi network, it will try to contact www.apple.com. This is being done to check if the internet connectivity is available. If it's not available, the Captive Network Assistant will pop-up, showing you the authentication page, or sometimes when I'm in Starbucks, an advertisement.
Following your question, since Apple themselves is doing it this way, I think you could check for HTTP response code, look for something in the HTML markup (slightly discouraged though) or trying to connect to a known server (Reachability).
For a corporation practicing well-documented projects, I am quite sure they won't be changing things without making sure that your app, once deployed will continue to work.