📺 Develpreneur YouTube Episode

Video + transcript

WebDriver IO - Part 1

2022-07-12 •Youtube

Detailed Notes

In this presentation, we are going to be talking about using the WebDriver IO: Building Automation Scripts using Javascript. Now, this is not really going to be a slide-driven presentation. Instead, we are going to go through the website and talk about the different technologies, and things you can do with WebDriver. Then, we're going to jump into a full hands-on example, building your first project, and looking at some of the different ways you can use WebDriver for testing.

In the past, I've talked about code test frameworks. Such as, topics about the different ways you can build your tests, and how you should test. Plus, we've talked about different things like unit testing, PHP testing, JUnit, every language, essentially own way of testing, and JavaScript's, no different. So open up the link below and enjoy the presentation.

WebDriver IO: Building Automation Scripts in JS Overview:

What is WebDriver IO How to build tests. The different types of frameworks it supports Reporting Hands-on Demo

Transcript Text
[Music]
welcome
thank you for joining us today today we
are going to be talking about using the
web driver io
to build automation scripts using
javascript
now this is not really going to be a
slide driven presentation today we are
going to primarily go through the
website talk about the different
technologies and things you can do with
webdriver
and then we're going to jump into a full
hands-on example building your first
project and looking at some of the
different ways you can use webdriver for
testing
let me jump out of here
so you can find webdriver io in the name
itself it is actually in
webdriver io
is the website so you can go to web
driver i o
and it basically is a next-gen browser
and mobile automation test framework for
nodejs
now in the past i've talked about code
test frameworks i've talked about the
different ways you can build your tests
how you should test
and we've talked about different things
like unit testing php testing junit
every language essentially has its own
way of testing
and javascript is no different
however with the difference here is a
lot of your javascript
tools that are out there for testing are
built on top of or around existing
frameworks that were built for other
languages like c and java
webdriver io is no exception so the
webdriver i o is actually built on top
of the selenium webdriver
so the
if you are a java house or ac housing
and you have a lot of backend developers
and you have a lot of core developers my
recommendation for you is to go look at
the selenium discussions i've talked
about
however if you are a javascript only or
front-end only shop where you're only
dealing with javascript html css things
of that nature you're going to probably
want something a little more lightweight
a little more friendly for your
development environment and for that i
would recommend looking at this web
webdriver io
webdriverio is real easy to get started
you just click the get started button
here and it walks you through setting up
your project and we'll get this in just
a second
but let's first talk about what is
webdriver io so webdriverio is a true
cross browser testing
javascript library that you can use
it is again wrapped around the selenium
webdriver so it
you can actually use it to test all the
different browsers like selenium
it follows basic web standards so again
it follows that webdriver protocol
you can use puppeteer you can use
different uh front-end tools
you can also interestingly enough with
webdriver i o you can actually go in and
interact with the chrome dev tools
protocol this actually comes from the
node.js libraries so this was kind of
neat that i liked with this
the other thing is it's a modern web
application so it's written in react
view and your sleeve and other
frameworks
so it works with those uh it also works
for running emulating on real devices so
you want to test mobile devices you can
use web driver i o
uh you can also use appian
but the other nice thing about this
webdriver io that i like is that it can
integrate with multiple different test
frameworks
uh and we'll take a look at that in a
minute but the thing is
web driver io is essentially a tool that
you can use
for javascript testing so if you use
node.js or our fernan
i recommend looking at webdriver io
so to get started
you essentially just need to do a few
things one you need to have node.js
installed
so the first thing you need to do is
come out here to node.js
and just make sure that you download the
current or the latest lts
version for your
operating system and then once you have
it installed you can test it by typing
node now i've already done this step so
i'm not going to do this again but if
you need to walk through installing node
again you can go back out to my react
native presentations where i actually
walk through uh using node.js for react
native
all right so we need node so we start
with node and then the other thing to do
is you just need to run
npm init
wdio for web driver i o and dot this
will install a default project
or it will install webdriver io into an
existing project or if you want to
create a new project you just do npm
init and the path to your project
so let's just do this real quick
so if i come out here to terminal
make this a little bit bigger
and let me go to my development
environment
driver
io environment
and the first thing i want to do is i
want to just build
uh or make my own project folder so
we'll do make directory
and we'll do uh example
two
all right so we'll go into our example
two folder
and then we will take that command that
they listed here
npm
space init space wd io space dot so this
will set up
web driver i o in the current folder
and hit enter
and the first thing it's going to do is
it's going to kick off
the web driver i o it's going to
download all package dependencies
and this takes about a minute or so
there we go so now it's running the
wizard and it's going to ask you a bunch
of questions
all right so the first thing you have is
you have a couple options so what's
interesting again is that web driver i o
is built
to work with multiple different
frameworks and multiple different tools
so you can run webdriver io locally you
can interact or interface it with
experti or ex very test saucelabs or a
browser stack
testing box or lambda test or some
different service
or if you have your own selenium cloud
you can choose that so we can go through
these i will say on my local machine
and then it also gives you the option of
building based on three
essentially javascript friendly test
frameworks mocha jasmine and cucumber
i'll take mocha by default but we're
gonna look at some different examples
of the projects that they have
in a minute so for now we'll just take
mocha
all right do you want to use a compiler
babel typescript
or no so
babel is really good it gives you kind
of that
type of head features that you can get
with visual code but i want to go ahead
and just use typescript because this
gives us a little bit more type ahead in
visual studio
okay and we're of our test located we're
just going to use the default dot slash
test
slash specs yadda yadda
and you want webdriver io to auto
generate some test files and this is the
beauty of web driver io you can get up
and running with a very simple test
project immediately so we'll say yes
and then do you want to use page objects
of course we do we love page options
page objects make our lives easier when
dealing with web pages now you don't
have to use page objects you can say no
however in this case i want to use page
objects
now wherever page jobs is going to be
located we're going to follow their
default example here
now
the last question is which reporter do
we want to use so
by default
webdriver gives you a whole slew of
options for creating reports so i'm just
going to stick with my typical junit
report
and select uh
spec
and you can go through and you can
actually select all of these
so you could do json cucumber
now i don't recommend doing all these
only do the ones that you really need
but just if you want to play around you
can and then once you're done you hit
enter
now
do you want to add a plugin for your
test setup and basically do we want a
wait for
or an angular component harness we
really don't want either so we'll just
hit enter for now
and then it's going to ask you uh which
service do you want your test set up for
and then we can select okay do we want
to test for chrome do we want to test
for
uh firefox edge saw slabs
moment here
so i want chrome driver to start with
and we'll take visual code
you can do appium browser stack firefox
profile cross browser testing
[Music]
lambdas docker
so you have all these different
integrations
which from a javascript perspective this
is awesome uh it really simplifies
things for you now with this being said
again this is really i recommend this if
you are more a front-end shop if you are
a back-end shop i highly recommend
maybe looking directly at using the
selenium webdriver with whatever unit
testing software you use like testing g
j unit php unit and so on all right so
we'll take chrome driver
and where's our base url we'll just do
localhost
you want to run npm install sure
and now we're installing all of our
packages
and almost done
perfect
so now we're done so now it's installed
your entire project and it set
everything up for you and it will
actually run so it tells you how to run
it so we do npm
run wd io
and it will take a minute to kick off
because it has to set everything up the
first time
it opens up the browser
and it logged into heroku and it logged
off and we're done
so that's how quickly it is to just get
up and running really
quickly
now we'll look at some more of this in
just a moment
so that is the quick and dirty that is
getting started
there are some other little pieces you
can do here so if you
have never used webdriver i o or
selenium or any web-based testing tool
they give you a whole lot of examples
here to work with so if you want to jump
in and look at what they've already
provided as boiler plates they have a
whole slew
of projects out here that you can go
through
and take a look at so if you have appium
there's an appian boilerplate you can
check out cucumber jasmine
web io with mocha
cucumber bdd
jasmine bdd so there are a ton of
projects out here to get you started
quickly so you don't have to go figure
out your project structure you don't
have to figure out your dependencies for
this it's all there
so that is
in a nutshell how to get started and
jump right in
now the next thing we're going to look
at are some of the concepts so we can
there are a couple different settings
you can do we can set it up for web
driver directly
or we can set it up to use the chrome
dev tools
there's some package apis in here which
if you're familiar with webdriver
it's the same essentially the same
options it's just a wrapper so you have
options modifier prototyping
standalone mode
multi-threaded mode things of that
nature
one thing that's new is since 2021 they
have disabled the sync mode or have at
least sunseted it because asynchronous
is primarily the way to go in the
angular world so with asynchronous mode
you have to use the a weights and this
has become standard practice in selenium
as well so this is nothing new
if you've used selenium before this will
look very similar to you as well
synchronous or synchronous mode
basically means you have to run the
entire test from beginning to end there
is no wait
it's going to come in here
you have to do pauses
uh so this is the old ugly stuff that we
had to do back when i was showing you uh
the test framework where we had to do
the thread pause to wait for some of
those ajax calls
well then uh
a group came out and decided hey why
don't we make life easier instead of
doing pause or which is uh thread unsafe
let's do something that's a little more
thread safe and that is using this await
and if you
use java there is an await
class that you can
include in your projects as well through
maven and i believe c also has this as
well
automation protocols well of course it's
the web driver protocol
you have to install the
drivers that you need so you have chrome
firefox microsoft edge internet explorer
and safari
the only thing i don't like about this
is you have to install the drivers
through the tool now
that's great
you can reinstall them as needed as they
get updated the only kicker i have with
this where i kind of like the
selenium version the java based version
better is that there is the web driver
manager project in git that allows you
to check out in
you go through the web driver manager
and it will let you choose the versions
that you want or it will always pull
down the latest version of the browser
web driver
at run time so you're always running the
latest and greatest
here you have to actually make sure that
you have the latest driver
for your particular testing so if you
if chrome comes out with a new version
you might need to reinstall or pull the
latest chrome product
uh auto weighting this is a neat little
feature so uh implicit versus explicit
weights kind of gets rolled out here uh
you can set timeouts wait for exists
find elements which is actually funny if
you go back to my framework uh test
framework that i built this is
essentially what i built into my
framework uh the implicit versus
explicit so it basically gives you the
ability to set the timeout or wait for
exists for particular elements so you
can set the timeout for the load time
for the page which is implicit and the
explicit weights are waiting for
specific elements
so the way they do it they just built it
all into one so wait for timeout
which is essentially the same kind of
method that i built into my test
framework so really wait for timeout you
just write a wrapper class around the
weights
in webdriver and it's really easy
however you could also use the a weight
with the asynchronous weight and you
could set up your properties this way
so just another simple way of handling
weighting
some different configurations you have
your driver binaries you can install and
configure
uh if you have to go through a proxy
they do support that
typescript setup so now you can for
autocomplete so remember i included this
this will help us for visual studios
this just gives you the type of head
feature so as you're typing
you can quickly hit enter and fill in
the gap so you don't have to sit there
and wait um
or have typos
babel setup
a babel is
just simple it gives you the nice
coloring presets
so you can use babel you can use
typescript you have options
uh web driver options this is the exact
so options are essentially the same as
the selenium web driver options so you
have all the different things that you
can set over here agents headers
webdriver io test runner specs
hooks your before or after all the
things that you have in selenium
webdriver you have here in webdav there
are essentially wrappers around the
actual selenium webdriver
application or i guess the runner
different guides so if you're not
familiar with selenium you've never used
selenium uh this is just kind of a quick
guide on how to look things up so you do
a weight
uh and what's interesting here is if
you're very familiar with using the
chrome
dev tools
you
Transcript Segments
1.3

[Music]

27.039

welcome

28.8

thank you for joining us today today we

30.96

are going to be talking about using the

32.88

web driver io

34.88

to build automation scripts using

37.12

javascript

38.64

now this is not really going to be a

40.879

slide driven presentation today we are

43.04

going to primarily go through the

44.8

website talk about the different

46.399

technologies and things you can do with

48.16

webdriver

49.68

and then we're going to jump into a full

51.6

hands-on example building your first

53.76

project and looking at some of the

55.84

different ways you can use webdriver for

57.44

testing

59.68

let me jump out of here

63.6

so you can find webdriver io in the name

67.04

itself it is actually in

70.84

webdriver io

74.159

is the website so you can go to web

75.759

driver i o

80.08

and it basically is a next-gen browser

82.64

and mobile automation test framework for

85.04

nodejs

86.799

now in the past i've talked about code

90.4

test frameworks i've talked about the

92

different ways you can build your tests

93.92

how you should test

95.84

and we've talked about different things

97.36

like unit testing php testing junit

100.799

every language essentially has its own

103.28

way of testing

104.96

and javascript is no different

106.96

however with the difference here is a

109.84

lot of your javascript

112.24

tools that are out there for testing are

114.96

built on top of or around existing

119.6

frameworks that were built for other

121.68

languages like c and java

125.759

webdriver io is no exception so the

128.319

webdriver i o is actually built on top

131.039

of the selenium webdriver

133.12

so the

134.56

if you are a java house or ac housing

137.76

and you have a lot of backend developers

139.44

and you have a lot of core developers my

142.4

recommendation for you is to go look at

144.959

the selenium discussions i've talked

147.2

about

148.08

however if you are a javascript only or

151.599

front-end only shop where you're only

154.239

dealing with javascript html css things

157.12

of that nature you're going to probably

159.2

want something a little more lightweight

162.319

a little more friendly for your

164.319

development environment and for that i

166.4

would recommend looking at this web

168.879

webdriver io

170.68

webdriverio is real easy to get started

173.84

you just click the get started button

175.44

here and it walks you through setting up

177.84

your project and we'll get this in just

179.92

a second

181.12

but let's first talk about what is

183.2

webdriver io so webdriverio is a true

187.2

cross browser testing

190.72

javascript library that you can use

192.959

it is again wrapped around the selenium

196.959

webdriver so it

198.4

you can actually use it to test all the

200.8

different browsers like selenium

204.4

it follows basic web standards so again

206.72

it follows that webdriver protocol

209.2

you can use puppeteer you can use

211.44

different uh front-end tools

214

you can also interestingly enough with

