onivim/oni

Improve test failure explenation

Open

#2,731 opened on Feb 28, 2019

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (336 forks)batch import
good first issuehelp wantedinsiderlowering the bar

Repository metrics

Stars
 (11,389 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

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.

Contributor guide

Research direction
Examine the test framework used in the repository and locate where assertions are made. Add descriptive messages to assertions to indicate what is being tested.
Tech stack
typescript
Domain
testing qa
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80