mattermost-community/focalboard

Auto-generate Cypress code coverage report

Open

#330 创建于 2021年4月24日

在 GitHub 查看
 (0 评论) (0 反应) (0 负责人)TypeScript (26,187 star) (2,542 fork)user submission
EnhancementHacktoberfestHelp WantedUp for grabs

描述

An issue to track adding code coverage reports to the Cypress test runs. I had looked into this briefly (Cypress docs), but found that it created conflicts with the Jest code coverage. If someone would like to try setting this up, please grab this ticket. Thanks!

Ideally, we would auto-generate code coverage reports on CI runs. If that takes too long (around +10s), we can move that to a separate workflow.

Bonus points: Create a combined Jest + Cypress code coverage report.

贡献者指南

技术栈
typescriptcypressjest
领域
testingci cd
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Basic knowledge of CypressBasic knowledge of JestFamiliarity with CI/CD
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
Review the Cypress code coverage documentation at https://docs.cypress.io/guides/tooling/code coverage. Investigate how to resolve conflicts with Jest code coverage, possibly by using separate coverage directories or combining reports. Consider integrating coverage generation into the existing CI workflow (likely GitHub Actions). If runtime is a concern, evaluate creating a separate workflow for coverage. Optionally, explore tools like nyc (istanbul) to merge Cypress and Jest coverage reports.