Local JUnit and console output are not scrubbed (document it, or add an opt-in)

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Read the report and CI documentation that describe Probe Cloud uploads, then trace where probe test writes local JUnit, JSON, and console output. Update the docs to identify which outputs are scrubbed and advise keeping secrets out of test names and error messages; add a CHANGELOG entry. The issue leaves whether to add --scrub-output undecided, so settle that scope in the PR description.

Written by the indexing model from the issue text.

Description

area/cli documentation

Summary

Only the Probe Cloud upload payload is scrubbed (relative paths, secret patterns, no artifacts). The JUnit file and the console output that probe test writes locally are the user's own output and are not scrubbed, so a secret that appears in a test name or error message can land in a CI log or a JUnit artifact.

Acceptance criteria

  • The report and CI docs say plainly which outputs are scrubbed (the upload payload) and which are not (local JUnit, JSON, console), and advise keeping secrets out of test names and error messages.
  • Decide in the PR description whether an opt-in --scrub-output is worth adding; if yes, it reuses the upload scrubber and is additive.
  • CHANGELOG entry.
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.