Skip to content
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.

Added test names to VS Code console logs for ruleTestRunner #3458

Closed
wants to merge 1 commit into from
Closed

Added test names to VS Code console logs for ruleTestRunner #3458

wants to merge 1 commit into from

Conversation

JoshuaKGoldberg
Copy link
Contributor

PR checklist

Overview of change:

Because some of the logs are to process.stdout, the VS Code F5 test running just shows a lot of "Passed" messages. Not very informative. This adds a folder > folder-style descriptor for the test if running with --verboseResultHandler, which is passed by launch.json.

Is there anything you'd like reviewers to focus on?

Alternately, it could just print everything using the console instead of process.stdout...?

Because some of the logs are to `process.stdout`, the VS Code F5 test running just shows a lot of "Passed" messages. Not very informative. This adds a `folder > folder`-style descriptor for the test if running with `--verboseResultHandler`, which is passed by `launch.json`.
@JoshuaKGoldberg
Copy link
Contributor Author

Per #3457 (comment), switched it to always use console.log except for the diffs.

image
image

Copy link
Contributor

@ajafff ajafff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is probably the better way to solve this: microsoft/vscode#19750 (comment)

@ajafff
Copy link
Contributor

ajafff commented Nov 6, 2017

#3374 tries to get rid of all console.log calls and only use process.stdout.write.

adidahiya pushed a commit that referenced this pull request Jan 9, 2018
HyphnKnight pushed a commit to HyphnKnight/tslint that referenced this pull request Apr 9, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants