►
From YouTube: Pajamas UI kit - Figma regression testing false alarm
Description
Please watch at 1.5–2x speed, I didn't have time to trim it down.
And sorry for my sniffing 🤧
A
But
do
stick
around
to
watch
this
if
you're
interested
in
the
process,
I
used
to
build
confidence
in
these
changes
and
learn
about
some
of
the
limitations
of
using
swap
Library
career
is,
if
you
don't
want
a
spoiler,
the
the
swap
Library
breaks.
Oh
if
the
component
API
changes,
that
is
the
properties,
the
variants.
A
If
it's
a
change
of
order
or
name,
then
the
component
resets
back
to
its
default
or
rest
in
state.
If
you
have
feel
free
to
stick
around
and
watch
my
roller
coaster
of
emotions
as
I,
try
and
work
out
if
we're
going
to
introduce
a
big
regression
or
not
hi
Friends
Dan
Mitzi
Harris,
here
I
I
just
want
to
talk
about
a
quite
nasty.
A
Your
high
kit,
regression
that
Katie
found
thanks
Katie
for
bringing
us
up
so
I've
just
testing
this
drop
down
action,
destruction,
Branch
I've,
duplicated
the
file
and
published
it
as
a
library,
so
that
I
can
do
some
swap
Library
testing
with
it
and
I'm
working
in
this
test
file.
Here
so
taking
the.
A
Option
which
one's
part
of
the
pattern
from
the
component
Library
and
configuring
a
bunch
of
different
options
for
it.
Some
of
these
will
break.
Don't
worry
too
much
back
to
it.
So
selected
not
selected
make
these
hover
sorry
about
that
break.
That's
not
the
problem,
and
then
we
make
these
without
tick.
A
So
when
I
do
a
I'm,
gonna
use
a
swap
Library
to
switch
between
the
component
Library
and
my
do
not
use
file,
which
is
a
mirror
of
the
branch
that
I'm
working
on
right
now
it
can
be
a
bit
temperamental
and
fragile,
so
it
doesn't
recommend
it
for
everything,
but
I
think
in
this
case
it
is
highlighting
a
real,
a
real
bug.
So,
if
I
do
a
swap
Library
switching
out
for
do
not
use
Dynamics,
these
will
all
switch
to
use
the
Dynamics
version,
and
you
can
see
we've
lost
everything.
A
Apart
from
the
text
override
the
state
information,
the
Rhythm,
and
that
tick
is
it?
Is
it
selected
yes
or
no,
which
pretty
pretty
bad
regression?
It
would
be
something
that
we'd
deprecate
a
component
and
do
a
whole
break
and
change
thing
for
to
compare
or
as
a
further
test.
Let's
leave
the
options
at
this
level,
the
same
but
add
in
some
stuff,
like
the
like
the
icon
and
switch
that
for
Avatar
switch
them
for
a
button
and
again
these
are
using
the
ones
from
component
Library.
A
A
A
B
A
B
A
A
For
context
why
this
wasn't
caught,
none
of
the
instances
here
broke
when
we
did
the
updates
and
I
wonder
if
that
something
different
happens,
there's
different
behaviors
when
you're
inside
the
same
file.
A
B
B
A
A
A
A
B
A
B
A
B
A
A
B
B
B
A
Give
it
a
hover
State,
because
you
know
that
broke
it.
I
do
swap
like
me.
A
A
B
B
A
A
A
Confident
that
the
changes
aren't
going
to
break
anything
I
think
the
swap
I
think
we've
identified
that's
doing
a
swap
Library
test
components
can't
or
a
limitation
of
the
swap
library
is
when
properties
either
the
key
or
the
value.
If
it
that
changes
order
or
value
like
the
name
of
it,
then
as
using
swap
Library
resets
it
to
its
first.
A
A
A
Questions
for
me
coming
out
of
this.
What
what
is
the
value
of
the
swap
Library
testing?
When
is
it?
When
is
it.
A
And
gives
me
more
confidence
that
building
the
regression
test
in
the
branch
you're
working
in
whether
that
be
just
reviewing
instances
and
making
sure
that
these
don't
update
unexpectedly
or
by
like
I've
done
in
other
branches,
build
build
out
of
Suite
of
tests
before
you
make
the
update
the
the
only
way
or
the
the
best
way
so
far
to
build
confidence
in
the
changes?