Skip to content

chore(ci): try using the spec test reporter instead of tab#6632

Merged
CommanderStorm merged 2 commits intolouislam:masterfrom
CommanderStorm:test-reporter-spec
Jan 7, 2026
Merged

chore(ci): try using the spec test reporter instead of tab#6632
CommanderStorm merged 2 commits intolouislam:masterfrom
CommanderStorm:test-reporter-spec

Conversation

@CommanderStorm
Copy link
Copy Markdown
Collaborator

ℹ️ To keep reviews fast and effective, please make sure you’ve read our pull request guidelines

📝 Summary of changes done and why they are done

this changes from

> cross-env TEST_BACKEND=1 node --test test/backend-test

TAP version 13
# Subtest: Check Translations
    # Subtest: should not have missing translation keys
    ok 1 - should not have missing translation keys
      ---
      duration_ms: 26.698205
      ...
    1..1
ok 1 - Check Translations
  ---
  duration_ms: 28.26023
  type: 'suite'
  ...
# Subtest: Expression Evaluator
    # Subtest: evaluateExpression() returns true when condition matches and false otherwise
    ok 1 - evaluateExpression() returns true when condition matches and false otherwise
      ---
      duration_ms: 1.400332
      ...
    # Subtest: evaluateExpressionGroup() with AND logic requires all conditions to be true
    ok 2 - evaluateExpressionGroup() with AND logic requires all conditions to be true
      ---
      duration_ms: 0.4022
      ...
    # Subtest: evaluateExpressionGroup() with OR logic requires at least one condition to be true
    ok 3 - evaluateExpressionGroup() with OR logic requires at least one condition to be true
      ---
      duration_ms: 0.294209
      ...
    # Subtest: evaluateExpressionGroup() evaluates nested groups correctly
    ok 4 - evaluateExpressionGroup() evaluates nested groups correctly
      ---
      duration_ms: 0.400818
      ...
    1..4
ok 2 - Expression Evaluator
  ---

to something more resonable like

▶ Check Translations
  ✔ should not have missing translation keys (152.595483ms)
✔ Check Translations (155.568093ms)
▶ Expression Evaluator
  ✔ evaluateExpression() returns true when condition matches and false otherwise (2.359275ms)
  ✔ evaluateExpressionGroup() with AND logic requires all conditions to be true (0.606662ms)
  ✔ evaluateExpressionGroup() with OR logic requires at least one condition to be true (0.80885ms)
  ✔ evaluateExpressionGroup() evaluates nested groups correctly (0.498249ms)
✔ Expression Evaluator (7.405674ms)
✔ Test ConditionExpressionGroup.fromMonitor (2.637844ms)

Copilot AI review requested due to automatic review settings January 7, 2026 04:22
@CommanderStorm CommanderStorm enabled auto-merge (squash) January 7, 2026 04:22
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR improves the readability of backend test output by changing the test reporter from the default TAP (Test Anything Protocol) format to the more human-friendly spec format. The change affects how test results are displayed during local development and CI runs, making them easier to read with visual indicators like checkmarks and a cleaner hierarchical structure.

  • Adds --test-reporter=spec flag to both Node.js 20 and 22 test commands
  • Transforms verbose TAP output into concise, visually structured test results

@CommanderStorm CommanderStorm merged commit 41233b6 into louislam:master Jan 7, 2026
23 checks passed
@CommanderStorm CommanderStorm deleted the test-reporter-spec branch January 7, 2026 04:29
@CommanderStorm CommanderStorm added this to the 2.1.0 milestone Jan 7, 2026
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.

2 participants