►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
A
A
Okay,
going
to
the
live
broadcast,
my
screen
is:
live
I've
learned
to
test
that
out,
which
is
neat
so
today.
Yes,
first
of
all,
we
have
the
asp
net
core
to
1rc
one
release
announcement,
so
that
is
cool
this.
This
post
talks
about
the
what
you
need
to
do
to
upgrade
and
all
that
so
and
and
updates
for
tools
so
good
stuff.
We
also
have
Scott
Hanselman
big
post,
where
he
kind
of
talks
through
everything.
A
Maybe
we
will
cover
that
as
well
coming
up
but
yeah.
So
that's
that
is
equal
post.
The
videos
for
four
or
so
Hayfield
2018
are
up
so
I
had
the
best
luck.
If,
if
you
search
for
a
dotnet
or
for
asp
net
or
asp
net
core,
you
won't
see
some
of
them,
so
I
actually
had
the
best
luck
just
going
in
and
getting
the
dotnet
core
if
you
sort
by
top
rated
asp
net
core
comes
right
to
the
top
anyways,
because
it's
awesome
so
so
here's
some
of
the
top
top
overview
sessions.
A
We
have
the
Hanselman
and
hunters
overview
and
roadmap.
We
have
the
what's
new
in
asp
net
core
2-1
overview
from
dan
Roth,
and
we
have
the
signal
our
overview
from
Davian
phalloides,
so
a
lot
of
good
stuff.
So
there
is
that
this
this
is
pretty
cool.
So
this
is
an
update
for
cash
cow
to
work
with
dotnet
standard
and
asp
net
core
MVC.
A
So
the
this
is
one
we
had
covered
in
a
while
ago
before
before
I
came
into
a
CNET
core.
So
this
this
is
cool.
To
get
that
that
support,
though
we
we've
already
had
some
questions
in
the
chat.
If
we
had
some
blazer
stuff,
yes,
we
got
a
few,
so
low
hits
has
a
blazer
hacker
news
clone.
So
this
is
kind
of
neat.
This
is
an
example
of
creating
a
hacker
news,
client
going
through
getting
all
the
the
data
and
everything
from
from
hacker
news
and
source
code
available
on
github,
also
interesting
on
blazer.
A
This
is
just
something
I've
been
keeping
an
eye
on.
This
is
cloud
crate.
This
is
so
when
you
are
working
on
the
client
you
need.
You
know
a
you
need
to
store
data
on
the
client
and
there's
you
can
store
it
directly
in
session
storage.
This
is
kind
of
a
nice
library
that
is
storing
against
against
that
storage
and
has
kind
of
a
wrapper
over
it.
So
you
can
set
values,
retrieve
values
and
it's
pulling
those
the
saving
them
intestines
stored,
but
it's
a
nice
c-sharp
wrapper
on
top,
so
that
is
cool.
I
will
confess.
A
I
found
this
because
I've
been
watching
the
the
blazer
teams,
kind
of
what
they're
contributing
to
and
and
what
they're
working
on
and
I
saw.
Steve
Sanderson
had
contributed
to
this
figuring
some
some
interesting
things
going
on
there,
Nate
McMaster,
so
we've
talked
before
about
global
tools,
and
so
Nate
has
updated
some
things
on
dotnet
core
to
one
and
how
global
tools
are.
Are
working
there,
I
need
to
lock
on
so
this
is
frustrating
because
I
am
locked
on
me
and
this
stupid.
A
Okay,
alright
I
am
locked
on
me
again.
Let's
see
if
it
sticks
this
time,
so
dotnet
core
to
one
global
tools,
so
these
are
updates
for
for
the
2.1
release.
So
it's
exciting.
It's
a
lot
easier.
It's
it's
kind
of
it's
more
built-in
and
then,
as
far
as
actually
creating
and
troubleshooting
etc,
working
with
common
errors
and
workarounds,
etc
and
Nate
has
you
covered
their
good
stuff.
A
Alright
is
so
there's
been
two
projects
that
have
a
very
similar
name,
one:
it
was
asp
net
core
boilerplate
excuse
me
ASP
net
MVC
boilerplate,
so
this
has
been
recently
renamed
to
dotnet
boxed
and,
along
with
that,
Mohammed
Roja.
He'd
aside
has
included
some
cool
stuff
for
graph
QL,
so
we've
we've
had
some
recent
posts
on
getting
graph
QL
set
up
how
to
work
with
it.
This
is
really
nice
because
it's
a
template,
that's
got
it
included,
so
there's
a
graph
QL
server
built
in
there's
yeah.
So
a
lot
of
good
stuff
in
this.
A
This
is
definitely
something
where,
as
a
boilerplate
is
something
where
you
can
go
through
and
you
know
create
a
new
project
that
has
a
lot
of
cool
things
that
you
can
include
just
in
check
boxes,
you'll
see
all
the
cool
stickers
here.
You
know
for
things
like
Sarah
log
and
graph,
QL
and
n,
w
or
n
website,
etc.
Those
are
all
kind
of
included
there,
so
very
cool,
and
so
again
one
of
the
you
know
top
feature
top
announcements
here
is
the
the
name
update
so
dotnet
box.
A
So
Nate
has
updated
the
asp
net
core
book.
I
know
we've
talked
about
this
several
times,
but
this
is
a
big
update
where
we're
he's
he's
revised
it.
So
this
is.
This
is
exciting.
This
is
an
update
for
it
for
the
book
and
then
working
on
asp
net
core
two
one
updates
as
well.
So
this
is
a
free
book,
great
way
to
learn.
What's
what's
new
in
asp
net
core
and
finally,
Steve
Gordon
and
Steve
Gordon
is
digging
into
dependency
injection,
and
here
he's
talking
about
registering
implementations
using
delegates.
A
C
B
B
So
essentially,
if
you're
a
developer,
you
usually
like
to
write
tests
for
your
app
yeah,
mostly
because
it's
a
way
of
like
building
quality
and
because
that
allows
you
to
determine
or
detect
when
to
break
your
app.
When
you
do
a
change
or
like
have
confidence
that
you
haven't
broken
your
app
when
when
you
make
changes,
so
we
have
ways
of
doing
unit
testing
for
controller
space
models,
and
you
say
dad,
oh
I'm,
completely
mute.
Is
that
no
no?
B
Can
you
hear
me
I,
hear
you,
okay,
yeah,
I
didn't
know
for
a
second,
if
I
was
mute
anyway.
So
going
back
to
what
we
were
talking
about,
the
you
can
write
unit
tests
for
pages.
You
can
write
unit
tests
for
controllers
and
and
things
like
that,
but
there
are
things
that
are
hard
to
test
by
its
own
nature.
For
example,
how
do
you
do?
How
do
you
test
routing?
How
do
you
test
authorization
things
like
that?
B
So
essentially,
what
people
has
been
doing
so
far
in
many
cases
has
been
to
just
doing
plain
old
integration
test.
You
deploy
your
app
to
a
server,
just
stand
it
up,
and
then
you
do
send
HTTP
request
to
like
test
the
app
or
your
selenium
to
test
the
UI
so
well.
That
works
is
kind
of
like
a
big
barrier
to
to
go
right
there.
So
in
the
embassy
team
we
use
a
feature.
B
Well,
we
have
we
built
our
own
infrastructure
to
test
SP
Annette
core
application
on
sim
memory.
So
what
we
do
essentially,
is
we
boot
up
your
app?
We
initialize
your
app
in
memory,
and
then
we
give
you
an
X
to
the
P
client
instance
that
you
can
use
to
talk
to
your
app.
So
that
way
you
don't
have
to
deal
with,
deploying
your
app
or
like
standing
it
up,
setting
it
down,
turning
it
down
and
all
those
type
of
things,
and
what
that
allows.
B
A
So
this
is
plugging
it
kind
of
a
nice
mid
point
where
you're
not
dealing
with
all
the
the
things
of
like
selenium
and
setting
up
all
the
HTTP
requesting
and
all
that
stuff
which
you
don't
really
need
to
testing,
can
be
slower
and
can
be
kind
of
finicky.
But
you
are
testing
at
a
higher
level
than
just
calling
in
to
specific
functions
and
saying
if
I
call
this
function,
give
me
this
so
you're
able
to
test
out
your
you're
able
to
say
if
I
call
this
URL
I
would
get
back.
This
result.
B
B
A
B
A
A
A
A
B
A
B
B
C
B
It's
just
that,
like
it's
technical,
easier
to
do
it
from
the
command
line.
Okay,
I'm
gonna,
I'm
gonna
copy
paste.
These
things
cuz.
It
would
be
faster,
okay,
so
I'm
gonna
add
it
to
the
solution.
Then
I'm
gonna
do
the
same
thing,
but
I'm
gonna
create
an
extremely
project
called
a
sample
application
for
small
test.
I'm
gonna
put
in
under
there
a
test,
folder,
okay,.
A
A
B
So
that
will
open
my
solution
here,
so
we
can
do
the
net
restore
real,
quick
here,
just
to
make
sure
that
everything
is
right,
then
what
we're
gonna
do
next
well,
this
is
restoring.
Is
we're
gonna
go
to
the
app
and
we're
gonna
do
a
couple
of
changes
that
we
need
to
do
to
enable
a
differential
test
in
the
test
project.
So
the
first
one
is:
we
need
to
reference
the
web
SDK
and
then
we
need
to
reference
a
Microsoft,
SP,
Annette
carafe.
A
This
is
gonna,
be
so,
while
you're
typing
that
question
for
you,
it's
great
that
you
can
do
all
that
you
just
did
there
use
from
the
command
line
and,
using
you
know
using
CLI
instructions
is,
will
it
at
some
point
or
is?
Is
there
an
easier,
an
easy
way
to
do
this
from
visual
studio
like
if
I'm
in
Visual,
Studio
and
I
want
to
add
functional
testing
to
my
app?
So
what.
B
You
would
do
is
you
would
already
have
it
so
I'm,
starting
here
from
scratch?
I,
don't
want
to
think
that,
like
you
need
to
do
all
these
steps,
I
I
only
did
like
the
seven
first
step,
because
I
was
starting
from
like
an
empty
solution,
but
typically
you
will
have
your
own
app
and
all
that
stuff.
So
you
will
already
have
like
hey
I
went
through
the
new
project.
B
Dialog
and
I
created
my
app
and
then
you
would
hit
like
go
at
project
and
add
function,
add
unit
test
project
and
you
will
add
your
during
test
project
and
then
you
will
add
the
reference
from
the
unit
test
project
to
the
to
your
app
great.
Ok,
yes,
so
the
messiest
part
is
something
that
this
changing.
B
This
to
the
web
is
the
case,
something
that
you
will
have
to
to
edit
by
hand
most
likely,
but
in
the
future
we
plan
to
give
you
a
template
that
will
will
have
this
set
up
for
you
essentially,
so
that
you
don't
have
to
go
into
your
CS
program
and
do
stuff.
So
we
done
the
other
thing
that
we
need
to
do.
Is
we
to
reference
Microsoft's,
Bennett
core
and
we
see
the
testing,
and
this
is
version
2.1
0rc?
One
final.
D
C
B
A
B
Okay-
and
this
is
system-
it
is
to
be
okay.
So
now
we
should
be
good,
so
I'm
going
to
explain
to
you
guys
what
we
have
done
so
we're
using
X
unit
for
for
writing
or
functional
test,
but
you
can
use
any
other
testing
framework
of
your
choice.
We
are
making
use
of
class
pictures,
which
is
a
feature
on
X
unit
that
creates,
creates
an
app
or
creates
a
set
of
data
for
then
for
all
the
that
is
shared
among
all
the
all
the
tests
in
the
in
that
class.
B
So
the
first
thing
to
know
this
is
this
web
application
Factory.
So
this
is
the
type
that
we
use
to
essentially
allow
you
to
create
or
to
instantiate
your
app
in
memory,
and
we
asked
you
to
give
us
to
give
you
or
give
us
your
programming
or
like
your
entry
point,
and
in
that
entry
point,
we
are
going
to
be
looking
for
a
specific
method,
name
create
web
bus
builder,
which
is
here
that
has
that
this
exact
signature.
B
So
if
you
are
upgrading
from
2.0
to
to
2.1
you,
you
will
have
a
very
similar
method
called
build
web
host.
You
just
need
to
change
it
to
be
created
with
us
builder
and
and
call
build
in
your
main
in
your
main
method,
and
that
will
enable
us
to
essentially
bootstrap
your
app
in
the
same
way
that
it
gets
bootstrap.
When
you
run
your
app
with
f5.
A
Okay,
if,
if
there's
some
sort
of
and
you're,
probably
just
about
to,
say
the
answer
to
what
I'm
asking,
but
if
there's
something
special
I
need
to
do
when
I'm
starting
it
up
under
the
web
application
factory
like
say,
for
instance,
I,
don't
want
to
load
some
initialization
data
or
I
want
to
have
some
different
config.
Is
there
any
way
that
I
can
say,
hey
I'm,
running
under
functional
test
mode?
Do
something
different!
Yes,.
B
So
we
we
don't
have
a
specific
guidance
on
how
to
do
that
yet,
but
I
plan
to
to
put
something
out.
The
idea
is
that
this
is
a
starting
point
for
you
to
to
be
able
to
just
like,
create
an
app
and
write
a
functional
test
and
have
it
work,
but
when
you
are
doing
functional
tests
that
you
want
to
run
on
the
CI
and
things
like
that,
you
will
have
to
do
things
like
mocking
your
dependencies
and
things
like
that
and
we'll
see
that
in
a
demo
die
off
later.
B
So
the
idea
would
be,
for
example,
for
sealing
data,
and
things
like
that.
You
can
do
two
things.
You
can
either
mock
your
database
so
that
your
seed
data
gets
populated
into
your
test
database,
for
example,
or
you
can
just
use
any
of
the
other
extensibility
points
to
use
a
different
startup
or
to
change
your
start
out
to
have
a
section
dedicated
to
functional
test.
I
will
be
providing
more
details
on
that
later
on.
B
B
Perfect
so
then,
the
next
thing
that
we
need
to
do
is
we
need
to
declare
our
constructor
in
our
test
class,
and
we
just
need
to
to
passing
this
web
application
factory
as
a
parameter.
X
unit
will
take
care
of
of
initializing
the
class
and
passing
it
to
you.
So
the
only
thing
that
we
do
is
we
set
it
on
a
property,
and
then
we
are
ready
to
write
our
functional
test.
So
what
we're
gonna
do
is
in
our
functional
test.
We're
just
gonna,
create
a
client.
B
B
C
E
B
D
B
B
So,
for
example,
let's
do
routing
test
okay,
a
very
day
test
that
you
can,
that
you
can
do
to
like
sanity,
check
the
health
of
your
app
it's
just
to
like
hit
the
endpoints
and
see
what
they
get,
that
what
they
get
back
and,
and
that
can
that
can
tell
you
whether,
like
you're
miss
you
don't
have
like
the
right
route
or
like
the
the
route,
is
not
expecting
the
right
thing
and
stuff
like
that.
So.
B
B
C
C
C
A
B
B
The
next
thing
we
probably
want
to
see
is
some
authorization,
because
this
is
also
a
really
good
way
of
just
testing
that
you
have
secured
all
the
endpoints
that
you
carry
in
your
app.
So
what
we
can
do
is
I'm,
just
gonna
go
ahead
and
copy
it
from
my
demo
script,
because
I'm
tempting
Locke
too
much
and
I'm
just
gonna
copy
this
snippet
and
paste
it
into
our
test
class.
So
I'm
gonna
walk
you
through
what
this
does
so,
essentially,
what
we
are
doing
is
we
are
sending
a
request
to
a
protected.
B
C
B
Let
me
show
you
to
create
clients,
so
we
have
create
client
that
has
an
over
load
without
parameters
and
we
have
create
client
that,
like
has
this
overload,
that
takes
web
application,
factory
client
options
and
we
have
creative
old
client,
so
normally
you
would
use
create
client
and
create
client
gives
you
gives
you
an
HTTP
client
that
does
a
couple
of
things
for
you.
It
follows
redirects
automatically
and
it
handles
cookies
automatically.
B
If,
for
some
reason,
you
have
a
one-off
test
in
which
you
are
interesting
in
actually
in
a
redirect
or
or
doing
something
more
specific,
you
can
either
use
create
client
I'm
passing
some
options
like
the
base
address
to
use
where
to
handle
cookies,
how
many
resurrections
are
allowed
and
whether
you
want
to
like
redirect
or
not
or
if
you
need
full
control
of
your
client.
You
can
just
call
create
default
client,
and
this
will
give
you
an
untainted
client.
B
It
will
not
have
any
handler,
it
will
not
have
any
specific
behavior,
so
you
can
essentially
configure
anything
you
want
in
here.
So
if
you
need
to
add
an
extra
middleware
or
something
like
that,
you
can
really
easily
plug,
in
whatever
logic
you
need
to.
So
what
we
are
doing
in
this
case
is
we
are
using
this
create
client
method
and
we
are
passing
the
options
to
essentially
say
hey.
This
is
my
base.
Url
and
I
want
you
to
not
follow
redirects
automatically.
So
that
way
we
can
see
the
specific
redirects.
B
So
after
that,
we
use
our
trying
to
talk
to
the
to
go
and
try
and
access
the
money.
Ten
point
and
given
the
fact
that
it's
a
protected
endpoint,
we
should
expect
to
have
a
react
and
we
we
should
expect
to
have
a
redirect
to
the
to
the
account
login
page.
Ok,
so
if
we
run
this
test,
I
want
to
do
it
through
the
test.
Discovery
thing
apparently
I
need
to
rediscover
something
like
that:
I,
don't
really
know
how
to
do
it
refresh
and
see
that
refresh.
So
what
is
happening
right
now?
B
What
is
going
to
happen
realize
that
we're
gonna
see
that
endpoint
being
hit,
and
we
are
gonna,
see
that,
like
we
have
logging,
the
the
other
thing
that
you
can
do,
which
we
also
do
in
identity,
is
the
complete
opposite.
Make
sure
that
when
you
have
an
authenticated
user,
you
can
have
you
can
access
authenticated,
endpoints
so
well,
that
is
running.
Oh,
it
already
run
perfect.
B
So
yeah
your
test
worth,
we
are
going
to
go
to
a
more
complete
sample,
which
is
the
one
that
I
was
mentioning
before
we
are
going
to
show
you
on
glass
which
to
be
so
studio
for
this.
Is
we
have
the
same
application
here
then
that
we
just
built,
but
it
has
a
couple.
It
has
a
couple
of
extra
things,
so
we've
built
a
page
that
essentially
goes
to
to
your
github
profile.
B
C
B
C
A
B
So
let
me
show
you
a
bit
real,
quick
how
this
look
like.
So
this
is
just
like
a
plain
page:
it
has
a
roud
with
a
username.
It
has
a
form
so
that
you
can
introduce
and
send
your
username
to
the
server
and
then,
if
we
found
a
user,
we
just
show
it.
So
the
only
important
piece
here
that
I
want
you
to
remember
is
that
we
have
an
ID
here
for
the
user
logging
and
we'll
come
back
later
there
to
see
why
it's
important.
B
B
There
is
the
big
time
factor,
so
this
is
a
very
razor-like
or
very
thematic
idiomatic.
We
define
an
input
model,
we
have
a
username,
we
have
our
input
property
and
we
say
that
that
this
needs
to
be
bound.
We
have
our
client
property
and
we
have
our
github
user
so
on
or
get
requests.
If
we
don't
have
a
username,
if
we
have
a
username,
we
go
and
fetch
it.
B
If
we
don't,
we
just
like
render
the
page
and
on
post,
we
essentially
grab
the
user
name
from
the
input
and
redirect
to
the
redirect
to
the
page.
So
the
last
part
I
want
to
show
you
is
startup,
so
a
startup
just
has
the
default
SP
the
latest
under
stuff,
and
then
we
are
just
like
in
the
clients
and
in
the
base
address
and
and
answering
the
user
agent.
B
A
E
B
So,
for
for
those
type
of
tests,
we
I
really
don't
want
to
be
hitting
big.
You
have
API
we
want
to.
We
want
to
replace
those
services
with
something
with
some
sort
of
mode
that
allows
us
to
still
test
or
a
pin
to
end
but
half,
but
don't
have
to
deal
with
with
their
external
dependencies
avoid
some
flakiness.
Yes,.
B
Exactly
exactly
so,
I'm
gonna
show
you
something
that
that
I've
built
to
show
you
how
you
can
do
this.
These
three
things
go
on
like
get
the
page
based
email
send
a
form
based
on
that
HTML
and
then
get
a
new
page
back
and
be
able
to
query
things
on
that
page.
So
what
I've
done
is
I
created
a
couple
of
helper
methods
that
I
just
copied,
the
straight
from
whatever
I
have
in
identity
for
doing
functional
tests
and
what
we
are
using.
B
C
A
A
B
I
can
also
point
I
was
planning
to
show
you
guys
a
tour
around
how
we
tested
the
entire
identity
UI,
with
with
this
thing
and
a
bit
more
and
a
couple
of
other
patterns
that
we
built
on
top,
so
that
you
can
get
an
idea.
That
of
like
the
type
of
things
that
you
can
build
yourself
with
with
this
thing
with,
without
writing
that
much
of
a
that
much
infrastructure
code,
okay
and.
A
B
When
you
are
running
tests,
we
also
copy
the
Deaf's
file,
which
is
a
file
that
the
donut
framework,
the
Necker
utilizes,
to
figure
out
the
dependencies
automatically
for
you,
and
we
essentially
take
care
of
anything
that
you
need
to
run
an
app
an
MVC
app
in
memory
on
top
of
test
host.
On
top
of
that,
we
also
give
you
a
bunch
of
nice
list,
so,
for
example,
with
test
host,
you
can
just
create
an
SDP
client
or
create
a
handler
with
the
web
application
factory.
You
can
automatically
do
cookies.
B
You
can
do
the
radio
acts
which
are
things
that
they
are
not
trivial
to
do
by
yourself.
We
have
we
have
tests
in
in
in
some
of
our
reports
that
use
test
force
directly
and
are
way
more
complicated
and
way.
More
verbose
and
way
more
error-prone
to
write
than
with
this
thing,
because
we
do
things
like
parse,
your
cookie,
unlike
grab
a
value
from
the
cookie
and
pass
it
back
on
the
network
on
the
next
request
all
by
hand,
and
those
type
of
things
are
things
that
are
very
low-level
there
are.
B
C
The
I
think
the
test
shows
the
goal.
The
test
shows
mainly
is
to
wire
up
the
HTTP
stuff
in
HP
client
to
the
HTTP
stuff
in
the
a
snake
or
middleware
pipeline
like
to
get
those
two
things
to
Wed
together,
so
you
can
exercise
the
pipeline
entirely
and
it's
a
very
well
factory
piece
of
code
that
does
that
web
application
factoring,
however,
is
more
like
a
batteries
included
model
where
it's
like.
C
This
does
all
the
things
that
you
really
need
when
you
go
to
test
an
app
like
all
the
app
model
concerns
like
the
content
route,
like
runtime
compilation.
All
these
all
these
types
of
things
are
just
set
up
to
work,
so
it's
it's
test
host,
plus
plus
it's
the
it's
the
thing
that
just
does
all
the
stuff
that
you're
probably
going
to
want
to
do
anyway.
On
top
of
test,
though,
so
that
you
can
write
functional
tests,
yeah.
B
That's
a
great
way
to
put
it
okay,
so
I'm
gonna
gloss
over
the
details
of
the
helpers
that
I
have
here,
but
I
essentially
have
one
that
creates
a
document
and
I
think
it's
like
45
lines
complete
and
then
I
have
another
one
here
that
allows
you
to
to
send
HTTP
requests
based
on
a
on
a
form
element
Anna
on
a
button.
So
if
I
go
and
show
you
my
test,
this
is
my:
can
I
get
a
github
user?
B
C
B
So
that's
one
of
the
things
that
we
are
doing
here.
We
are
customizing
your
app
after
with
building.
So
what
happens?
Is
you
give
us
your
program?
We
find
that
create
web
host
builder
method.
We
call
it
and
then,
in
the
context
of
testing,
we
allow
you
to
call
more
methods
on
that
builder
so
that
you
can
customize
your
app
for
testing
without
having
to
go
and
explicitly
made
your
the
source
code
in
your
app
a
test
friendly.
B
So
in
this
case,
what
we're
doing
is
we're
calling
this
with
warehouse
builder
that
will
give
you
the
web
host
builder
and
we'll
create
a
custom
factory
or
a
custom
instantiation
of
your
app
with
the
customizations
that
you
have
added.
So
in
this
case,
we
are
just
calling
this
configured
test
services
method
that
will
essentially
allow
you
to
override
services
that
you
have
in
your
app
the.
C
B
C
B
That's
that's
the
magic,
so,
for
example,
if
you
need
to
reconfigure
options,
options
are
really
hard
to
reconfigure
because
like
if
you
have
an
option
here
and
then
you
have
an
option
here-
and
this
is
the
one
in
your
startup,
no
matter
what
you
said
in
the
option
here,
even
that
this
one
in
your
startup
is
registered
after
it.
It's
always
going
to
overwrite
the
one
that
you
put
in
your
test,
but
if,
instead,
you
move
the
setup
from
your
test
after
the
registration
in
a
startup,
okay.
C
B
B
B
B
So
in
this
case,
what's
gonna
be
happening
is
that
we
are
gonna,
say
we're
gonna
post
this
form
and
then
that
form
is
gonna,
protect
to
the
to
the
login
page,
and
then
we
are
gonna,
get
sorry
not
to
a
login
page
to
the
github
user,
page
with
a
specific
user
name,
and
then
we
are
gonna
get
the
debates.
So,
given
that
we
are
using
the
default
client
is
following
those
redirects
automatically,
so
you
can
think
of
you
can
think
of
it
as
follows.
You
introduce
your
user
name
on
the
page.
B
You
hit
the
button
and
then
you
get
the
new
page
with
the
additional
information,
and
that
is
what
is
happening
here.
We
get
the
page,
we
send
the
form
with
with
information
and
we
get
the
new
page
with
the
additional
information.
So
in
this
case,
when
we
get
the
response
back,
we
just
again
parse
the
document
and
then
we
say
hey.
B
Can
you
give
me
the
user
login,
the
user
logging
element-
and
this
is,
if
you
remember
before,
when
I
showed
the
sample
the
ID,
that
I
was
mentioning
that
was
specific
to
the
user
log,
a
that
was
the
container
for
the
user
login.
So
the
idea
is
that,
while
you
are
building
your
app
and
you're
testing,
you
should
like
find
some
way
of
identifying
these
things.
It
can
be
a
simple
as
an
ID,
but
you
can
find
other
schemes
and-
and
it's
really
after
you,
how
you
want
to
choose
to
do
this.
That's.
C
D
B
B
B
D
A
C
A
B
Burbage
so
honestly,
I
use
FeliCa.
This
test
function
test.
They
are
really
if
you
want
to
be
technical
integration
test.
The
way
to
think
of
it
is
as
a
pyramid.
So
you
have
unit
tests
that
test
the
function,
the
functionality
in
your
component
in
isolation,
okay,
you're,
testing,
a
method,
you're
testing,
a
property.
You
are
testing
just
one
thing,
then
integration
tests
are
things
that
range
between
like
testing,
how
two
components
work
together
to
testing
pretty
much
everything.
B
The
main
difference
that
I
make
between
integration
tests
and
functional
tests
is
that,
for
me,
functional
tests
imply
if
we
want
to
be
a
strict
imply
that
you
deploy
the
thing
to
the
server
and
you
test
it
with.
Whatever
clients
is
gonna
is
gonna,
be
talking
to
those
are
also
called
sometimes
end-to-end
tests,
but
in
general,
for
me,
I'm,
okay,
with
calling
this
type
of
in
memory
test
functional
test
because
you
are
essentially
or
you
are
essentially
executing
the
entire
pipe-laying,
except
for
like
the
network.
Unlike
your
dependencies.
B
For
authentication
testing,
I
haven't
show
it
here,
but
one
thing
that
you
can
do
is
when
you
are
testing
authentication.
You
are
typically
not
testing
authentication,
you
are
testing
authorization
and
what
you
want
to
know
essentially,
is
if
I
have
an
ID
of
some
sort
of
yeah
if
I
have
an
ID,
a
user
like
with
and
I,
have
an
action
with
like
these
attributes
or
these
requirements,
or
these
roles
will
I
be
able
to
hit
the
same
point.
That's
kind
of
what
you
want
to
know.
B
So
one
thing
that
you
can
do
is
you
can
build
your
own
testing
middleware.
Sorry,
your
own
testing,
authentication
middleware,
and
you
can
do
something
like
when
I
send
a
request
with
this
header.
Then
I'll
Fanta
gave
me
with
this
ID
with
this
with
this
principle,
and
that
way
from
that
point
on
the
rest
of
your
the
rest
of
your
pipeline
works.
That
way
for
doing
something
is
specific
with
with
OBC
or
else
I
would
have.
B
D
B
Okay,
exactly
and
what
I
was
mentioning
is
well.
What
you
can
do
in
the
context
of
a
test
is
instead
of
validating
the
token
on
doing
things
like
that.
You
just
change
the
authentication
middleware
to
say
here
is
my
test
authentication
and
it
can
have
a
scheme.
That
is
a
simple
as
like.
I
will
always
have
indicate
you
with
this
user,
or
something
like
that.
I
do.
C
Think
would
be
interesting
for
this
infrastructure
is
like
if
you
are
like,
building
an
open,
ID
Connect
provider
like
the
identity,
server,
guys
or
open
ID
dict,
or
something
like
that,
all
the
endpoints
that
they
have
I'm
sure
they
would
love
to
be
able
to
exercise
all
the
flow.
All
the
open,
D
Connect
flows
with
that
server
and
this
infrastructure
I,
would
think
would
be
ideal.
C
B
Deeper,
yes,
so
let
me
get
here
to
the
functional
test
in
identity
and
what
I'm
going
to
show.
You
is
something
that
I
built
on
top
of
this
testing
infrastructure
just
to
be
able
to
test
identity.
So
when,
when
building
test
for
for
the
UI,
you
typically
want
to
do
a
couple
of
things.
You
want
to
reuse
as
much
code
as
possible
and
there
will
be
a
lot
of
overlapping
between
whatever
your
your,
between
whatever
your
like
different
tests.
Do
so
you
kind
of
want
to
structure
the
cadena
in
a
different
way.
B
So
what
I
did
was
for
each
page
that
I
have
in
my
in
the
identity
UI
for
each
race
or
page
I
created
an
equivalent
test?
Page
okay,
so
I
have
a
bunch
of
infrastructure
code
that
I'm
not
gonna
go
into,
but
the
idea
the
idea
is
that
for
each
pace
that
you
have
in
your
app,
you
create
a
test
page.
That
is
the
logical
view
of
of
that
of
that
bracer
page
and
you
have
there
things
like
there.
B
You
have
the
things
that
you
care
about
like,
for
example,
what
actions
you
can
do
so
that
that
is
a
nice
way
to
to
essentially
abstract
the
important
things
on
the
page.
For
example,
I
want
to
click
this
login
button.
I
want
to
send
this
form
type
of
thing.
So,
for
example,
a
very
simple
page
is
this
index
test
page
that
I
have
here
and
it
just
gets
an
HTTP
client
and
it
can
get
an
index
document
and
Ana
context.
Class
I'm
not
gonna
get
into,
but
essentially
we
have
methods
like.
B
C
B
So
maybe
it's
clear
if
I
show
a
test
so,
for
example,
if
I
show
the
management
test
like
if
I
want
to
write
a
test
for
like
hey,
can
I
enable
two-factor
off
in
my
app
through
the
UI
yeah
I
essentially
have
what
I
call
user
stories,
which
are
the
flows
that
you
follow
in
your
app
or
the
journey
that
you
follow
in
your
app
to
accomplish
something
like,
for
example,
registering
a
user,
and
things
like
that.
So.
B
B
B
B
So
what
I'm
trying
to
do
I'm
trying
to
show
you
with
this,
is
essentially
how
you
can
like
structure
your
code
to
test
to
test
your
app
by
essentially
abstracting
the
logic
of
the
details
of
like
the
HTML
and
like
how
do
click
things
and
how
you
send
forms
into
this
test
pages
concept.
Then,
on
top
of
that,
you
can,
you
can
essentially
create
the
flows
that
you
follow
through
your
app.
So,
for
example,
create
app
go
to
the
index.
B
B
Enabling
two-factor
off
in
this
case,
you
can
reuse
all
the
code
that
you
use
for
when
you
were
testing
the
registration
and
then
say
now,
I
want
to
do
this
extra
step
or
or
this
extra
thing
and
yuria
solve
that
code.
Iii
do
get
that
this
is
a
bit
abstract
and
a
big
kind
of
like
too
much
two,
maybe
two
graphs
at
once.
I
just
want
to
like
give
you
kind
of
an
overview
of
what
what
we've
done
in
identity
you.
Why?
A
This
is
great
to
see
the
kind
of
progression
from
the
here's,
a
very
simple
hello
world
thing
that
you
started
with
up
through
more
complicated
and
then
here's
a
like
real
world.
This
is
how
you're
testing
complicated
scenarios
in
the
identity,
library,
and
so
this
is
scaling
all
the
way
up
to
that
yeah.
B
And
as
I
said,
like
I,
don't
have
a
lot
of
coding
here.
This
is
pretty
much
everything
that
I
have
to
to
test
my
app
I
one
last
thing
that
I
want
to
show
you
guys
is.
We
were
calling
this
create
web
host
builder
method,
but
you
can
also
just
extend
web
application.
Factory
and
maybe
I
need
to
like
up
my
font
of
it.
You
can
just
extend
web
application
factory
and
we
have
a
bunch
of
methods
that
allow
you
to
to
configure
extra
things
in
there.
B
So
you
can
like
configure
the
the
Whitehorse
builder
for
your
app
and
you
can
configure
the
client
and
things
like
that.
So,
for
example,
in
this
case,
I'm
setting
up
my
death,
the
clients
that
I
create
with
create
client
to
just
not
follow
redirects,
because
I
was
interesting
generally
in
following
the
entire
flow
yeah,
but
yeah
I.
Think
with
this.
This
is
all
I
have
to
show
you
guys.
A
B
B
A
A
A
Alright,
this
is
great,
so
thank
you
very
much.
I
think
this
is
really
useful
to
see
kind
of,
like
I
said
that
whole
progression
of
like
easy
enough
to
get
started
and
then
kind
of
built,
and
this
is
what
this
is
based
on,
what
you've
been
using
in
the
team.
So
it's
something
that's
it's
new
in
the
product,
but
it's
something
that
this
is
kind
of
an
abstraction
of
the
testing
infrastructure.
You've
been
using
for
a
while
correct.
B
So
yeah
we
have,
we
have
kind
of
like
battle-tested
days
of
it.
If
you
want
to
like
call
it
that
way,
we
just
like.
Essentially
what
we
did
is
we
grabbed
what
we
had
and
we
clean
it
up
with
providing
a
nice
API,
and
we
did
a
bunch
of
work
to
make
things
more
magical
so
that
you
didn't
have
to
to
do
a
bunch
of
setup
that
you
had
to
do
in
the
past
manually,
which
was
pretty
much
impossible
to
do.