A startup connect failure should still write a valid JUnit report

Open
#410 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #597 by @jay23606 — closed without merging

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
testing

Research direction

Start with the CLI startup connection failure path and the JUnit output writer, then find the tests for closed-port failures and JUnit parsing. Add coverage that checks the output file contains one error testcase per planned test file with the connect error, while the exit code stays unchanged. Document that local JUnit output is unscrubbed, add an additive CHANGELOG entry, and verify the upload payload remains scrubbed.

Written by the indexing model from the issue text.

Description

area/cli bug

Summary

When the CLI cannot connect to the agent at startup (for example a closed port), probe test --format junit -o results.xml returns the error before any result exists and writes no file. CI then has nothing to publish.

Acceptance criteria

  • The failure still writes a valid JUnit file with one <error> testcase per planned test file, carrying the connect error message.
  • The exit code is unchanged.
  • Covered by a test (closed port, junit output file exists and parses).
  • Local JUnit output stays unscrubbed; document that it is the user's own output and only the upload payload is scrubbed.
  • CHANGELOG entry (additive).
Dominant language
Go
Stars
6
Forks
3
Avg merge
6h 28m
Merged PRs (30d)
362

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AlphaWaveSystems/flutter-probe

All issues in AlphaWaveSystems/flutter-probe

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.