Local Testing

Local testing allows you to test your private and internal servers using the BrowserStack cloud,
which has support for firewalls, proxies and Active Directory.
Local testing establishes a secure connection between your machine and our servers. This can be done in one
of two ways: Browser extensions, which are intended for Live, Screenshots and Responsive; or via
the binaries which is recommended for Automate.
Getting started
Note: Browser extensions are currently only available for Chrome 31+ and Firefox 22+ and work with Live,
Screenshots and Responsive. IE, Safari, Opera and Automate users can connect using the binaries.
Browser extensions
On clicking the Start local testing button, the extension will install itself on your machine. Alternatively,
these extensions are available at the respective Chromeand Firefox app stores. The Firefox browser extension
is digitally signed, identifying the publisher as BinaryLife Technology Pvt. Ltd., and asking your permission
to install itself.


Installation of the extension on Chrome

Installation of the extension on Firefox
Once the extension has been installed, a configuration popup opens up. Enter the local server host and port
information or select a local folder to test. View ouruse cases for more options.




On clicking the Finish button, a connection is established, and BrowserStack generates a link to the pages on a
remote browser. In the event that more than one server has been connected, each connection appears as a
separate link.
If the port number is not provided, a default port number of 80 is used. If the port number is present in the
URL, it will be extracted automatically. To test servers with SSL, check the HTTPS box. Once the option is
checked, you can enter a SSL port number that is independent of the HTTP port number. When the connection
is established, the HTTP and HTTPS connections appear as separate links.
Note: If the server is not running, the connection will not be established. To test servers that are not running,
please use the binaries instead.


Binaries
Use the steps below to setup a local testing connection or view our use cases for more help.
1. Download the appropriate file:
OS X (Lion, Mountain Lion, Mavericks)
Linux 32-bit
Linux 64-bit
Windows (Recommended for your system)
The binaries' download links are secure. The binaries are digitally signed, identifying the publisher as
'BinaryLife Technology Pvt. Ltd.'.
2. Navigate to the folder in which the file was downloaded.
3. Run the file from your machine with your access key - pYsqjKzUvK2zWcsGmzzs. Once the connection has
been established, you will see the 'Verified parameters, starting local testing' message on the terminal. Live and
Screenshots users can move to the browser, where a local testing session will have been initialized. Automate
users can start running tests after the local testing connection has been established.
OS X & Linux
Windows
Test an internal server
BrowserStackLocal.exe <KEY> host1,port1,ssl_flag,host2,port2,ssl_flag...

//Example:
BrowserStackLocal.exe pYsqjKzUvK2zWcsGmzzs localhost,3000,0
Test local HTML design files and folders
BrowserStackLocal.exe -f <KEY> "<full path to local folder>"

//Example:
BrowserStackLocal.exe -f pYsqjKzUvK2zWcsGmzzs C:\WAMP\htdocs\example
If the port number is not provided, a default port number of 80 is used. If the port number is present in the
URL, it will be extracted automatically. Once the connection is created, testing of local servers and files can
begin on the remote machine.
Configuration options
The following flags can be set to enable extra functionality for local testing using the binaries:
-v - Provides verbose logging. Set this flag to debug issues with connecting to local testing.
-f - Required to be set for testing a local folder.
-h - Display the help file for setting configuration options.
-force - Kill other running instances of BrowserStackLocal.
-onlyAutomate - Setup local testing only for Automate. When this flag is set, local testing using the binaries
cannot be used for Live, Screenshots and Responsive.
-skipCheck - Skip verification of the host parameters. Use this flag to establish connections to servers which
are not currently running.
-proxyHost - Hostname/IP address of the proxy server. If this flag is not set, the remaining proxy options are
ignored.
-proxyPort - Port for the proxy server. Defaults to 3128.
-proxyUser - Username for connecting to the proxy server (Basic Auth Only).
-proxyPass - Password for connecting to the proxy server (Basic Auth Only). If the -proxyUser flag is missing
or not set, -proxyPass will be ignored.
-version - Displays the current version of BrowserStackLocal.
-localIdentifier - Specify a unique identifier for each connection, while creating multiple local testing
connections.
Back to top
Use cases
Localhost
To test web server running on localhost:3000,
Browser extensions

Binaries
//OS X and Linux
./BrowserStackLocal pYsqjKzUvK2zWcsGmzzs localhost,3000,0

//Windows
BrowserStackLocal.exe pYsqjKzUvK2zWcsGmzzs localhost,3000,0
Internal or private server
To test an internal staging server running on staging.example.com,
Browser extensions

Binaries
//OS X and Linux
./BrowserStackLocal pYsqjKzUvK2zWcsGmzzs staging.example.com,80,0

//Windows
BrowserStackLocal.exe pYsqjKzUvK2zWcsGmzzs staging.example.com,80,0
HTTPS
To test a local web server running on localhost:3000 and HTTPS server running on https://localhost,
Browser extensions

Binaries
//OS X and Linux
./BrowserStackLocal pYsqjKzUvK2zWcsGmzzs localhost,3000,0,localhost,443,1

//Windows
BrowserStackLocal.exe pYsqjKzUvK2zWcsGmzzs localhost,3000,0,localhost,443,1
Content served from multiple servers
To test a web server running at https://staging.example.com with static images served from
assets1.staging.example.com and assets2.staging.example.com,
Browser extensions

Binaries
//OS X and Linux
./BrowserStackLocal pYsqjKzUvK2zWcsGmzzs
staging.example.com,80,0,staging.example.com,443,1,assets1.staging.example.com,80,0,assets2.staging.exam
ple.com,80,0

//Windows
BrowserStackLocal.exe pYsqjKzUvK2zWcsGmzzs
staging.example.com,80,0,staging.example.com,443,1,assets1.staging.example.com,80,0,assets2.staging.exam
ple.com,80,0
Subdomains
To test a web server running at dev.example.com, and two subdomains user1.dev.example.com and
user2.dev.example.com,
Browser extensions

Binaries
//OS X and Linux
./BrowserStackLocal pYsqjKzUvK2zWcsGmzzs
dev.example.com,80,0,user1.dev.example.com,80,0,user2.dev.example.com,80,0

//Windows
BrowserStackLocal.exe pYsqjKzUvK2zWcsGmzzs
dev.example.com,80,0,user1.dev.example.com,80,0,user2.dev.example.com,80,0
Configuration in hosts file
To test a web server running on localhost:3000 and a server with /etc/hosts configuration 192.168.0.201
api.example.com
Browser extensions

Binaries
//OS X and Linux
./BrowserStackLocal pYsqjKzUvK2zWcsGmzzs localhost,3000,0,api.example.com,80,0

//Windows
BrowserStackLocal.exe pYsqjKzUvK2zWcsGmzzs localhost,3000,0,api.example.com,80,0
HTML design folders
To test a local folder,
Browser extensions

Binaries
//OS X and Linux
./BrowserStackLocal -f pYsqjKzUvK2zWcsGmzzs <full path to local folder>

//Windows
BrowserStackLocal.exe -f pYsqjKzUvK2zWcsGmzzs <full path to local folder>
Warning: URLs generated for local folders can only be opened on BrowserStack remote machines. They are
neither accessible from your local browser, nor from any other machine.
Behind a proxy
Note: Browser extensions come with out-of-the-box support for proxies and firewalls and do not require any
additional configurations to be set.
To test web server running on localhost:3000,
Browser extensions

Binaries
OS X & Linux
Windows
Without authentication
BrowserStackLocal.exe <KEY> localhost,3000,0 -proxyHost localhost -proxyPort 3128

//Example:
BrowserStackLocal.exe pYsqjKzUvK2zWcsGmzzs localhost,3000,0 -proxyHost localhost -proxyPort 3128
With authentication
BrowserStackLocal.exe <KEY> localhost,3000,0 -proxyHost localhost -proxyPort 3128 -proxyUser user -
proxyPass password

//Example:
BrowserStackLocal.exe pYsqjKzUvK2zWcsGmzzs localhost,3000,0 -proxyHost localhost -proxyPort 3128 -
proxyUser user -proxyPass password
To test a local folder,
Browser extensions

Binaries
OS X & Linux
Windows
Without authentication
BrowserStackLocal.exe -f <KEY> "<full path to local folder>" -proxyHost localhost -proxyPort 3128

//Example:
BrowserStackLocal.exe -f pYsqjKzUvK2zWcsGmzzs C:\WAMP\htdocs\example -proxyHost localhost -
proxyPort 3128
With authentication
BrowserStackLocal.exe -f <KEY> "<full path to local folder>" -proxyHost localhost -proxyPort 3128 -
proxyUser user -proxyPass password

//Example:
BrowserStackLocal.exe -f pYsqjKzUvK2zWcsGmzzs C:\WAMP\htdocs\example -proxyHost localhost -
proxyPort 3128 -proxyUser user -proxyPass password
Tip: Port 3128 is the default. If a username is not specified, the password is ignored.
Behind a firewall or VPN
If your private server is behind a firewall or only accessible through VPN, all you need to do is set up Local
Testing. There is no extra configuration required; only ensure that your machine can access the private server.
For more information, contact support.
Whitelist BrowserStack IPs
If you are testing a server that requires IP whitelisting, set up a Local Testing connection. You only need to
ensure that your machine has access to your restricted server, since all requests are sent via that machine. Read
about other security aspects of local testing.
Disconnection/Duration of the connection
The connection between your machine and the remote machine remains open till such time as you explicitly
disconnect it, the browser window is closed, or you sign out of your BrowserStack account. The connection is
persistent, and even if you accidently close your browser tab, you can resume testing.
Security
Read through our security policies for testing sessions, local testing, application security and
privacy.
Remote testing session
Remote sessions establish a connection between your computer and the BrowserStack cloud, thus allowing
you to test your website on secure virtual machines. Each virtual machine is a fresh instance, restored to its
original settings, guaranteeing not only a tamper-proof environment, but also a consistent baseline for test
scenarios. Read more about our virtual machine security policies here.
To make testing as easy as possible, we use VNC protocol to transfer the data from your machine to the server.
This data is encrypted, so as not to be accessible whilst in transit. Also, there is no additional setup required on
the client end, since all the transacting takes place from within the browser itself.
In the event that you are testing from behind a firewall, BrowserStack does not require any special rules to
operate successfully. We use HTTPS and WSS, both of which are standard web protocols, allowed universally
by firewalls. Therefore, your existing security is left altogether intact.
Back to topLocal testing
Local Testing enables you to test local folders and internal servers. We use custom-designed Chrome and
Firefox extensions, with WSS (secure websockets) to connect your machine to the cloud. Websockets allows
extensive interaction between the client browser and the servers. To protect the privacy of transferred data
during the testing session, we use WSS exclusively. WSS uses SSL over port 443 for transport and therefore
only transmits encrypted data.
When testing an internal or local server, we forge a connection between the server you have specified, and our
virtual machines. The mechanism is set up to forward requests and responses back and forth, and nothing else.
Similarly for folder testing, the cloud only has access to the folder mentioned during the setup of the
connection. Our infrastructure cannot access anything else on your filesystem.
Learn more about local testing internals and security.
Back to topVirtual machines privacy and security
Each time a new testing session is created, the cloud assigns the user a pristine virtual machine. Our machines
are restored to their original states, which means they are stripped of their registry contents, caches are erased,
cookies are deleted, and all running processes are killed. Additionally, users do not have the privileges to
install any programs on the machines. Therefore, after the restoration process is complete, the virtual machines
are guaranteed to be tamper-proof. The advantage is that each time a test is run, the default settings are
restored, thus providing an ideal test scenario.
Once the restoration process is complete, the virtual machine is then put through a series of validation checks,
as a fail-safe mechanism. In the rare case that the virtual machine fails even a single check, it is taken off the
infrastructure altogether. The machines themselves are in a secure network, and behind strong firewalls to
present the safest environment possible.
At any given time, you have sole access to a virtual machine. Your testing session cannot be seen or accessed
by other users, including BrowserStack administrators. Once you release a virtual machine, it is taken off the
grid, and restored to its initial settings. All your data is destroyed in this process.
Back to topBrowsing data security and privacy policy
Our restoration mechanisms for virtual machines is stringent and extremely thorough, ensuring that even the
smallest scrap of browsing data is erased. This list includes the temporary cache of files, the browsing history,
any cookies generated during the testing session, passwords and other form data, logs of any kind, and all
downloads. We guarantee to our users that we do not have any mechanism to view or store their browsing data.
All data is wiped out from the virtual machines as soon as the session ends.
Back to topSecure hosting for virtual machines
BrowserStack partners with only with the best hosting providers across the globe, and our machines are
located in secure locations in the US, Europe, Singapore, and Australia. Our selection process is exacting,
focussing on excellent service records and established security policies.
Each service provider has implemented security with the view to protect all those using their cloud. Many have
had their security policies independently audited from an external authority, and have been certified under
major compliance regulators. One of our providers is AWS, and you can read more about their security here.
We ensure that the machines within the infrastructure are protected from ground up. Starting from physical
security, we constantly improve security policies as the threat landscape changes. Our priority is to protect the
integrity of your data, and guard against any service interruptions.
Back to topSecure storage of BrowserStack credentials
Your account information: username, logins, password, access keys, and account details, are stored in an
encrypted format on our systems. We use SSL to transmit information back and forth from our servers.
BrowserStack cannot view any of your credentials, so much so that if you lose your password, it must go
through the reset procedure for your account to be accessible again.
The same policies are applied to all payment details. We have partnered with the reputable credit card
processor - Stripe. You can read more about their privacy and security in their documentation.
Back to topAccess control systems
Our sophisticated Identity Access Management systems log every entry into the cloud infrastructure.
BrowserStack has limited access to client instances, therefore ensuring a completely secure testing
environment.
In addition to these mechanisms, we provide a role-based administration system for the user accounts as well.
There are 3 roles: owner, admin, and user; each with different permissions. The administrators of the account
(owner and other admins) can control user activity at will, even to the extent of prohibiting team members
from accessing products.
Back to topScreenshots and Automate log data
Any screenshots and Automate log data, generated during the testing sessions, is stored in a secure database on
our cloud. The access mechanism is highly encrypted and therefore, your data is only accessible to you, via
your BrowserStack account.


Browsers & Platforms
Browse our comprehensive list of available browsers and official mobile emulators.

Windows XP (32-bit)
o Firefox 3.0
o Firefox 3.6
o Firefox 4.0
o Firefox 5.0
o Firefox 6.0
o Firefox 7.0
o Firefox 8.0
o Firefox 9.0
o Firefox 10.0
o Firefox 11.0
o Firefox 12.0
o Firefox 13.0
o Firefox 14.0
o Firefox 15.0
o Firefox 16.0
o Firefox 17.0
o Firefox 18.0
o Firefox 19.0
o Firefox 20.0
o Firefox 21.0
o Firefox 22.0
o Firefox 23.0
o Firefox 24.0
o Firefox 25.0
o Firefox 26.0
o Firefox 27.0
o Firefox 28.0
o Firefox 29.0 beta
o Firefox 30.0 aurora
o Chrome 14.0
o Chrome 15.0
o Chrome 16.0
o Chrome 17.0
o Chrome 18.0
o Chrome 19.0
o Chrome 20.0
o Chrome 21.0
o Chrome 22.0
o Chrome 23.0
o Chrome 24.0
o Chrome 25.0
o Chrome 26.0
o Chrome 27.0
o Chrome 28.0
o Chrome 29.0
o Chrome 30.0
o Chrome 31.0
o Chrome 32.0
o Chrome 33.0
o Chrome 34.0
o Internet Explorer 6.0
o Internet Explorer 7.0
o Internet Explorer 8.0
o Opera 10.6
o Opera 11.1
o Opera 11.5
o Opera 11.6
o Opera 12.10
o Opera 12.14
o Opera 12.15
o Opera 12.16
o Opera 15.0
o Opera 16.0
o Opera 17.0
o Opera 18.0
o Opera 19.0
o Opera 20.0
o Opera 21.0 dev
o Safari 4.0
o Safari 5.0
o Safari 5.1

