Strider-CD/strider

Test output colors not applied if output is too long

Open

#999 opened on Oct 7, 2016

View on GitHub
 (7 comments) (0 reactions) (0 assignees)JavaScript (4,587 stars) (454 forks)batch import
help wanted

Description

We are using Strider v1.9.4

When the output of our tests is too long (2107 lines) the coloring stops working: screen shot 2016-10-07 at 11 25 47

When the output is shorter (~100 lines) the coloring works great (same output but stops before because of test failure): screen shot 2016-10-07 at 11 28 45

Contributor guide

Tech stack
javascriptnodejs
Domain
frontendtesting
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Investigate the rendering of test output in the Strider UI. Look for how the output is transformed and displayed, likely using a library for ANSI color conversion. Check for any truncation or buffering that might affect coloring when output exceeds a certain length. Review the issue comments for any additional context or attempted fixes.