►
Description
Developers and testers let us know that while it was great to be able to upload a screenshot of a failed test into GitLab they were hard to find and match up to the test results in the Test Reports. We've implemented an issue that now includes a direct link to a screenshot captured that's associated with a failed test in the Test Report Details.
Documentation: https://docs.gitlab.com/ee/ci/unit_test_reports.html#viewing-junit-screenshots-on-gitlab
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/216979
A
Hi,
I'm
james
heimbach,
the
product
manager
for
the
testing
group
at
git
lab
today.
I'm
just
walk
through
a
new
feature
that
will
be
part
of
the
1312
release
and
it's
available
already
on
gitlab.com
today
and
that's
a
link
to
a
failed
screenshot
attachment
as
if
the
test
is
configured
to
capture
a
screenshot
on
failure.
A
So
what
we
hear
from
developers,
what
we
heard
was
that
it's
great,
that
we
could
capture
screenshots
and
include
them
as
an
artifact
in
gitlab,
but
they're
buried
in
the
artifacts
of
a
build,
so
they're
really
hard
to
find
and
they're
not
attached.
So
you
still
have
to
hunt
and
peck
and
figure
out
how
it
relates
to
a
test
so
to
resolve
that
we
implemented
this
feature
so
here
to
just
quickly
show
it
off.
A
Here's
a
merge
request
for
one
of
our
demo
projects
that
you
can
take
a
look
at
and
it
has
a
test
that
has
failed.
This
test
is
configured
to
take
a
screenshot
on
failure,
so
this
feature
is
available
in
the
full
test
report
today
on
the
pipeline
page.
So
in
the
test
report
here
we
can
look
and
see.
We
have
a
test
failure.
A
If
we
look
at
our
details,
we
see
that
we
did
capture
as
an
artifact,
a
job
artifact
a
screenshot
here.
So
our
test
was
expecting
that
the
title
of
this
page
was
fail.
It
was
not
fail
and
so
the
test
failed,
and
so
it
grabbed
the
screenshot
and
attached
it
or
grabbed
it
as
an
artifact
and
uploaded
it.
Now,
it's
here
in
gitlab
and
much
more
easily
accessible
to
the
user.
So
you
can
see
what
actually
was
displayed
on
the
page
as
long
as
you
understand
the
test
and
see
really
what
is
going
on.
A
So
you
can
write
a
better
bug
description
or,
if
your
developer
more
quickly
fix
that
bug.
So
we
hope
that
you
enjoy
this
new
feature,
we're
looking
forward
to
your
feedback
and
for
our
next
iteration,
we'll
be
bringing
the
same
functionality
to
the
modal.
In
the
test
summary
report
on
the
merge
request
page
thanks.