Windows 7 (32-bit and 64-bit)
o Firefox 3.0
o Firefox 3.6
o Firefox 4.0
o Firefox 5.0
o Firefox 6.0
o Firefox 7.0
o Firefox 8.0
o Firefox 9.0
o Firefox 10.0
o Firefox 11.0
o Firefox 12.0
o Firefox 13.0
o Firefox 14.0
o Firefox 15.0
o Firefox 16.0
o Firefox 17.0
o Firefox 18.0
o Firefox 19.0
o Firefox 20.0
o Firefox 21.0
o Firefox 22.0
o Firefox 23.0
o Firefox 24.0
o Firefox 25.0
o Firefox 26.0
o Firefox 27.0
o Firefox 28.0
o Firefox 29.0 beta
o Firefox 30.0 aurora
o Chrome 14.0
o Chrome 15.0
o Chrome 16.0
o Chrome 17.0
o Chrome 18.0
o Chrome 19.0
o Chrome 20.0
o Chrome 21.0
o Chrome 22.0
o Chrome 23.0
o Chrome 24.0
o Chrome 25.0
o Chrome 26.0
o Chrome 27.0
o Chrome 28.0
o Chrome 29.0
o Chrome 30.0
o Chrome 31.0
o Chrome 32.0
o Chrome 33.0
o Chrome 34.0
o Internet Explorer 8.0
o Internet Explorer 9.0
o Internet Explorer 10.0
o Internet Explorer 11.0
o Opera 10.6
o Opera 11.1
o Opera 11.5
o Opera 11.6
o Opera 12.10
o Opera 12.14
o Opera 12.15
o Opera 12.16
o Opera 15.0
o Opera 16.0
o Opera 17.0
o Opera 18.0
o Opera 19.0
o Opera 20.0
o Opera 21.0 dev
o Safari 4.0
o Safari 5.0
o Safari 5.1

Windows 8 (64-bit)
o Firefox 16.0
o Firefox 17.0
o Firefox 18.0
o Firefox 19.0
o Firefox 20.0
o Firefox 21.0
o Firefox 22.0
o Firefox 23.0
o Firefox 24.0
o Firefox 25.0
o Firefox 26.0
o Firefox 27.0
o Firefox 28.0
o Firefox 29.0 beta
o Firefox 30.0 aurora
o Chrome 22.0
o Chrome 23.0
o Chrome 24.0
o Chrome 25.0
o Chrome 26.0
o Chrome 27.0
o Chrome 28.0
o Chrome 29.0
o Chrome 30.0
o Chrome 31.0
o Chrome 32.0
o Chrome 33.0
o Chrome 34.0
o Internet Explorer 10.0
o Internet Explorer 10.0 Desktop
o Opera 12.0
o Opera 12.10
o Opera 12.14
o Opera 12.15
o Opera 12.16
o Opera 15.0
o Opera 16.0
o Opera 17.0
o Opera 18.0
o Opera 19.0
o Opera 20.0
o Opera 21.0 dev
o Safari 5.1

Windows 8.1 (64-bit)
o Firefox 16.0
o Firefox 17.0
o Firefox 18.0
o Firefox 19.0
o Firefox 20.0
o Firefox 21.0
o Firefox 22.0
o Firefox 23.0
o Firefox 24.0
o Firefox 25.0
o Firefox 26.0
o Firefox 27.0
o Firefox 28.0
o Firefox 29.0 beta
o Firefox 30.0 aurora
o Chrome 22.0
o Chrome 23.0
o Chrome 24.0
o Chrome 25.0
o Chrome 26.0
o Chrome 27.0
o Chrome 28.0
o Chrome 29.0
o Chrome 30.0
o Chrome 31.0
o Chrome 32.0
o Chrome 33.0
o Chrome 34.0
o Internet Explorer 11.0
o Internet Explorer 11.0 Desktop
o Opera 12.0
o Opera 12.10
o Opera 12.14
o Opera 12.15
o Opera 12.16
o Opera 15.0
o Opera 16.0
o Opera 17.0
o Opera 18.0
o Opera 19.0
o Opera 20.0
o Opera 21.0 dev
o Safari 5.1

