►
From YouTube: Verify:Testing 12 month direction Jan 2021
Description
An update on progress since the last update in Oct 2020. Walk through some high level themes for the next 12 months for the Verify:Testing team specific to Web Performance Testing.
Oct 2020 update: https://www.youtube.com/watch?v=Mf6r_Infg8w&list=PL05JrBw4t0Kq53VUOvTk3VdXN79PA0SXT&index=12&t=2s
Web Performance Testing Direction: https://about.gitlab.com/direction/verify/web_performance/
A
Hi,
I'm
james
heimbuck,
the
product
manager
for
the
verified
testing
group
at
gitlab.
I
wanted
to
record
another
of
our
12
month
vision
updates
as
we
head
into
our
fiscal
year,
22
q1,
the
last
one
of
these
I
recorded
in
october
and
I'll
link
to
it
below
so
just
a
reminder.
Our
long-term
vision
for
our
group
is.
A
Today,
the
vision
there
remains
much,
the
same,
we're
executing
against
those
maturity
plans
for
code
testing
and
coverage
and
code
quality
to
solve
the
problems
that
I
outlined
three
months
ago
again
I'll
link
to
the
video.
I
am
happy
to
say
that,
as
of
today
january
22nd,
we
have
shipped
our
mvc
for
showing
repeat
test
failures
in
the
test.
A
A
So
this
is
our
direction,
page
I'll
link
to
it
in
the
video
below
web
performance.
I
want
to
talk
a
little
bit
about
what
is
next
and
why
that
is
not
a
scheduled
item,
but
it
is
the
very
next
step
that
we'll
take
and
then
talk
a
little
bit
more
about
the
longer
vision
at
the
end.
So
what's
next
and
why,
for
us
we
discovered
that
really.
A
This
is
a
great
category
in
understanding
how
things
are
going
to
change
or
understanding
where
there's
changes
in
the
performance
of
your
webpage,
but
one
of
the
problems
there
is
that,
maybe
you
don't
know
exactly
what
you
need
to
configure
for
the
urls
or
it's
just
a
really
manual
work
around
in
getting
just
those
pages
tested.
Otherwise
you
might
end
up
testing
the
whole
site,
and
that
slows
down
your
feedback
loop,
which
we
don't
want
to
do
so.
A
The
very
next
thing
for
us
in
this
category
is
using
some
functionality
that
already
exists
in
the
platform
that
we
can
wire
together
to
automatically
scan
just
those
pages
that
have
changed.
So
this
is
a
bit
that
we'll
take
from
the
review.
Apps,
pull
it
down
to
the
web
browser
performance
and
just
run
a
scan
against
those
things,
so
that'll
be
something
that
you
can
enable
as
part
of
your
scan
and
just
increase.
A
The
feedback
loop
where
that
starts
to
get
interesting
and
important
is,
as
we
start
talking
about
that
longer
term
vision
for
this
category
being
able
to
track
the
performance
over
time
being
able
to
track
the
performance
in
test
environments
against
production
environments,
and
really,
you
know
having
all
of
that
in
a
view
that's
easily
found
for
all
of
the
different
personas
developers.
Team
leads.
You
know
up
to
directors
in
the
c-suite
as
they
want
to
see
these
things
so
starting
to
leverage
some
of
the
monitor
data
there.
But
that
view
isn't
just
data.
It's
something!
A
That's
actionable!
It
tells
you
what
you
need
to
do
so
tracking
web
performance
over
time,
comparing
my
performance
stats
against
test,
so
test
production,
test
environments
against
production.
Those
are
two
key
things
that
we
think
really
are
where
we
need
to
go
in
the
next
couple
of
years
in
this
category
and
then
tying
that
back
into
that
overall
vision.
A
Looking
at
that,
that
dashboard
type
view
that
we
looked
at
on
code
testing
and
coverage
so
that
you
can
see
really
what
the
data
looks
like
today
in
the
project
how
the
data
is
trending
over
time,
where
you
need
to
act
a
very
similar
view
here
and
again.
This
is
a
forward-looking
vision.
We
do
expect
some
of
these
things
to
be
pulled
into
issues,
but
this
is
just
an
idea
of
where
we
want
to
take
these
categories.