onivim/oni

Improve test failure explenation

Open

#2,731 创建于 2019年2月28日

在 GitHub 查看
 (0 评论) (0 反应) (0 负责人)TypeScript (11,389 star) (336 fork)batch import
good first issuehelp wantedinsiderlowering the bar

描述

Looking for help from the community regarding this issue.

Issue: Unclear CI test failure.

Expected behavior: Failed test would indicate the failure with some extra info for investigation.

Actual behavior: Prints Expected: true, Actual: false which is less than optimal.

Steps to reproduce: Run a failing test.

Would help to have more verbose logging for the tests instead of just 'timed out' and the like. Knowing how far it got / where it got stuck would help.

贡献者指南

技术栈
typescript
领域
testingdesktop
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Familiarity with test runnerBasic knowledge of CI
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
Start by examining the CI configuration file (likely .travis.yml or similar) and the test runner setup (perhaps Jest or Mocha). Look at the test output format and identify where 'Expected: true, Actual: false' is printed. Consider modifying the test runner's reporter or adding custom error messages to provide more context about the failure, such as which assertion failed and where the test got stuck. Check existing issues or PRs that might have discussed this before.