►
From YouTube: GitLab 13.3 Kickoff - Verify:Testing
Description
Kickoff Page: https://about.gitlab.com/direction/kickoff/#verify
Ops Direction: https://about.gitlab.com/direction/ops/#verify
We love feedback and you can reach me at jheimbuck@gitlab.com or mention me on GitLab.com using @jheimbuck_gl
A
Hi,
I'm
james
hembach,
the
product
manager
for
the
testing
group
at
the
verify
stage
in
gitlab
today
I
have
one
ramirez
with
me
as
well.
The
product
designer
today
we'll
be
previewing
some
of
the
items
that
the
testing
team
is
working
on
for
the
upcoming
13.3
milestone
you'll
find
a
link
to
the
13.3
kickoff
page
with
links
to
these
items
in
the
verify
stage
direction
page
with
discussion
of
all
of
our
future
work.
A
A
Manually
second
item
I
want
to
talk
about
today
and
that
the
team
is
going
to
be
working
on
is
to
improve
the
performance
of
the
junit
report.
This
feature
the
junit
report,
was
introduced.
First
back
in
12.5,
it's
been
turned
off
by
default
on
gitlab.com
and
as
part
of
the
install
due
to
some
performance
issues
for
really
large
tests.
So
the
team
is
making
a
change
so
that
individual
junit.xml
files
won't
be
loaded
until
a
user
is
drilled
into
that
file.
A
Specifically,
this
will
help
dramatically
speed
up
the
report
for
projects
with
a
large
number
of
tests
like
the
gitlab
project,
and
then
this
will
be
turned.
The
feature
will
be
turned
on
by
default
on
gitlab.com
after
this
work
is
completed
and
we're
happy
with
the
page
speed.
I'm
going
to
hand
it
over
to
juan
who's,
going
to
talk
through
some
of
the
usability
improvements
that
we're
going
to
be
making
as
well
to
the
junit
report
in
the
milestone.
B
Thanks
james,
so
I'm
going
to
share
my
screen
quickly.
B
All
right
so
yeah,
as
james
mentioned,
we
are
also
planning
to
do
some
usability
improvements.
I
think
this
image
it's
a
good
summary
of
the
issues
that
we
currently
have
with
the
genu
unit
report.
B
Most
of
the
issues
that
we
currently
have
are
related
to
the
density
of
data
and
how
it's
being
presented
on
this
table
so
in
these
milestone,
we're
also
exploring
how
to
make
this
table
better.
I
mean,
besides
the
the
the
idea
of
fixing
the
the
evident
visual
box
that
we
have.
The
idea
is
to
make
this
table
much
more
more
flexible,
so
we
can
accommodate
more
things,
as
we
add
new
values
and
new
data
to
the
junit
report.
B
A
more
real
example
is
this
one
in
this
pipeline,
where
you
can
see,
things
are
getting
truncated
and
it's
not
very
easy
for
the
customers
to
see
what's
going
on
unless
they
hover
so
yeah
we're
just
trying
to
improve
the
the
overall
horizontal
real
state
of
this
table
and
making
it
more
flexible
us
as
we
keep
growing
this
feature.