microsoft/Terminal

Bootstrap tests on Color Tool

Open

#1,067 opened on May 30, 2019

View on GitHub
 (0 comments) (3 reactions) (0 assignees)C++ (3,212 forks)batch import
Area-CodeHealthHelp WantedIssue-TaskProduct-Colortool

Repository metrics

Stars
 (35,764 stars)
PR merge metrics
 (Avg merge 27d 19h) (24 merged PRs in 30d)

Description

Per #1052, apparently there's no tests already in place for color tool.

This represents going from 0 tests to at least some base level of testing infrastructure so people can't use the "there's no framework, I can't write a test" excuse.

I'd imagine we should have a ut_colortool for checking some of the methods that builds in the classes/componentry and then an ft_colortool that attaches to the console and attempts to run some of the commands and see what it does.

Contributor guide

Research direction
Examine existing test patterns in the Terminal repo (e.g., ut * and ft * tests), then create a ut colortool unit test and an ft colortool functional test for the Color Tool.
Tech stack
cpp
Domain
desktop
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
C++Testing frameworksWindows Terminal development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60