JetBrains / JetBrains/teamcity-cli
Filter test results by status and highlight new failures
- Dominant language
- Go
- Stars
- 123
- Forks
- 16
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 22
Description
### Area
Build Operations (run, trigger, cancel, logs)
### Problem or use case
Users need to distinguish new failures from existing failures and filter a run’s test results. Test history and paginated results already shipped in #337; MUTED labels are also implemented.
### Proposed solution
First slice:
- Add `--status passed|failed|ignored|new` to `run tests`, using the existing occurrence query support.
- Show NEW for occurrences marked `newFailure`; preserve MUTED labels and existing `--failed` / `--muted` behavior.
- Verify filtering and labels against actual test occurrences, including pagination and empty results. Keep JSON compatible.
The live server accepts build-scoped occurrence queries and returns status/muted fields. Grouping by suite/class needs additional `parsedTestName` data and can follow separately. Project-wide views and mute operations remain demand-driven; investigation management is tracked in #136.
### Alternatives considered
Use `run tests --test` for history and `teamcity api` for queries not yet exposed as flags. No additional top-level test command is needed for this slice.
### Contribution
- [ ] I'd be willing to submit a PR (once it's `status:finalized`)
Contributor guide
Assessment
This issue has not been assessed yet.