# Access Selenium Test Screenshots on failed GitLab Pipeline Steps

DevFeed: [Access Selenium Test Screenshots on failed GitLab Pipeline Steps](<https://devfeed.tech/articles/access-selenium-test-screenshots-on-failed-gitlab-pipeline-steps-21373.md>)

Original publisher: [Read original article](<https://juri.dev/blog/2020/10/upload-failed-artifacts-gitlab/>)

Published: 2020-10-14T00:00:00Z

Content type: tutorial

Language: en

Sources: [Juri Strumpflohner](<https://devfeed.tech/sources/juri-strumpflohner.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [Selenium](<https://devfeed.tech/topics/selenium.md>), [Docker](<https://devfeed.tech/topics/docker.md>)

Tags: [chrome](<https://devfeed.tech/tags/chrome.md>), [ci](<https://devfeed.tech/tags/ci.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-image](<https://devfeed.tech/tags/docker-image.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [node](<https://devfeed.tech/tags/node.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [screenshots](<https://devfeed.tech/tags/screenshots.md>), [selenium](<https://devfeed.tech/tags/selenium.md>), [test](<https://devfeed.tech/tags/test.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

## AI overview

This tutorial explains how to configure GitLab pipeline artifacts to retain Selenium test screenshots when a CI step fails. It also mentions a Protractor-based end-to-end setup using a Cypress Docker image with Node.js and Chrome configuration.

## Source excerpt

Lorem ipsum dolor sit amet