Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: unexpected-error test expects non-colored output #5275

Merged
merged 1 commit into from
Sep 4, 2024

Conversation

thisislawatts
Copy link
Member

Rebase for #4813, but otherwise no changes made.

@thisislawatts thisislawatts requested a review from a team as a code owner May 30, 2024 05:16
@thisislawatts thisislawatts force-pushed the unexpected-error-FORCE_COLOR branch from 3f75051 to eb534db Compare May 30, 2024 05:17
@thisislawatts thisislawatts force-pushed the unexpected-error-FORCE_COLOR branch from eb534db to a7b5d03 Compare September 4, 2024 10:41
Copy link
Contributor

@sandor-trombitas sandor-trombitas left a comment

Choose a reason for hiding this comment

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

🌈

The assertions in unexpected-error.spec.ts expect the output being tested to not contain ANSI color codes. To ensure that is always the case, set FORCE_COLOR="0" so node doesn't output colors.

Without this change, this test will pass or fail depending upon the terminal being used to run the tests. With this change, the test runs consistently.
@thisislawatts thisislawatts force-pushed the unexpected-error-FORCE_COLOR branch from a7b5d03 to dcfbeec Compare September 4, 2024 12:03
@thisislawatts thisislawatts merged commit 230b997 into main Sep 4, 2024
11 checks passed
@thisislawatts thisislawatts deleted the unexpected-error-FORCE_COLOR branch September 4, 2024 13:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants