While there are a few different definitions of “ Local Testing ” that have appeared in late years, there is only one that is commonly accepted among developers and tester alike. At Sauce Labs, we define local examination as any test that is done on a developer ’ s/tester ’ s own machine. Similar to local ontogenesis, you execute your tests, whether they are automated or manual, locally as opposed to externally (i.e. on any hosted host or testing grid).

There are benefits to this coming - mainly the fact that you are able to quickly run unit tests to control the quality of your code, or run manual tests on your app for one-off issues that may arise in production. However, there are a few drawback to running your tests locally only:

• Older browser support = trim quality - sure, you may experience a couple of different browsers on your calculator. However, chances are that your customers are using browser that you don ’ t hold downloaded on your local machine. Additionally, many people may nonetheless be using different adaptation of browsers that you don ’ t get access to. This too use to operating system - your local machine is not able to account for all of the different versions of Windows and MacOS and their component to guarantee that your app works as expect. A lack of coverage across different browser/OS combinations means that local-only testing can not guarantee your app is to the caliber standards that your users expect.

• Testing becomes a chokepoint - say that you feature entree to every browser and operating scheme your user can admission your app from on your local machine. Problem solved, right? Not so fast! Even if you have the coverage, running tests from your local machine means that each of those test receive to run one at a time, even if they are automated. Serial testing significantly retard down the speed at which you can liberate new features to delight your user. And if you are work in CI/CD workflow, this intend that the intact build can be await on your tests to finish executing.

• No accountability for roving - over 50 % of the existence ’ s digital traffic is arrive from a roving device. And with the proliferation of hundreds of different device character across the Android and iOS work systems, testing through your local machine only can not account for this breadth, and the caliber of your app is at risk.

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

Local testing is valuable in certain scenarios, but if you want to deliver your applications at the hurrying and quality your users demand, it is imperative to execute your tests through an external test infrastructure. This can be in the form of a home-built grid with admittance to the respective browsers, operating systems and peregrine devices, or by outsourcing that infrastructure to a service like the Sauce Labs Continuous Testing Cloud.

Sauce Labs provides:

• The world ’ s bombastic cloud for continuous testing, with the industriousness ’ s most comprehensive coverage across different browser, operate systems and mobile device (both real devices and emulators/simulators)

• A highly scalable platform that allows you to execute your tests in massive parallel, decreasing your try clip by upwards of 10x, and decimate a mutual bottleneck to attain true CI/CD

• Tools that let you to fully understand the efficaciousness of your testing - such as videos, screenshots, log and full analytics to determine where gaps may exist

To learn more about how Sauce Labs can level up your testing,mark up for a gratuitous tryout today.