garris/BackstopJS

Clean up CLI output

Open

#165 opened on Feb 20, 2016

View on GitHub
 (7 comments) (0 reactions) (0 assignees)JavaScript (6,510 stars) (601 forks)batch import
enhancementhelp wanted

Description

When running the BackstopJS the command line output is noisy. Some of that is caused by the gulp implementation (see #164) and some of it is just logging out too much stuff at runtime. It would be a great service to the community if someone could help out with this terminal hygiene issue! Namaste.

Contributor guide

Tech stack
javascript
Domain
clitesting
Issue type
refactor
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.
mostly clear
Prerequisites
Node.js basicsFamiliarity with BackstopJS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Review issue #164 for the gulp implementation that contributes to noise. Then examine the CLI output logging in the BackstopJS source code, especially files like cli.js or similar. Look for repeated or verbose log messages that can be reduced or removed. Check the comment threads for any specific suggestions from maintainers.