mattermost-community/focalboard

Feature Idea: upload Cypress artifacts in CI

Open

#2,973 opened on Apr 28, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (2,542 forks)user submission
EnhancementHelp WantedUp for grabs

Repository metrics

Stars
 (26,187 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Summary

Configure CI to upload Cypress artifacts.

How important this is to me and why

Importance: Medium

Use cases:

  1. Easier debugging of failed CI runs.

Additional context/similar features

At a glance, looks like it's a matter of using the upload-artifact plugin that we're already using to upload the build directory: https://docs.cypress.io/guides/continuous-integration/github-actions#Caching-Dependencies-and-Build-Artifacts

Contributor guide

Research direction
Look at the existing CI configuration (e.g., GitHub Actions workflow) that uploads the build directory using the upload artifact action. Add a similar step to upload Cypress artifacts (e.g., screenshots, videos) after the Cypress test run. Reference the Cypress documentation on GitHub Actions artifacts.
Tech stack
typescript
Domain
ci cd
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80