Write tests for CLI

Description

This issue does not include a description.

Contributor guide

Tech stack

javascriptnodejs

Domain

clitesting

Issue type

test

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.

half day

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

Familiarity with JavaScript testing (e.g., Mocha, Chai)Understanding of bootlint CLI usage

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

70

Research direction

Review existing test files in the repository (possibly in 'test/' directory) to understand patterns. Identify the CLI entry point, typically 'bin/bootlint.js'. Write tests covering argument parsing and linting behavior. Consider using 'child process' to spawn the CLI and assert outputs. No linked PRs or comments are present; maintainer attention may be needed to clarify expected test scope.