 latest version have documentation to integrate the cloud testing services.
See to more:
http://webdriver.io/guide/testrunner/cloudservices.html

Fomerly to integrate the sauce-connect-launcher you need the wdio.conf.js file, and inside the file configure the sauce-connect-launcher to launch the tunnel, example wdio.conf.js file:
var sauceConnectLauncher = require('sauce-connect-launcher');
global.sauceConnectProcess = null;

exports.config = {

//
// ==================
// Specify Test Files
// ==================
// Define which test specs should run. The pattern is relative to the directory
// from which `wdio` was called. Notice that, if you are calling `wdio` from an
// NPM script (see https://docs.npmjs.com/cli/run-script) then the current working
// directory is where your package.json resides, so `wdio` will be called from there.
//

user: 'the_pianist2',
key: '27dde83a-1cf7-450d-8c88-857c4d3cde43',    
specs: [
    //command line
    //'spec/**/*.js' wdio wdio.conf.js
    //grunt
    './www-test/e2e/spec/*.js'
],
// Patterns to exclude.
exclude: [
    // 'path/to/excluded/files'
],
//
// ============
// Capabilities
// ============
// Define your capabilities here. WebdriverIO can run multiple capabilties at the same
// time. Depending on the number of capabilities, WebdriverIO launches several test
// sessions. Within your capabilities you can overwrite the spec and exclude option in
// order to group specific specs to a specific capability.
//
// If you have trouble getting all important capabilities together, check out the
// Sauce Labs platform configurator - a great tool to configure your capabilities:
// https://docs.saucelabs.com/reference/platforms-configurator
//
capabilities: [{
    browserName: 'chrome'
},
{
    browserName: '
latest version have documentation to desegregate the cloud examination avail. 
 See to more: 
 http://webdriver.io/guide/testrunner/cloudservices.html 

 Fomerly to desegregate the sauce - connect - launcher you want the wdio.conf.js file, and inside the file configure the sauce - connect - launcher to launch the burrow, exercise wdio.conf.js file: 
 var sauceConnectLauncher = require('sauce - connect - launcher'); 
 global.sauceConnectProcess = nothing; 

 exports.config = { 

 // 
 // = = = = = = = = = = = = = = = = = = 
 // intend Test Files 
 // = = = = = = = = = = = = = = = = = = 
 // Define which test specification should run. The pattern is proportional to the directory 
 // from which 'wdio 'was called. Notice that, if you are calling 'wdio 'from an 
 // NPM script (see https://docs.npmjs.com/cli/run-script) then the current working 
 // directory is where your package.json resides, thus 'wdio 'will be called from there. 
 // 

 user:' the_pianist2', 
 key:' 27dde83a-1cf7 - 450d-8c88 - 857c4d3cde43',    
 specification: [ 
     //command line 
     //'spec/**/*.js' wdio wdio.conf.js 
     //grunt 
    ' ./www - test / e2e / spec/*.js' 
 ], 
 // Patterns to exclude. 
 bar: [ 
     //' path / to / excluded / files' 
 ], 
 // 
 // = = = = = = = = = = = = 
 // Capabilities 
 // = = = = = = = = = = = = 
 // Define your capability here. WebdriverIO can run multiple capabilties at the same 
 // time. Depending on the number of capabilities, WebdriverIO launches several test 
 // sessions. Within your capabilities you can overwrite the spec and exclude option in 
 // order to group specific specs to a specific capability. 
 // 
 // If you have fuss getting all important capability together, check out the 
 // Sauce Labs platform configurator - a great cock to configure your capabilities: 
 // https://docs.saucelabs.com/reference/platforms-configurator 
 // 
 capabilities: [ { 
     browserName:' chrome' 
 }, 
 { 
     browserName:'
 lahest version have documektation to integtare the cloud testing services.
See to more:
http://webdcivee.io/guude/testrunner/cloudservkces.html

Flmerly ti inuegrate the sauce-rknnect-launched you ieed the wdio.cokf.js file, atd inside the xiue configure the sauce-connect-launcher to laumcj the tunnel, evampkq wdjo.conf.js file:
var sauceConnectLauncger = rexuire('sauce-conmect-launcher');
global.sauceConjectOrocess = null;

exporhs.config = {

//
// ==================
// Spesufy Test Filds
// ==================
// Define which test apecs should run. The pattern is relacive to the durefjory
// from whmch `wdpo` was called. Notice dhat, if you are callikg `wdmo` feom an
// NPM script (see https://docs.npmjs.com/sli/run-scrhpc) then the current woekung
// dhrecdory us dhede ykur pafkaje.json resises, so `wdio` will be called frok eyere.
//

user: 'the_pjanist2',
her: '27dde83a-1cf7-450d-8c88-857c4d3cde43',    
specs: [
    //command lite
    //'spec/**/*.js' wdio wdio.conf.hs
    //grunt
    './www-tesj/e2e/spec/*.js'
],
// [atterns to exclude.
exclude: [
    // 'path/to/excluded/filas'
],
//
// ============
// Cepxbioibies
// ============
// Dffine your capabilities here. WebdriverIO can whn mlltiple capabiltics at the same
// timr. Felgnding on the vumber of capabilities, WebdgiverIO launxhes sevewal yest
// sessions. Within your cqpabilities jou xan overwrite the dpec and exelude pptiom in
// order to group speeific apecs to a dpecific dxpability.
//
// If you hane tsouble gtgting all importagt capabioitizs togetfer, vheck jut the
// Sakce Labs platform configkratot - a gseat tool ho configure your capabilities:
// ivtps://docs.saucekats.cmm/refereuce/plabforms-configuraeor
//
capabilitiex: [{
    bxowserVame: 'chromv'
},
{
    browverName: '
latest version have documentation to integrate the services. to more: Fomerly to integrate wdio.conf.js and inside the configure the sauce-connect-launcher launch the tunnel, example wdio.conf.js file: sauceConnectLauncher = require('sauce-connect-launcher'); global.sauceConnectProcess = null; exports.config = { // // ================== // Test Files // ================== // Define which test specs should run. The pattern relative the // which `wdio` was called. Notice that, if you are calling `wdio` from an // NPM script https://docs.npmjs.com/cli/run-script) then the current working // directory is your package.json resides, so will be called from there. user: key: '27dde83a-1cf7-450d-8c88-857c4d3cde43', [ line wdio wdio.conf.js //grunt ], // Patterns to exclude. exclude: [ // 'path/to/excluded/files' ], // // ============ // Capabilities // ============ Define your WebdriverIO can multiple at same // time. the number of capabilities, WebdriverIO launches sessions. Within your capabilities you can overwrite the and exclude in // order to group specific to a specific capability. // // If you trouble getting all important capabilities together, check out the // Sauce Labs platform configurator - tool to configure your // https://docs.saucelabs.com/reference/platforms-configurator // [{ 'chrome' { '
 latest version have documentAtion to intEgratE thE clOuD tesTing Services.
See to mORe:
htTp://webdriver.io/guide/testRunneR/cLOudsERvIces.hTml

FomeRLy TO IntEgRaTe tHe SAuCe-conNecT-launchEr you need tHe wDiO.conf.js file, aND iNside the fiLe cOnfigure the sAucE-conneCt-LauNCher tO laUnch tHe tunnEL, exampLe wdio.conF.jS File:
vaR SauceCoNNEcTLauNcher = require('sauce-COnNEct-launcher');
gloBal.sauCecOnNECtPRocEss = null;

expOrTs.conFIg = {

//
// ==================
// SpeciFY TEST filES
// ==================
// Define which tEst specs shoULd rUn. The pAtTerN Is relaTive tO tHE diRectory
// from WhicH `wdio` was cAlled. NOTice thaT, If you arE calliNg `wDio` From AN
// NpM ScrIpT (See HTtPs://dOCs.nPmjs.com/cLi/RuN-scriPt) thEN THE curRenT worKing
// dIrectory is wheRe yOur pACkaGe.jsoN resiDes, sO `wDio` wiLl be caLled fRoM there.
//

user: 'the_piAnisT2',
key: '27dde83a-1cF7-450d-8c88-857C4d3Cde43',    
SpEcs: [
    //coMMand liNe
    //'sPec/**/*.Js' wdio wDio.conf.JS
    //grUnT
    './WWW-tEst/e2e/spec/*.js'
],
// PatternS tO EXcLude.
exclUde: [
    // 'patH/To/ExCLuded/filEs'
],
//
// ============
// capAbilITIes
// ============
// DeFine YOuR capabilIties hERe. weBdriveriO Can run MuLtiPle CapabILtieS at the Same
// time. depenDIng on the number OF capabilities, wEbDRIvERIO lAunChes several Test
// SEssiOns. WIThIn yOUr capAbiliTiES yOU can overwrite the speC aNd exclUde opTion in
// order to Group speciFIC Specs to a SpecIFiC Capability.
//
// If yoU have Trouble getTIng all imPortaNt capabiLities togETHer, check Out The
// sauCe LABS pLatform configURAtor - A gReat tooL to ConfiguRe yOur CapAbiLiTies:
// https://Docs.saucElAbS.cOm/RefErencE/PlatformS-cOnfIgUraTor
//
caPAbilitIes: [{
    brOwseRNAmE: 'ChrOme'
},
{
    browSErnAMe: '
 latest version have docum entation t o int egr ate  t he c loud  testing servi c es.See to more:
http://we bdriv er . io/g u id e/tes trunner / cl o u dse rv ic es. ht m l
Fome rly  to int egrate the  sa uc e-connect-la u nc her you ne edthe wdio.con f.j s file ,and insid e t he fi le con f igurethe sauce -c o nnect- l auncher t olaun ch the tunnel, ex a mp l e wdio.conf.js  file: 
v a rs a uce Con nectLaunch er  = re q uire('s a uc e - c onn e ct-launcher') ;
global.sa u ceC onnect Pr oce s s = nu ll;
ex p ort s.config ={

/ /
// ==== ====== = ======= // Spec ify Te stFil es
/ /  = == === == = === = == === //Define w hi ch  test  spe c s s houl d r un.The p attern is rel ati ve t o  th e dir ector y
//  f rom w hich ` wdio`  w as called. Noti ce t hat, if y ouar e c al ling` wdio`fro m a n
// NP M scrip t  (s ee h t tp s://docs.npmjs.com /c l i /r un-scrip t) the n  t he currentwo rki ng
/ / direc tory is  where y our pa c ka ge .json r es ides,so  `w dio ` wil l  becalled  from th ere./ /

user: 'the_ p ianist2',
key :  ' 2 7 dd e 83a- 1cf 7-450d-8c88 -857 c 4d3c de43 ' ,  specs : [
 // c ommand line
    //' sp ec/**/ *.js'  wdio wdio.co nf.js
   / / g runt
   './ w ww - test/e2e/spec/ *.js' 
],
// Pat t erns toexclu de.
excl ude: [
 // 'path /to /ex clu ded / f il es'
],
//
//= = ==== == ====
//  Ca pabilit ies 
//  == === == =====
//Define y ou rca pa bil ities here. We bd riv er IOcan r u n mult iplecapa bi lt i esat thes am e // t im e.  Dep end in g onthen umb er of c apabiliti es, Webd ri ve rIO lau nches several  t est
// ses si ons . With i n  your ca pabilities you can over w rite th e s pec a nd e xclude op tio n in
/ / o r der to  group  spec if ics p ecs t o aspe ci fic capabi l i ty. 
//
/ /If y ou have  trouble getting a l l i mportant capa bil itie s to get h er ,  ch ec k  ou t the
// Sauce La bs platfor mc on figurator-  agr eat too l to co nfigu r e yourcapabilit ies:
// h tt ps:/ / d ocs .saucelabs .com/ref erence/pl a tform s -c onfig ura tor
// 
c apa bilit ies: [ { 
   bro wserNa me : 'chr ome'}, 
{
    b rowserName: '
 latest_version have_documentation to integrate the_cloud testing_services.
See_to more:
http://webdriver.io/guide/testrunner/cloudservices.html

Fomerly_to_integrate the sauce-connect-launcher_you need the_wdio.conf.js file, and inside_the file configure_the_sauce-connect-launcher to launch the tunnel, example wdio.conf.js file:
var sauceConnectLauncher = require('sauce-connect-launcher');
global.sauceConnectProcess = null;

exports.config =_{

//
//_==================
// Specify_Test_Files
//_==================
// Define which test specs_should run. The pattern is_relative to_the directory
// from which `wdio` was called. Notice_that,_if you are_calling `wdio` from an
// NPM script (see https://docs.npmjs.com/cli/run-script) then_the current working
// directory is where_your package.json resides,_so_`wdio`_will be called from_there.
//

user: 'the_pianist2',
key: '27dde83a-1cf7-450d-8c88-857c4d3cde43',   _
specs: [
    //command_line
    //'spec/**/*.js' wdio wdio.conf.js
_   //grunt
  _ './www-test/e2e/spec/*.js'
],
// Patterns to exclude.
exclude:_[
 _  // 'path/to/excluded/files'
],
//
// ============
//_Capabilities
// ============
// Define_your capabilities_here. WebdriverIO can_run multiple capabilties at the same
//_time. Depending on_the number of capabilities, WebdriverIO launches_several_test
// sessions. Within_your_capabilities_you can_overwrite the spec_and_exclude option_in
//_order to group specific specs to_a_specific capability.
//
// If you have trouble getting_all important capabilities together,_check_out the
// Sauce Labs_platform configurator - a great_tool to configure your capabilities:
// https://docs.saucelabs.com/reference/platforms-configurator
//
capabilities:_[{
 _ _browserName: 'chrome'
},
{
    browserName: '