Mac OS X Lion (64-bit)
o Firefox 3.6
o Firefox 4.0
o Firefox 5.0
o Firefox 6.0
o Firefox 7.0
o Firefox 8.0
o Firefox 9.0
o Firefox 10.0
o Firefox 11.0
o Firefox 12.0
o Firefox 13.0
o Firefox 14.0
o Firefox 15.0
o Firefox 16.0
o Firefox 17.0
o Firefox 18.0
o Firefox 19.0
o Firefox 20.0
o Firefox 21.0
o Firefox 22.0
o Firefox 23.0
o Firefox 24.0
o Firefox 25.0
o Firefox 26.0
o Firefox 27.0
o Firefox 28.0
o Firefox 29.0 beta
o Firefox 30.0 aurora
o Chrome 14.0
o Chrome 16.0
o Chrome 17.0
o Chrome 18.0
o Chrome 19.0
o Chrome 20.0
o Chrome 21.0
o Chrome 22.0
o Chrome 23.0
o Chrome 24.0
o Chrome 25.0
o Chrome 26.0
o Chrome 27.0
o Chrome 28.0
o Chrome 29.0
o Chrome 30.0
o Chrome 31.0
o Chrome 32.0
o Chrome 33.0
o Chrome 34.0
o Opera 11.1
o Opera 11.6
o Opera 12.0
o Opera 12.12
o Opera 12.14
o Opera 12.15
o Opera 15.0
o Opera 16.0
o Opera 17.0
o Opera 18.0
o Opera 19.0
o Opera 20.0
o Opera 21.0 dev
o Safari 5.1
o Safari 6.0

Mac OS X Mavericks (64-bit)
o Firefox 3.6
o Firefox 4.0
o Firefox 5.0
o Firefox 6.0
o Firefox 7.0
o Firefox 8.0
o Firefox 9.0
o Firefox 10.0
o Firefox 11.0
o Firefox 12.0
o Firefox 13.0
o Firefox 14.0
o Firefox 15.0
o Firefox 16.0
o Firefox 17.0
o Firefox 18.0
o Firefox 19.0
o Firefox 20.0
o Firefox 21.0
o Firefox 22.0
o Firefox 23.0
o Firefox 24.0
o Firefox 25.0
o Firefox 26.0
o Firefox 27.0
o Firefox 28.0
o Firefox 29.0 beta
o Firefox 30.0 aurora
o Chrome 14.0
o Chrome 16.0
o Chrome 17.0
o Chrome 18.0
o Chrome 19.0
o Chrome 20.0
o Chrome 21.0
o Chrome 22.0
o Chrome 23.0
o Chrome 24.0
o Chrome 25.0
o Chrome 26.0
o Chrome 27.0
o Chrome 28.0
o Chrome 29.0
o Chrome 30.0
o Chrome 31.0
o Chrome 32.0
o Chrome 33.0
o Chrome 34.0
o Opera 11.1
o Opera 11.6
o Opera 12.0
o Opera 12.12
o Opera 12.14
o Opera 12.15
o Opera 15.0
o Opera 16.0
o Opera 17.0
o Opera 18.0
o Opera 19.0
o Opera 20.0
o Opera 21.0 dev
o Safari 7.0

Mac OS X Mountain Lion (64-bit)
o Firefox 3.6
o Firefox 4.0
o Firefox 5.0
o Firefox 6.0
o Firefox 7.0
o Firefox 8.0
o Firefox 9.0
o Firefox 10.0
o Firefox 11.0
o Firefox 12.0
o Firefox 13.0
o Firefox 14.0
o Firefox 15.0
o Firefox 16.0
o Firefox 17.0
o Firefox 18.0
o Firefox 19.0
o Firefox 20.0
o Firefox 21.0
o Firefox 22.0
o Firefox 23.0
o Firefox 24.0
o Firefox 25.0
o Firefox 26.0
o Firefox 27.0
o Firefox 28.0
o Firefox 29.0 beta
o Firefox 30.0 aurora
o Chrome 14.0
o Chrome 16.0
o Chrome 17.0
o Chrome 18.0
o Chrome 19.0
o Chrome 20.0
o Chrome 21.0
o Chrome 22.0
o Chrome 23.0
o Chrome 24.0
o Chrome 25.0
o Chrome 26.0
o Chrome 27.0
o Chrome 28.0
o Chrome 29.0
o Chrome 30.0
o Chrome 31.0
o Chrome 32.0
o Chrome 33.0
o Chrome 34.0
o Opera 11.1
o Opera 11.6
o Opera 12.0
o Opera 12.12
o Opera 12.14
o Opera 12.15
o Opera 15.0
o Opera 16.0
o Opera 17.0
o Opera 18.0
o Opera 19.0
o Opera 20.0
o Opera 21.0 dev
o Safari 6.1

Mac OS X Snow Leopard (64-bit)
o Firefox 4.0
o Firefox 5.0
o Firefox 6.0
o Firefox 7.0
o Firefox 8.0
o Firefox 9.0
o Firefox 10.0
o Firefox 11.0
o Firefox 12.0
o Firefox 13.0
o Firefox 14.0
o Firefox 15.0
o Firefox 16.0
o Firefox 17.0
o Firefox 18.0
o Firefox 19.0
o Firefox 20.0
o Firefox 21.0
o Firefox 22.0
o Firefox 23.0
o Firefox 24.0
o Firefox 25.0
o Firefox 26.0
o Firefox 27.0
o Firefox 28.0
o Firefox 29.0 beta
o Firefox 30.0 aurora
o Chrome 14.0
o Chrome 16.0
o Chrome 17.0
o Chrome 18.0
o Chrome 19.0
o Chrome 20.0
o Chrome 21.0
o Chrome 22.0
o Chrome 23.0
o Chrome 24.0
o Chrome 25.0
o Chrome 26.0
o Chrome 27.0
o Chrome 28.0
o Chrome 29.0
o Chrome 30.0
o Chrome 31.0
o Chrome 32.0
o Chrome 33.0
o Chrome 34.0
o Opera 11.1
o Opera 11.6
o Opera 12.0
o Opera 12.12
o Opera 12.14
o Opera 12.15
o Opera 15.0
o Opera 16.0
o Opera 17.0
o Opera 18.0
o Opera 19.0
o Opera 20.0
o Opera 21.0 dev
o Safari 4.0
o Safari 5.0
o Safari 5.1


Apple iOS
o iPhone 3GS
o iPhone 4
o iPhone 4S
o iPhone 4S (6.0)
o iPhone 5
o iPhone 5S
o iPad
o iPad 2
o iPad 2 (5.0)
o iPad 3rd
o iPad 3rd (6.0)
o iPad Mini
o iPad 3rd (7.0)


Google Android (with Device SDK)
Cupcake (1.5)
o HTC Hero
Donut (1.6)
o Sony Xperia X10
Froyo (2.2)
o Samsung Galaxy S
o HTC Wildfire
o LG Optimus 3D
Gingerbread (2.3)
o Samsung Galaxy S II
o Samsung Galaxy Note
o Motorola Droid Razr
o Motorola Droid 4
o Motorola Photon 4G
Ice Cream Sandwich (4.0)
o Samsung Galaxy Nexus
o Motorola Atrix HD
o Motorola Razr
o HTC Evo 3D
o HTC One X
o Sony Xperia Tipo
Jelly Bean (4.1)
o Samsung Galaxy S III
o Samsung Galaxy Note II
o Motorola Razr Maxx HD
Jelly Bean (4.2)
o LG Nexus 4
Ice Cream Sandwich (4.0)
o Amazon Kindle Fire 2
o Amazon Kindle Fire HD 8.9
o Samsung Galaxy Note 10.1
o Samsung Galaxy Tab 2 10.1
Jelly Bean (4.1)
o Google Nexus 7


Opera Mobile
o HTC Wildfire
o LG Optimus One
o Nokia 5800 XpressMusic
o Samsung Galaxy S II
o Motorola Droid X
o Motorola Atrix 4G