“Wirelessly pair multiple iOS and Android devices to your computer. Since then it has since been rebranded as Adobe Edge Inspect CC and requires a paid subscription to Adobe Creative Cloud for all the features. Adobe Edge Inspect CCĪ few years ago Adobe released a product called Adobe Shadow which was revolutionary as it was the first that easily allowed you to synchronise and remotely inspect your testing across multiple devices. Not only do we use it for testing on mobile devices, but we also use it for our regular desktop cross-browser testing as well. Ghostlab has lived up to its promise and is now an invaluable tool in our cross-browser testing toolkit. I haven’t had a device yet that Ghostlab couldn’t remotely inspect, however, I did try to use it to inspect desktop versions of Internet Explorer with no luck. To remotely inspect a device it’s as simple and double-clicking the device listed in the sidebar and then clicking ‘debug’. Ghostlab includes the Weinre remote web inspector that lets you inspect the DOM and debug JavaScript on any connected device. If a device has JavaScript enabled then Ghostlab can run on it. GhostlabĮarlier this year I came across Ghostlab and was immediately attracted to the product by their promise that it “synchronizes scrolls, clicks, reloads and form input across all connected clients.”Īvailable for Mac, Ghostlab allows you to connect any device (computer, tablet, smartphone, etc.) as long as you are on the same network. Products like Ghostlab and Adobe Edge Inspect CC solve this problem and help speed up testing with the added bonus of being able to remotely inspect and debug each connected browser. Synchronised testing is an efficient way to automatically perform the same action across a variety of browsers and devices simultaneously. Luckily there are some quality tools and techniques available to help alleviate the pain of developing and testing responsive websites, whether you own any testing devices or not. This means being signed in simultaneously on each device and simulating different scenarios. Due to the nature of the marketplaces, we want to focus on testing the same actions across a range of mobile devices and browsers. Since beginning our journey to responsive enlightenment, this testing process has become even slower and more complicated. Until recently we used a combination of Pow and xip.io on our development machines to serve the marketplaces to our testing devices and VMs. When developing the marketplaces we run multiple local development servers which makes normal cross-browser testing complicated. Reviewing your own mobile traffic data and researching device stats usage is a great place to start deciding which devices and browsers to support. We’re using traffic data and survey results to help narrow down the devices on which we focus our mobile browser support, so that the changes we make assist the bulk of our users. The ultimate goal is to deliver a consistent experience to users on a variety of devices and browsers. When testing mobile and responsive sites on mobile devices there are basic factors to test for. I’m going to take you through some of the options I’ve explored while setting up the cross-browser testing suite we use for the marketplaces, and some of the workflows and techniques that make us more efficient. We’re currently working on making the sites responsive, so having the right tools and cross-browser testing on a range of mobile devices is incredibly important. On the Envato Marketplaces we get over 16 million monthly visits, 6% of which are from mobile devices. Add in the ever-growing multitude of mobile devices now available, and it can be a real challenge developing your site to deliver a consistent experience to all. Not so long ago, cross-browser testing meant firing up different versions of Internet Explorer, Chrome, Safari, Firefox and (possibly) Opera on multiple operating systems.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |