onivim/oni

Improve test failure explenation

Open

#2,731 opened on 2019年2月28日

GitHub で見る
 (0 comments) (0 reactions) (0 assignees)TypeScript (11,389 stars) (336 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
half day
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.
Improve test failure explenation · onivim/oni#2731 | Good First Issue