216.64

webdriver i o you can actually go in and

220.799

interact with the chrome dev tools

223.04

protocol this actually comes from the

225.519

node.js libraries so this was kind of

228.08

neat that i liked with this

231.04

the other thing is it's a modern web

232.64

application so it's written in react

234.799

view and your sleeve and other

237.04

frameworks

238.64

so it works with those uh it also works

241.36

for running emulating on real devices so

243.92

you want to test mobile devices you can

246.239

use web driver i o

248.879

uh you can also use appian

251.12

but the other nice thing about this

252.64

webdriver io that i like is that it can

255.76

integrate with multiple different test

258.32

frameworks

259.44

uh and we'll take a look at that in a

261.12

minute but the thing is

263.28

web driver io is essentially a tool that

266.96

you can use

268.88

for javascript testing so if you use

271.12

node.js or our fernan

273.919

i recommend looking at webdriver io

276.8

so to get started

279.44

you essentially just need to do a few

281.919

things one you need to have node.js

283.84

installed

284.88

so the first thing you need to do is

286.479

come out here to node.js

289.44

and just make sure that you download the

291.6

current or the latest lts

295.04

version for your

296.96

operating system and then once you have

299.199

it installed you can test it by typing

302.16

node now i've already done this step so

304.32

i'm not going to do this again but if

306.32

you need to walk through installing node

308.08

again you can go back out to my react

310.4

native presentations where i actually

312.96

walk through uh using node.js for react

315.919

native

317.6

all right so we need node so we start

319.6

with node and then the other thing to do

322.16

is you just need to run

324.479

npm init

326.44

wdio for web driver i o and dot this

330.479

will install a default project

333.52

or it will install webdriver io into an

336.4

existing project or if you want to

339.039

create a new project you just do npm

341.52

init and the path to your project

344.479

so let's just do this real quick

346.639

so if i come out here to terminal

350.16

make this a little bit bigger

353.84

and let me go to my development

355.36

environment

357.759

driver

358.639

io environment

360.319

and the first thing i want to do is i

362.319

want to just build

364.08

uh or make my own project folder so

366.639

we'll do make directory

368.479

and we'll do uh example

371.039

two

372.8

all right so we'll go into our example

374.96

two folder

377.12

and then we will take that command that

379.199

they listed here

384.4

npm

385.52

space init space wd io space dot so this

389.759

will set up

391.039

web driver i o in the current folder

394.639

and hit enter

397.759

and the first thing it's going to do is

399.36

it's going to kick off

402.24

the web driver i o it's going to

404.24

download all package dependencies

408.88

and this takes about a minute or so

414.319

there we go so now it's running the

416.16

wizard and it's going to ask you a bunch

418.16

of questions

425.28

all right so the first thing you have is

427.199

you have a couple options so what's

429.68

interesting again is that web driver i o

433.12

is built

434.56

to work with multiple different

436.72

frameworks and multiple different tools

439.199

so you can run webdriver io locally you

442.24

can interact or interface it with

444.319

experti or ex very test saucelabs or a

449.12

browser stack

450.56

testing box or lambda test or some

452.56

different service

453.919

or if you have your own selenium cloud

455.759

you can choose that so we can go through

457.759

these i will say on my local machine

461.44

and then it also gives you the option of

464.479

building based on three

468

essentially javascript friendly test

470.96

frameworks mocha jasmine and cucumber

474.96

i'll take mocha by default but we're

476.56

gonna look at some different examples

479.199

of the projects that they have

481.199

in a minute so for now we'll just take

482.96

mocha

484.16

all right do you want to use a compiler

486.879

babel typescript

488.8

or no so

490.56

babel is really good it gives you kind

492.72

of that

493.84

type of head features that you can get

496.24

with visual code but i want to go ahead

498.16

and just use typescript because this

499.599

gives us a little bit more type ahead in

502.16

visual studio

504.16

okay and we're of our test located we're

506.96

just going to use the default dot slash

509.199

test

510.24

slash specs yadda yadda

513.919

and you want webdriver io to auto

516

generate some test files and this is the

518.24

beauty of web driver io you can get up

520.959

and running with a very simple test

523.12

project immediately so we'll say yes

527.2

and then do you want to use page objects

530

of course we do we love page options

532.24

page objects make our lives easier when

534.48

dealing with web pages now you don't

537.04

have to use page objects you can say no

539.36

however in this case i want to use page

541.76

objects

543.04

now wherever page jobs is going to be

544.88

located we're going to follow their

547.12

default example here

550.32

now

551.2

the last question is which reporter do

553.36

we want to use so

555.6

by default

556.88

webdriver gives you a whole slew of

558.959

options for creating reports so i'm just

561.839

going to stick with my typical junit

563.76

report

566.16

and select uh

568.88

spec

571.12

and you can go through and you can

572.399

actually select all of these

574.48

so you could do json cucumber

577.279

now i don't recommend doing all these

579.44

only do the ones that you really need

581.2

but just if you want to play around you

582.959

can and then once you're done you hit

584.8

enter

585.68

now

586.8

do you want to add a plugin for your

588.88

test setup and basically do we want a

591.839

wait for

593.12

or an angular component harness we

595.519

really don't want either so we'll just

596.88

hit enter for now

598.72

and then it's going to ask you uh which

601.839

service do you want your test set up for

604.72

and then we can select okay do we want

606.399

to test for chrome do we want to test

608.64

for

609.44

uh firefox edge saw slabs

613.839

moment here

621.68

so i want chrome driver to start with

624.079

and we'll take visual code

627.6

you can do appium browser stack firefox

630.399

profile cross browser testing

632.5

[Music]

633.839

lambdas docker

636.56

so you have all these different

638.24

integrations

639.36

which from a javascript perspective this

641.68

is awesome uh it really simplifies

644.16

things for you now with this being said

646.959

again this is really i recommend this if

649.6

you are more a front-end shop if you are

652.399

a back-end shop i highly recommend

656.48

maybe looking directly at using the

658.56

selenium webdriver with whatever unit

661.2

testing software you use like testing g

663.36

j unit php unit and so on all right so

666.64

we'll take chrome driver

668.24

and where's our base url we'll just do

670.16

localhost

671.6

you want to run npm install sure

676.959

and now we're installing all of our

678.32

packages

683.68

and almost done

686.959

perfect

689.2

so now we're done so now it's installed

691.68

your entire project and it set

693.92

everything up for you and it will

695.6

actually run so it tells you how to run

697.36

it so we do npm

699.44

run wd io

704.56

and it will take a minute to kick off

706.56

because it has to set everything up the

708.079

first time

710.32

it opens up the browser

712.56

and it logged into heroku and it logged

714.959

off and we're done

716.48

so that's how quickly it is to just get

718.32

up and running really

720.639

quickly

721.76

now we'll look at some more of this in

723.279

just a moment

724.48

so that is the quick and dirty that is

727.279

getting started

728.88

there are some other little pieces you

731.12

can do here so if you

733.04

have never used webdriver i o or

735.04

selenium or any web-based testing tool

738.88

they give you a whole lot of examples

740.959

here to work with so if you want to jump

743.36

in and look at what they've already

745.839

provided as boiler plates they have a

749.12

whole slew

750.399

of projects out here that you can go

752.24

through

753.36

and take a look at so if you have appium

756

there's an appian boilerplate you can

757.68

check out cucumber jasmine

761.44

web io with mocha

764.56

cucumber bdd

766.16

jasmine bdd so there are a ton of

768.639

projects out here to get you started

770.399

quickly so you don't have to go figure

772.32

out your project structure you don't

774.32

have to figure out your dependencies for

776.24

this it's all there

779.76

so that is

781.279

in a nutshell how to get started and

784

jump right in

785.68

now the next thing we're going to look

787.2

at are some of the concepts so we can

790.48

there are a couple different settings

791.92

you can do we can set it up for web

794.8

driver directly

796.56

or we can set it up to use the chrome

799.92

dev tools

804.399

there's some package apis in here which

806.32

if you're familiar with webdriver

808.56

it's the same essentially the same

810.399

options it's just a wrapper so you have

812.48

options modifier prototyping

817.36

standalone mode

819.839

multi-threaded mode things of that

821.839

nature

823.199

one thing that's new is since 2021 they

826.32

have disabled the sync mode or have at

828.72

least sunseted it because asynchronous

831.839

is primarily the way to go in the

833.76

angular world so with asynchronous mode

837.44

you have to use the a weights and this

839.839

has become standard practice in selenium

842.16

as well so this is nothing new

844.399

if you've used selenium before this will

846.88

look very similar to you as well

850.88

synchronous or synchronous mode

852.959

basically means you have to run the

854.24

entire test from beginning to end there

856

is no wait

857.279

it's going to come in here

859.519

you have to do pauses

861.6

uh so this is the old ugly stuff that we

863.839

had to do back when i was showing you uh

866.079

the test framework where we had to do

867.44

the thread pause to wait for some of

869.68

those ajax calls

