Is your feature request related to a problem? Please describe.
The native Slack integration can notify a channel when an individual automated run completes, but it does not provide a scheduled aggregate view across multiple runs. Teams therefore need to review many individual notifications or build separate reporting automation to understand recent quality trends.
Describe the solution you'd like
Add aggregate reporting to the native Slack integration with support for:
- A configurable reporting window, such as the previous 5 or 7 days, plus explicit start and end dates.
- Test counts and pass rates grouped by tag.
- Daily pass-rate trends and, optionally, comparison with a rolling average.
- Filters for project, branch, environment, and run-title pattern.
- Links to the latest matching CI build and Testomat report.
- Scheduled delivery to Slack on a configurable cadence.
- Manual backfill so the same report can be generated for an older date range.
Ideally, scheduled and backfilled reports would use the same filters and output format so teams can reproduce and compare summaries consistently.
Describe alternatives you've considered
The main alternative is to query the Testomat API and maintain a separate scheduled reporting service or dashboard. That duplicates configuration already available in Testomat and makes the native Slack integration less useful as the central reporting path.
Additional context
This would complement the existing per-run completion notifications by providing a concise multi-run quality summary for recurring team reviews.
Is your feature request related to a problem? Please describe.
The native Slack integration can notify a channel when an individual automated run completes, but it does not provide a scheduled aggregate view across multiple runs. Teams therefore need to review many individual notifications or build separate reporting automation to understand recent quality trends.
Describe the solution you'd like
Add aggregate reporting to the native Slack integration with support for:
Ideally, scheduled and backfilled reports would use the same filters and output format so teams can reproduce and compare summaries consistently.
Describe alternatives you've considered
The main alternative is to query the Testomat API and maintain a separate scheduled reporting service or dashboard. That duplicates configuration already available in Testomat and makes the native Slack integration less useful as the central reporting path.
Additional context
This would complement the existing per-run completion notifications by providing a concise multi-run quality summary for recurring team reviews.