►
From YouTube: GitLab 12.10 Kickoff - Verify:Testing
Description
Issues for the 12.10 Milestone for the Testing Group
Kickoff Page: https://about.gitlab.com/direction/kickoff/#verify
CI/CD Direction: https://about.gitlab.com/direction/cicd/
We love feedback and you can reach me at jheimbuck@gitlab.com or mention me on GitLab.com using @jheimbuck_gl
A
Lab
project
first
item
I
want
to
talk
about
today
is
the
next
step
in
our
accessibility
testing
category.
When
we
interview
developers
and
testers
about
accessibility.
One
of
the
problems
we
kept
hearing
about
was
that
the
feedback
loop
was
just
too
slow
to
get
data
about
how
accessibility
had
changed
from
build
to
build.
So
an
issue
number
three:
nine
four
to
five
we're
gonna
be
adding
a
merge
request.
Widget.
It
shows
the
accessibility
results
instead
of
showing
the
full
report
we're
going
to
be
showing
just
results
for
pages
that
have
changed
associated
with
the
EMR.
A
You
can
see
the
design
here
and
in
the
design
tab
itself,
showing
where
accessibility
has
changed,
I,
don't
think
to
learn
more.
The
other
item
I
want
to
talk
about
addresses
feedback
that
we
hear
internally,
all
the
time
from
our
engineering
team.
Even
when
teams
are
running
tests
in
parallel
engineers
may
have
to
wait
up
to
45
minutes
just
for
a
unit
test
to
run
for
code
that
they've
just
committed
so
with
issue
number
one:
nine,
eight,
five:
five
zero.
A
It's
our
next
step
and
you're
trying
to
shorten
that
feedback
loop
by
running
tests
for
modified
code
files
first
in
the
pipeline
in
a
new
job
before
any
other
test
run.
This
will
provide
additional
confidence
that
the
pipeline
will
either
eat
green
because
those
tests
pass
or
provide
a
quicker
feedback
loop
about
failure.
The
testing
team's
gonna
be
dogfooding,
this
item
initially,
and
we
look
forward
to
your
thoughts
on
our
approach
in
getting
those
test
results
back
to
you
sooner
as
always.
I
welcome
feedback
through
discussion
on
these
issues.