872.399

well then uh

874.24

a group came out and decided hey why

876.48

don't we make life easier instead of

878.48

doing pause or which is uh thread unsafe

883.12

let's do something that's a little more

884.639

thread safe and that is using this await

888.56

and if you

890.399

use java there is an await

892.72

class that you can

894.24

include in your projects as well through

896

maven and i believe c also has this as

898.399

well

900.639

automation protocols well of course it's

902.48

the web driver protocol

904.32

you have to install the

907.36

drivers that you need so you have chrome

909.12

firefox microsoft edge internet explorer

911.36

and safari

912.48

the only thing i don't like about this

914.959

is you have to install the drivers

917.68

through the tool now

920.399

that's great

921.76

you can reinstall them as needed as they

924.079

get updated the only kicker i have with

926.8

this where i kind of like the

929.199

selenium version the java based version

931.68

better is that there is the web driver

933.92

manager project in git that allows you

937.36

to check out in

939.68

you go through the web driver manager

941.44

and it will let you choose the versions

943.759

that you want or it will always pull

945.6

down the latest version of the browser

947.839

web driver

949.36

at run time so you're always running the

951.92

latest and greatest

953.519

here you have to actually make sure that

955.279

you have the latest driver

957.6

for your particular testing so if you

960.56

if chrome comes out with a new version

962.24

you might need to reinstall or pull the

964.24

latest chrome product

968

uh auto weighting this is a neat little

970.48

feature so uh implicit versus explicit

973.759

weights kind of gets rolled out here uh

976.32

you can set timeouts wait for exists

978.72

find elements which is actually funny if

981.36

you go back to my framework uh test

983.92

framework that i built this is

985.6

essentially what i built into my

987.519

framework uh the implicit versus

990.56

explicit so it basically gives you the

992.56

ability to set the timeout or wait for

995.36

exists for particular elements so you

998.16

can set the timeout for the load time

999.839

for the page which is implicit and the

1002.399

explicit weights are waiting for

1004.24

specific elements

1005.839

so the way they do it they just built it

1007.759

all into one so wait for timeout

1010.48

which is essentially the same kind of

1012.24

method that i built into my test

1014.24

framework so really wait for timeout you

1016.88

just write a wrapper class around the

1018.399

weights

1019.279

in webdriver and it's really easy

1022.959

however you could also use the a weight

1025.28

with the asynchronous weight and you

1027.199

could set up your properties this way

1030.079

so just another simple way of handling

1032.319

weighting

1034.4

some different configurations you have

1036.16

your driver binaries you can install and

1038.799

configure

1040

uh if you have to go through a proxy

1041.679

they do support that

1043.679

typescript setup so now you can for

1046

autocomplete so remember i included this

1048.72

this will help us for visual studios

1051.2

this just gives you the type of head

1053.12

feature so as you're typing

1055.6

you can quickly hit enter and fill in

1057.52

the gap so you don't have to sit there

1058.799

and wait um

1060.64

or have typos

1063.12

babel setup

1066.48

a babel is

1068.96

just simple it gives you the nice

1070.72

coloring presets

1073.6

so you can use babel you can use

1075.2

typescript you have options

1077.52

uh web driver options this is the exact

1079.919

so options are essentially the same as

1082

the selenium web driver options so you

1084.799

have all the different things that you

1086.16

can set over here agents headers

1089.76

webdriver io test runner specs

1093.12

hooks your before or after all the

1096.08

things that you have in selenium

1098

webdriver you have here in webdav there

1100.16

are essentially wrappers around the

1103.28

actual selenium webdriver

1106.32

application or i guess the runner

1109.76

different guides so if you're not

1111.84

familiar with selenium you've never used

1113.52

selenium uh this is just kind of a quick

1116

guide on how to look things up so you do

1118.799

a weight

1120

uh and what's interesting here is if

1122.96

you're very familiar with using the

1125.28

chrome

1126.559

dev tools

1143.52

you