►
Description
In this session we dived into writing fixtures to replace hard coded graphql responses in Frontend specs.
Thumbnail: AI-generated by DALL-E. Thanks DALL-E!
A
B
B
A
B
A
So
these
fixtures
are
a
bit
magical,
so
don't
don't
feel
bad
for
feeling
like
I'm.
Certainly
I'm
missing
something
because
you're
not
it's
it's
it's
actually
quite
magical,
so
that,
like
it
when
these,
when
these
specs
they
technically
get
run
by
rspec,
and
that
it
is
actually
gonna
be
the
name
of
the
fixture
file
that
is
going
to
output
the
graphql
response
to,
and
it
just
does
this
magically
behind
the
scenes.
So
it
is
quite
a
bit
of
magic
that
happens
here.
I
think
let's
follow.
B
A
A
It
was
just
targeting
the
jobs
controller,
so
miguel
took
it
upon
himself
to
say
no,
the
top
scope
is
jobs,
but
then
we're
going
to
have
an
inner
describe,
that's
doing
the
jobs
controller,
and
I
bet
if
you
scroll
down
you'll,
see
something
about
the
graphql
or
something
yeah.
If
you
keep
going
down,
these
changes
won't,
be
probably
won't
be
that
nice
yeah
and
then
we're
going
to
describe
the
query
and
here's
all
the
stuff
we
need
for
the
quarry
and
like
this
is
actually
new
stuff
that
we're
adding
okay,
so
yeah.
A
A
A
A
B
B
B
A
Yes,
but
I
am
now
noticing
that
this
describe,
we
might
want
to
add,
we
might
want
to
add
the
top
line
similar
to
not
this
one,
but
the
one
that
miguel
had
where
he
had
just
a
string
on
that
top
level
described
yeah
yeah
from
line
one
to
five.
Let's
have
that
be
our
or
actually,
let's
include
all
the
way
to
eight
one
to
eight
that
should
probably
be
the
top
of
the
file,
probably
not
the
api
helpers.
We
won't
need
that,
but
yeah
yep
okay.
A
So
I'm
pretty
sure
if
we
did
look
at
the
other
fixture
files,
we'll
see
that
we
need
this
javascript
fixtures
helper
and
because
we're
doing
these
graphql
methods,
I'm
pretty
sure
that
implies
us
needing
this
graphql
helper.
So
we
could
look
at
other
examples
that
do
that,
I'm
pretty
sure
we
won't
need
api
helpers,
so
we
can
get
rid
of
line
six.
A
B
B
A
A
Yeah,
but
I
think
it's
I
think
it's
good
to
bring
it
up,
because
I
think
the
way
we
do
these
fixtures
might
be
different
because
there's
so
much
magic
going
on
like
it
might
be
faster,
maybe-
and
it
might
require
us-
also
doing
a
very
special
way
for
those
certain
shared
global
variables
to
get
filled
like
so
I
I
I
really
don't
know
so
when
it
comes
to
the
fixtures.
I
I
copy
a
lot
of
what's
already
there.
A
A
A
A
B
A
A
B
A
A
A
A
A
A
A
B
A
B
A
B
A
A
A
A
B
B
B
B
B
B
A
A
B
A
B
A
B
A
A
B
B
A
B
I
mean
the
way
the
way
ruby
works
is
there's.
You
have
a
class
like
the
the
item
class
and
then
you
just
whatever
include
you
do
applies
on
top
of
that
and
overwrites
and
the
last
thing
wins.
So
if
you
have
multiple
methods
to
find
in
multiple
modules,
the
last
sequential
one
is
going
to
win
interesting.
A
A
B
A
B
A
B
B
B
A
A
A
A
B
A
B
B
B
B
A
A
A
A
A
A
B
B
A
A
B
A
B
A
Maybe
but
right
now
the
project
is
being
null
and
that's
that's
concerning,
because
it's
like
the
that's
the
main
issue
doesn't
have
to
do
previously.
It
wasn't
null.
It
was
finding
this.
So,
let's,
let's
just
do
this
if
you
go
to
on,
let
me
try
this
and
then
we'll
do,
let's
add
a
before
after
the
let
it
be
sorry,
after
all
the
let
it
bees,
let's
just
do
it
before,
do.
A
B
B
A
B
A
B
A
B
A
B
A
B
A
B
A
A
You
go
to
I'll
lead
you
to
there.
If
you
go
to
the
to
the
response
that
we're
getting
here,
the
fixture
response
that
corey
jason
thing
incident
management
on
call
schedules,
the
that
property
name
that's
empty
nodes
on
the
back
inside.
This
is
gonna,
be
snake
case.
So
if
we
can
snake
case
it
and
see
where
it's
where
it's
referenced,
that
might
be
helpful.
A
A
A
A
A
A
A
A
B
A
B
A
B
A
B
A
A
A
A
A
A
B
B
A
A
If
we
dive
into
the
expect
graphql
errors
to
be
empty,
let's,
let's
copy
that
method
name
and
do
a
project
wide
search
to
see
if
we
can
find
where
that's
defined
yeah
expect
this
one
yeah.
If
you
do
project
that
should
be
deft
somewhere,
is
there
a
def
anywhere
for
that
yeah?
There
we
go
graphql,
hoppers
all
right,
there's
flattened
errors,
where's
graphql
errors,
great
reference
somewhere
in
here
we'll
also
have
graphql
errors
referenced.
I
think
that
might
be
up.
Maybe.
A
A
A
Yes
raises
an
error.
If
no
data
is
found
yeah,
let's
do
graphql
data.
I
think
I
think
that'll
be
so
instead
of
that,
let's
do
something
like
ex,
I'm
not
sure
how
to
use
dig
at,
but
one
of
these
will
be
able
to
say
something
like
this:
we'll
be
I'll
type.
It
out
we'll
be
able
to
do
something
like
graphql
data.
A
A
A
A
A
B
A
B
B
A
All
right,
I
have
no
idea
I've,
no
freaking
idea,
but
then,
instead
of
referencing
this
as
mock
data,
you
we
can
either
replace
our
references
to
that
thing
and
mock
data
or
replace
mock
data
to
actually
just
re-export
importing
from
this
fixture.
So
you
can
do
a
search
through
the
javascript
files
where
we
do
import.
I
would
do
like
a
project
white
search
for
like
import
dot,
star
fixtures
and
you'll
see,
hopefully,
some
ee
fixtures
being
imported.
A
A
A
B
A
Yep
yep,
but
now
we're
working
system
thanks,
wow,
that's
no
idea
why
it
was.
Oh,
my
gosh,
that's
so
wild!
I
wonder
if
vs
code
just
wasn't
updating
that
I
I
bet
that
was
it
wow.
This
was
not
a
good
day
for
vs
code.
Well,
thanks
james
thanks
john!
This
is
fun.
Sorry,
we
didn't
get
to
get
it
all
glued
together,
but
you.
B
Might
ask
that
little
helper
method?
We
we
card
occult
it
over,
like
it's
only
three
lines,
but
might
even
try
to
consider
adding
that
to
the
the
factory
or
something
make
it
easier
to
do
since
we
duplicated
it.
Yeah
say
that
again
I
don't
understand
that
ad
rotation
for
user,
like
it's
only
three
lines
that
we
copied
over.
So
it's
not
not
a
big
deal
duplication,
but
it.